# July 2025 - v1.1.0

**Release date**: 25.07.2025

This update brings several enhancements to the Apentis API, focusing on better document support, data validation, and improved integration capabilities.

***

### New document types

We’ve added 3 new document types to improve support for regional and regulatory KYC needs:

* Criminal Record: used to assess whether an individual has any criminal history relevant to AML risk classification.
* Engagement Letter: a formal letter confirming the agreement between a client and your organization. Frequently required for onboarding validations.
* Unique Identification Number (NIU): a national identifier used in the Democratic Republic of Congo (RDC) for individuals and legal entities.

These document types are now fully supported in document submission and retrieval endpoints and are included in KYC completeness checks.

### Unique `crmCode` control

To prevent duplicates, a validation check has been added to ensure that the `crmCode` used when creating a new business relation is unique.\
\
If the code already exists, the API will return HTTP 409 Conflict with a clear error message.

### New address fields for Business relations

We’ve added address-related fields to the business relations endpoints for better data structure and completeness:

* `address`
* `postalCode`
* `city`

These fields are now accepted in creation and update requests and returned in GET responses.


---

# Agent Instructions: 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:

```
GET https://apentis.gitbook.io/apentis-api/release-notes/release-notes/2025/july-2025-v1.1.0.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.