Get application status

Returns the current status of an application.

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

Only applications created with Create application are found.

Fields without a value are not returned.

Application status flow

Statuses are the values of status.
From new, consent_signed, pre_scoring_approved, bank_selected and scoring_rejected, the application can also move to canceled, canceled_customer or expired: these transitions are not drawn.

Status	Meaning
`new`	The application is created: the client has not opened the link yet or has not given consent.
`consent_signed`	The client gave consent to the data check.
`pre_scoring_approved`	The preliminary check is passed: the client chooses a bank offer.
`pre_scoring_rejected`	The preliminary check is failed.
`bank_selected`	The client chose a bank and a program: `approved_amount` and `bank_code` are returned.
`scoring_rejected`	The bank declined the application.
`signed`	The client signed the agreement with the bank: hand over the goods, then set `delivered`.
`delivered`	The merchant confirmed the delivery with Change application status.
`canceled`	The merchant cancelled the application with Change application status.
`canceled_customer`	The client cancelled the application.
`expired`	The application expired: the client did not complete it in time.
`refund`	The merchant requested a refund with Change application status.
`refunded`	The refund is completed.

Label	Meaning
consent	The client gave consent to the data check.
check passed	The preliminary check is passed.
check failed	The preliminary check is failed.
bank chosen	The client chose a bank offer.
bank declined	The bank declined the application.
signed	The client signed the agreement with the bank.
delivered	The merchant confirmed the delivery with Change application status.
refund requested	The merchant requested a refund with Change application status.
refunded	The refund is completed.

Result

HTTP	Meaning	Next step
`200`	The status is returned.	If the status is not final, repeat the request later.
`400`, `401`, `404`, `422`, `500`	The request is rejected.	See «Errors» below.

Errors

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`.
`422`	`1001`	Both `id` and `external_id` are passed, none of them, or `id` is not a UUID.	Pass one of them.
`500`, `503`	`5000`	Internal error.	Repeat the request later with a new `X-Request-Id`.

Responses

🟢200Success

application/json

Headers

Bodyapplication/json

Examples

SignedNew

{
    "id": "0190c3e2-7f3a-7c1b-9e4d-2a6f8b1c4d55",
    "external_id": "order1001",
    "status": "signed",
    "approved_amount": 1500000,
    "currency": "UZS",
    "bank_code": "anorbank",
    "created_at": "2026-10-31T15:00:00+05:00",
    "updated_at": "2026-10-31T15:20:00+05:00"
}

🟠400Bad Request

🟠401Unauthorized

🟠404Not Found

🟠422Unprocessable Entity

🔴503Service Unavailable

Get application status

Application status flow#

Result#

Errors#

Request

Responses

Application status flow

Result

Errors