Change application status

Sets the status of an application: canceled, delivered or refund.

Find the application by id or by external_id: pass one of them, not both.

A repeated request with the status the application already has returns 200 and does not change the application.

New status	From
`canceled`	`new`, `consent_signed`, `pre_scoring_approved`, `bank_selected`, `scoring_rejected`
`delivered`	`signed`
`refund`	`signed`, `delivered`

HTTP	Meaning	Next step
`200`	The status is set.	—
`400`, `401`, `404`, `409`, `422`, `500`	The request is rejected.	See «Errors» below.

The body of an error: error_code and error_description. The texts of validation errors are in Russian.

HTTP	`error_code`	When	What to do
`400`	`1001`	`X-Request-Id` is missing or is not a UUID.	Pass a new UUID.
`401`	`3001`	The signature is invalid.	Check the signature: see Invoice Overview.
`401`	`3002`	`X-JWS-Signature` is missing.	Pass the signature.
`404`	`4001`	The application is not found.	Check `id` or `external_id`.
`409`	`2001`	The transition is not allowed from the current status.	Check the status with Get application status.
`409`	`2002`	The application is in a final status: `pre_scoring_rejected`, `canceled`, `canceled_customer`, `expired` or `refunded`.	Do not repeat the request.
`422`	`1001`	Both `id` and `external_id` are passed, none of them, or `status` is not `canceled`, `delivered` or `refund`.	Fix the request.
`500`, `503`	`5000`	Internal error.	Repeat the request later with a new `X-Request-Id`.

Responses

🟢200Success

application/json

Headers

Bodyapplication/json

Example

{
    "id": "0190c3e2-7f3a-7c1b-9e4d-2a6f8b1c4d55",
    "status": "delivered",
    "updated_at": "2026-10-31T16:00:00+05:00"
}

🟠400Bad Request

🟠401Unauthorized

🟠404Not Found

🟠409Conflict

🟠422Unprocessable Entity

🔴503Service Unavailable

Request