# v1.3.0

#### Added

* **User Password Reset:** A new endpoint has been added to the Partner API, allowing partners to trigger a password reset for an active user. The user will receive a new temporary password via email, which will expire after 30 days.
  * **Endpoint:** `POST /users/{userId}/reset-password`
* **Enhanced API Validation:** New validation rules have been implemented to increase API robustness and data integrity.
  * **Technical Details:**
    * **Header Validation:** Comprehensive OpenAPI validation has been added for required header parameters (e.g., `requestorId`), enforcing presence, type, format, and other constraints.
    * **Duplicate Account Prevention:** Added API and database-level validation to prevent duplicate `refAccount` values during customer creation and updates.

#### Changed

* **Onboarding Process Refactored:** The centralized onboarding process has been split into three dorelease-test-specific APIs to improve clarity and separation of concerns. The documentation has been updated to clearly describe the three distinct workflows:
  * **Role Onboarding:** Manages `CUSTOMER` and `PROXY` roles via the `/roles/onboardings` endpoint.
  * **Entity Onboarding:** Manages `BENEFICIAL_OWNER` entities via the `/entities/onboardings` endpoint.
  * **User Onboarding:** Manages partner users via the `/user-onboardings` endpoint.
* **Onboarding Process Improvement:** The entity onboarding flow has been refactored to correctly process multiple administrative tasks (e.g., adding signatories) for a single customer.
* **NACE Sector Data:** The list of available NACE sectors has been updated.


---

# 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://docs.tradevest.ai/release-notes/archive/v1.3.0-test-environment.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.