> For the complete documentation index, see [llms.txt](https://docs.delos.financial/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.delos.financial/batchservice/request-batch-changes.md).

# Request Batch Changes

Reopens a committed batch for corrections. The batch moves from `CLOSED` to `CHANGE_REQUESTED`; you can then get new storage credentials, upload corrected files and a new manifest, and commit again.

Calling it on a batch already in `CHANGE_REQUESTED` is a no-op. Calling it on an `OPEN` batch returns `409`: an open batch is already editable.

**Endpoint**

`POST /v2/compliance/batch/{batch_id}/change`

**Link**

<https://partner.sandbox.delos.financial/openapi/v2.html#/operations/BatchService_RequestBatchChanges>

**Request**

**Path Parameters**

| Parameter      | Type     | Description                        | Required | Example                                  |
| -------------- | -------- | ---------------------------------- | -------- | ---------------------------------------- |
| **`batch_id`** | `string` | Batch ID returned by Create Batch. | Yes      | `"01a0af8b-831f-7dbe-8eaf-459f81998958"` |

**Headers**

| Key             | Value              | Required |
| --------------- | ------------------ | -------- |
| `Authorization` | `<JWT>`            | Yes      |
| `Accept`        | `application/json` | Yes      |

**Body**

No request body.

**Response (200 OK)**

Returns the `Batch` object. See Create Batch → Response Fields for every field and the `counters` object.

**Example Response:**

```json
{
  "batch_id": "01a0af8b-831f-7dbe-8eaf-459f81998958",
  "status": "CHANGE_REQUESTED",
  "schema_version": "string",
  "types": [
    "individual",
    "company"
  ],
  "individual_kyc_level": "string",
  "company_kyc_level": "string",
  "party_kyc_levels": [
    "string"
  ],
  "counters": {
    "total": 120,
    "draft": 0,
    "valid": 0,
    "invalid": 3,
    "creating": 2,
    "submitted": 85,
    "finished": 24,
    "change_requested": 4,
    "rejected": 1,
    "failed": 1
  },
  "processed": false,
  "done": false,
  "created_at": "2026-09-28T10:15:30Z",
  "committed_at": "2026-09-28T11:02:04Z",
  "error": ""
}
```

***

**Examples**

**Request**

```bash
curl --request POST \
  --url <https://partner.sandbox.delos.financial/v2/compliance/batch/01a0af8b-831f-7dbe-8eaf-459f81998958/change> \
  --header 'Accept: application/json' \
  --header 'Authorization: Bearer <JWT>'
```

***

**Error Responses**

Errors are returned as `{"code", "message", "details"}`, where `code` is a gRPC status code. Use the HTTP status for error handling.

**Batch Cannot Be Changed (409)** — the batch is `OPEN` or `CANCELLED`:

```json
{ "code": 10, "message": "batch cannot be changed from its current state", "details": [] }
```

**Batch Not Found (404)** — the batch does not exist or belongs to another partner:

```json
{ "code": 5, "message": "batch not found", "details": [] }
```

**Authorization fail (401)**:

```json
{ "code": 16, "message": "Unauthorized", "details": [] }
```

***

**Notes**

* **Full manifest**: after reopening, always upload the **complete** manifest, not only the changed rows. The manifest is the source of truth: a row you remove that has not yet been submitted for review is withdrawn.
* **Replace files under new paths**: upload a corrected document under a new file path instead of overwriting the old one, and point the row to it.
* **Final rows are history**: rows in `finished`, `rejected` or `failed` are never changed by a later commit. To retry a `failed` customer, add a new row with a new `row_key`.
* **Immutable row identity**: the `type` and `external_customer_id` of an existing `row_key` cannot be changed.
* **Customer-side fixes**: for rows in `change_requested`, you can also send the end customer a verification link from Get Item WebSDK Link.

**Typical Workflow**:

1. Find rows to fix with Get Batch Status.
2. Call `POST /v2/compliance/batch/{batch_id}/change`.
3. Get new credentials with Get Upload Credentials.
4. Upload corrected files under new paths and the full `manifest.json`.
5. Call Commit Batch.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.delos.financial/batchservice/request-batch-changes.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.