Skip to main content
You set an application’s status when you create it, and it records a decision that has already happened. There is no in-progress status and no lifecycle to move through. Report all three outcomes.

​
Statuses

Every application, whatever its status, needs entities.account_holders, product_name, details.underwriting with is_secured, is_mla, and currency_code, decision.decided_at, decision.reason, and documents. When you send both limit and max_limit, limit cannot be higher, on any status.

​
Changing a status

Status cannot change after you create the application. A PATCH that includes status returns 200 and leaves the status unchanged. To correct a status you reported in error, create a new application with the correct status and data. If you already opened a user account from it, close that user account and open a new one that references the new application.

​
Using an approved application

Only an approved application can be referenced as application_id when you create a user account with the credit_with_underwriting feature. The user account’s account holders, authorized signers, and account_holder_type must match the application’s when you create the user account.

​
Webhooks

Applications do not send webhooks. You set every status yourself, so there are no Lead-driven changes to listen for. Applications Overview · The Application Object · User Accounts