> 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/changelog/readme.md).

# Changelog

New updates and improvements

{% updates format="full" %}
{% update date="2026-08-13" %}

## API v2 Update — Share Verified KYC/KYB Data

**New: Share Verified KYC/KYB Data**

A new method is now available in the Compliance endpoint — **Share Verified KYC/KYB Data** — `POST /v2/compliance/{customerId}/share`.

This method applies a SumSub share token to an existing customer, transferring already-verified KYC/KYB data instead of requiring the customer to go through verification again. One token covers the whole share:

* For an **INDIVIDUAL** — the customer's own verified profile.
* For a **CORPORATE** — the company profile, copied together with its verified beneficiaries/UBOs.

The token is validated before it is consumed. If the token is rejected, the response returns `applied: false` with the reason in `message`, and nothing is applied — the request can be retried with a corrected token. Once a token has been **successfully** applied (`applied: true`), the customer can no longer be shared again and subsequent calls will return `409`.

Tokens are short-lived (\~20 minutes) and single-use.

**Required next steps after a successful share**

* Call `PATCH /v2/customer/{customerId}/application` to finalize the customer's application status.
* If the response includes items in `outstanding`, the shared data did not fully cover the required verification level. Use `GET /v2/compliance/{customerId}/web_sdk_link` to generate a link for the customer to upload the remaining document sets (e.g. `PROOF_OF_RESIDENCE`).

Please note: this method is not available for partners on the BaaS verification program (`403`).
{% endupdate %}

{% update date="2026-05-06" %}

## API v2 Update — Compliance & Document Types

**New: Compliance**

A new Compliance endpoint is now available. It includes a new method **Get Compliance Link** — `GET/v2/compliance/{customerId}/web_sdk_link` — which generates a short-lived URL for the customer's KYC/KYB verification flow. When opened, the URL launches a modal window with the required verification fields for the customer to complete.

***

**Heads up: Set Customer Application is being deprecated**

The **Set Customer Application** method in the Application endpoint will be deprecated soon. Going forward, the new application flow should be handled through the **Get Compliance Link** method.

Please note: Get Compliance Link does not affect the current functionality of Set Customer Application. Both methods remain active and can be used simultaneously.

***

**New: Additional document types**

In the **Get Customer Application** endpoint, the following new document types have been added:

`SOURCE_OF_FUNDS`, `TYPE_VISA`, `IDENTIFY_BIOMETRICS`, `INCUMBENCY_CERT`, `PHOTO`, `COMPLIANCE_OFFICER_RESUME`, `REGULATORY_LICENSE`, `SANCTIONS_AUDIT`, `SANCTIONS_POLICY`, `TRADE_LICENSE`, `COMMERCIAL_LICENSE`, `WOLFSBERG_GCBDDQ`, `SOURCE_OF_WEALTH_COMPANY`, `SOURCE_OF_WEALTH_SHAREHOLDER`, `ORG_CHART`, `AML_KYC_POLICY`, `OWNERSHIP_STRUCTURE`, `UBO_POA`, `DIRECTOR_POA`, `UBO_LIVENESS`, `DIRECTOR_LIVENESS`, `CONTRACT`, `INVOICE`, `TERM_SHEET`, `BILL_OF_LADING`.
{% endupdate %}

{% update date="2026-04-14" %}
KYC/KYB Requirements article updated

Please note that the sample documents templates have been updated, make sure use the new versions for your clients' onboarding. 

{% endupdate %}
{% endupdates %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.delos.financial/changelog/readme.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.