> 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/get-item-websdk-link.md).

# Get Item WebSDK Link

Generates a fresh verification link for a batch row in `change_requested`. Send the link to the end customer so they can correct data or upload missing documents themselves, without another batch commit.

The link is available only while the row is in `change_requested`; for any other status the method returns `409`.

**Endpoint**

`GET /v2/compliance/batch/{batch_id}/items/{row_key}/web_sdk_link`

**Link**

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

**Request**

**Path Parameters**

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

**Headers**

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

**Response (200 OK)**

Returns a `GetItemWebSDKLinkResponse`.

**Response Fields**

| Field             | Type      | Description                                | Example                                  |
| ----------------- | --------- | ------------------------------------------ | ---------------------------------------- |
| **`url`**         | `string`  | Verification link for the end customer.    | `"<https://in.sumsub.com/websdk/p/>..."` |
| **`ttl_seconds`** | `integer` | How long the link stays valid, in seconds. | `1800`                                   |

**Example Response:**

```json
{
  "url": "<https://in.sumsub.com/websdk/p/sbx_example>",
  "ttl_seconds": 1800
}
```

***

**Examples**

**Request**

```bash
curl --request GET \
  --url <https://partner.sandbox.delos.financial/v2/compliance/batch/01a0af8b-831f-7dbe-8eaf-459f81998958/items/client-001/web_sdk_link> \
  --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.

**Row Not In change\_requested (409)** — the row is in any other status:

```json
{ "code": 10, "message": "item is not in change_requested", "details": [] }
```

**Item Not Found (404)**:

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

**Authorization fail (401)**:

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

***

**Notes**

* **Fresh link every call**: request a new link when the previous one expires.
* **Useful for two-sided documents or missing files**: when a customer needs to add something only they have, the link is faster than a new batch cycle.
* **Result**: once the customer completes the check, the row continues through review and its status updates in Get Batch Item.


---

# 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/get-item-websdk-link.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.