Get an account application
Returns one application with what it waits for. Act on status_reason. Upload required_documents or send required_fields with the update, or send the customer to required_action_url for terms or verification. Use status, not the deprecated provisioning object.
Path Parameters
ID of the account application. Read it from the account (application_id) or from the application webhooks.
Responses
| Status | Description |
|---|---|
200 |
The application |
404 |
Not found, or not in your business |
200 response
Possible values: individual, business
Possible values: individual, joint, minor, business
processing while the bank works, blocked while it waits on you or the customer, manual_review while Gravv holds it, then approved or rejected. draft and submitted appear only on applications not made with POST /v2/accounts.
Possible values: draft, submitted, processing, blocked, manual_review, approved, rejected, expired, cancelled
Associated person ID. Use it as party_id on a document.
Possible values: primary, joint_owner, authorized_individual, guardian, minor_beneficial_owner, trustee, grantor, trustee_and_grantor, executor
Possible values: declared, documents_pending, verified_locally, submitted_to_provider, flagged, accepted
Same codes as on the account. The API returns it only when you read a single application.
The update returns it when it checks the data you sent
Deprecated. Use the flat status fields and status.
{
"data": {
"application_id": "5e7a9c1b-2d4f-4a6b-8c0d-e1f2a3b4c5d6",
"customer_id": "0b6f3c1e-2a4d-4c8e-9f10-7d2a6b5e4c33",
"customer_type": "individual",
"registration_type": "individual",
"status": "blocked",
"parties": [
{
"role": "primary",
"status": "declared",
"first_name": "Jane",
"last_name": "Doe"
}
],
"created_at": "2026-10-13T09:12:44.512031Z",
"updated_at": "2026-10-13T09:20:02.118734Z",
"status_reason": "awaiting_customer_data",
"required_fields": [
"tax_id_number"
],
"requires_user_action": true
},
"error": null
}
404 response
Error message. When several fields fail, it names the first and says how many others are in details. Branch on the HTTP status and the details codes, not on this text.
Field problems, keyed by field path. Each value is CODE: message, such as REQUIRED: Customer ID is required. The API joins several problems on one field with ; .
{
"data": null,
"error": "Resource not found"
}
Authorization
- ApiKeyAuth