---
updatedAt: 2026-09-29T08:31:43.000Z
agentTools:
projectIndex: https://docs.sumsub.com/llms.txt
---
# Change applicant status to init
# Overview
Use this method to change the [applicant review status](https://docs.sumsub.com/sumsub/reference/get-applicant-review-status#review-statuses) back to `init` (**Documents requested**).
This allows you to request missing documents without resetting previously uploaded documents or completed verification steps.
### Warning
This endpoint can temporarily reject the status change with a `409 Conflict` error, a message asking to retry, and a header indicating the time after which you can retry — for example, `Retry-After: 10` (seconds). This can happen when an applicant is set to `pending` and then almost immediately moved to a final status via the API (for example, `approved` right after `pending`) — the request may arrive while internal processing is still running.
To handle this:
- Retry `409` responses instead of treating them as permanent failures. If the response includes a `Retry-After` header, wait for the interval it specifies; otherwise, fall back to a short fixed delay (for example, 10–15 seconds).
- Avoid calling `approve`/`reject`/`init` immediately after moving an applicant to `pending` — wait for processing to finish, or be ready to retry on conflict.
### Attention
This method is intended specifically for cases when applicants are in the `onHold` (**Requires action**) status and have at least one grey (**Requested**) step. It is designed to help you manage such cases more efficiently.
In all other situations—when the applicant has no grey (**Requested**) steps—the status you attempt to assign will be automatically overridden and replaced with the system-determined status.
### Note
The [Reset applicant profile](https://docs.sumsub.com/reference/reset-applicant) method also sets the applicant status to `init` but resets all completed verification steps, deactivates all uploaded documents, and removes all previously assigned statuses.
# Required permissions
To use this method, your [app token](https://docs.sumsub.com/sumsub/docs/app-tokens) must have the following [permissions](https://docs.sumsub.com/sumsub/docs/user-roles#permissions):
* **View applicants**
* **View applicant's personal data**
* **Manage applicant notes**
* **Manage applicant tags**
# Request example
```curl
curl -X POST \
'https://api.sumsub.com/resources/applicants/687fb2373fc85ad66b5d0000/-/init' \
-H 'content-type: application/json' \
-H 'X-App-Token: ' \
-H 'X-App-Access-Sig: ' \
-H 'X-App-Access-Ts: ' \
-d '{
"note": "Example note",
"tags": [
"First tag",
"Second tag"
],
"reasons": {
"manual": [
"additionalDocumentRequest"
]
}
}'
```
# Response explained
If the request is sent and processed successfully, you will receive a JSON response representing the applicant profile.
You can see the response structure, possible content with descriptions, and examples of response on the [following page](https://docs.sumsub.com/sumsub/reference/get-applicant-data#response-explained).
If the request fails, you will receive an HTTP response containing an error code and a message explaining the error. For example:
```json
{
"code": 400,
"description": "Applicant must be on hold to move to init",
"correlationId": "0d3457fdac54803edf23c932ddd561a2"
}
```
# Errors
| Error code | Description |
| :--------- | :-------------------------------------------------------------------------------------------------------------------------------------- |
| `400` | Applicant must have at least one grey step to move to `init`. |
| `400` | Applicant must be on hold to move to `init`. |
| `400` | When moving an applicant to **Documents requested** status at least one reason must be provided / At least one reason must be provided. |
| `400` | The request body must not be `null`. |
# OpenAPI definition
```json
{
"openapi": "3.1.0",
"info": {
"title": "sumsub-api",
"version": "1.0"
},
"servers": [
{
"url": "https://api.sumsub.com"
}
],
"components": {
"securitySchemes": {
"sec0": {
"type": "apiKey",
"name": "X-App-Token",
"in": "header",
"x-default": ""
}
}
},
"security": [
{
"sec0": []
}
],
"paths": {
"/resources/applicants/{applicantId}/-/init": {
"post": {
"summary": "Change applicant status to init",
"description": "",
"operationId": "change-applicant-status-to-init",
"parameters": [
{
"name": "applicantId",
"in": "path",
"description": "Unique identifier of the applicant in the Sumsub system.
This identifier is a random combination of 24 digits and lowercase Latin characters. It is automatically generated when the applicant is created on the Sumsub side, and can be found in the [Dashboard](https://cockpit.sumsub.com/checkus/#/applicants/individual?limit=10&page=0).
If the `applicantId` is unknown to you, use the [Get applicant data (externalUserId)](https://docs.sumsub.com/sumsub/reference/get-applicant-data-via-externaluserid) method to fetch it.",
"schema": {
"type": "string"
},
"required": true
}
],
"requestBody": {
"content": {
"application/json": {
"schema": {
"type": "object",
"required": [
"reasons"
],
"properties": {
"note": {
"type": "string",
"description": "Optional note text providing additional context for the applicant profile. Notes can be added and managed either in the Dashboard or via [dedicated API methods](https://docs.sumsub.com/sumsub/reference/add-applicant-note)."
},
"tags": {
"type": "array",
"description": "[Tags](https://docs.sumsub.com/sumsub/reference/add-custom-applicant-tags) that you may want to assign to the applicant profile. Each string represents a standalone tag.
⚠️ Mind that tag names are case sensitive.",
"items": {
"type": "string"
}
},
"reasons": {
"type": "object",
"description": "Includes internal objects where each object stands for a predefined reason group and contains an array of strings with predefined reasons.
⚠️ For this method, we highly recommend using the `manual` group with the `additionalDocumentRequest` reason, so that all such cases are clearly separated.",
"properties": {
"fraud": {
"type": "array",
"description": "Covers cases where the applicant intentionally tries to deceive the system or commit identity fraud. Refer to the [Reason List](https://docs.sumsub.com/sumsub/reference/external-rejection-reasons-list#fraud-group) for available reasons.",
"items": {
"type": "string"
}
},
"finance": {
"type": "array",
"description": "Covers financial risks and payment-related fraud. Refer to the [Reason List](https://docs.sumsub.com/sumsub/reference/external-rejection-reasons-list#finance-group) for available reasons.",
"items": {
"type": "string"
}
},
"regulation": {
"type": "array",
"description": "Covers legal and compliance-related violations. Refer to the [Reason List](https://docs.sumsub.com/sumsub/reference/external-rejection-reasons-list#regulation-group) for available reasons.",
"items": {
"type": "string"
}
},
"abuse": {
"type": "array",
"description": "Covers violations of platform rules or misuse of services. Refer to the [Reason List](https://docs.sumsub.com/sumsub/reference/external-rejection-reasons-list#abuse-group) for available reasons.",
"items": {
"type": "string"
}
},
"device": {
"type": "array",
"description": "Covers risks associated with applicant devices. Refer to the [Reason List](https://docs.sumsub.com/sumsub/reference/external-rejection-reasons-list#device-group) for available reasons.",
"items": {
"type": "string"
}
},
"manual": {
"type": "array",
"description": "Covers cases where the final decision was made by the risk or compliance team. Refer to the [Reason List](https://docs.sumsub.com/sumsub/reference/external-rejection-reasons-list#manual-group) for available reasons.",
"items": {
"type": "string"
}
}
}
}
}
}
}
}
},
"deprecated": false
}
}
},
"x-readme": {
"headers": [],
"explorer-enabled": true,
"proxy-enabled": true
},
"x-readme-fauxas": true
}
```