Submit and process application
Combine submission and processing into a single call.
Headers
Required for POST requests. Reuse the key only when retrying the same operation with an identical payload.
Path Parameters
Responses
| Status | Description |
|---|---|
200 |
Application submitted and processed |
400 |
Request failed. All gateway errors are returned as HTTP 400 with this envelope. |
200 response
Unique identifier for the application.
ID of the tenant that owns this application.
UUID of the customer this application belongs to.
Type of application. One of individual or business.
Current status of the application. creating_account is a deprecated transitional value and should not be treated as a required lifecycle step. manual_review means a human decision is required.
Possible values: draft, submitted, processing, creating_account, manual_review, approved, rejected, expired
First name of the individual. Required.
Last name of the individual. Required.
Middle name of the individual.
Email address of the individual. Required.
Role of the individual in the application (for example, owner).
Phone number of the individual, in E.164 format. May be required depending on your account configuration.
Date of birth of the individual, in YYYY-MM-DD format. Required.
Gender of the individual.
Nationality of the individual, in ISO 3166-1 alpha-2 format.
Social Security Number of the individual. May be required depending on your account configuration.
Tax Identification Number of the individual. May be required depending on your account configuration.
Primary source of income. May be required. One of employment, self_employment, investments, retirement, or other.
Current employment status of the individual (for example, employed or self_employed).
Country of citizenship, in ISO 3166-1 alpha-2 format. May be required depending on your account configuration.
Type of government-issued ID. May be required. One of drivers_license, passport, or state_id.
Document number of the government-issued ID. May be required depending on your account configuration.
Country that issued the identification document, in ISO 3166-1 alpha-2 format.
Expiry date of the identification document, in YYYY-MM-DD format.
Front of the government-issued ID, as a Base64 data URI. May be required depending on your account configuration.
Back of the government-issued ID, as a Base64 data URI.
Proof of address document, as a Base64 data URI.
Sources of the individual's wealth. May be required depending on your account configuration.
Free-text description of the source of wealth when not covered by the standard options.
Purposes for opening the account. May be required depending on your account configuration.
Free-text description of account purposes when not covered by the standard options.
Sources of funds for the account. May be required depending on your account configuration.
Free-text description of the source of funds when not covered by the standard options.
Countries where the individual expects to transact, in ISO 3166-1 alpha-2 format. May be required depending on your account configuration.
Expected monthly volume of fiat transactions. May be required depending on your account configuration.
Expected monthly volume of crypto transactions.
Registered legal name of the business. Required.
Trading name or DBA (doing business as) name of the business.
Description of the business operations. May be required (minimum 100 characters).
Legal entity type of the business (for example, llc or corporation). Required.
Industry category of the business. May be required depending on your account configuration.
Public-facing website URL of the business.
Official registration or incorporation number of the business.
Tax Identification Number (TIN) of the business. May be required depending on your account configuration.
Date the business was incorporated, in YYYY-MM-DD format.
Country where the business is incorporated, in ISO 3166-1 alpha-2 format. Some account configurations require this to be US.
US state where the business is incorporated. May be required depending on your account configuration.
Current operating status of the business (for example, active or inactive).
Provide at least one associated person.
Indicates whether the business has ownership held through a material intermediary.
Business formation document, as a Base64 data URI.
Document showing the ownership structure of the business, as a Base64 data URI.
Proof of business address, as a Base64 data URI.
Document that verifies the nature of the business, as a Base64 data URI.
Indicates whether the business is a decentralized autonomous organization (DAO).
Primary purpose for opening the account (for example, operations or payroll).
Primary source of business funds (for example, revenue or investment).
Subtype of financial services industry, if applicable.
Subtype of crypto industry, if applicable.
Description of the industry when it does not fit a standard category.
Countries where the business expects to transact, in ISO 3166-1 alpha-2 format.
Sources of funds for the account. May be required depending on your account configuration.
Free-text description of the source of funds when not covered by the standard options.
Document verifying the business TIN, as a Base64 data URI. May be required depending on your account configuration.
Authorization document for the account, as a Base64 data URI. May be used depending on your account configuration.
Indicates whether the business is a money services business (MSB).
Purposes for opening the account. May be required depending on your account configuration.
Free-text description of account purposes when not covered by the standard options.
Primary geographic market the business targets.
Free-text description of the primary target market when not covered by the standard options.
Expected monthly volume of fiat transactions.
Expected monthly volume of crypto transactions.
Kind of account to open (for example, regular or savings). This is the account type, not the customer type. Use the top-level application_type field for individual vs business.
Possible values: regular, savings
Currency for the account, in ISO 4217 format.
Blockchain network to back the account (for example, polygon or stellar).
Blockchain wallet address to associate with the account.
UUID of an existing Gravv wallet to link to the account.
Human-readable label for the account.
ID of the provider agreement associated with this application.
URL to the terms of service the applicant must accept.
Arbitrary key-value pairs for storing additional information about the application.
Arbitrary key-value pairs attached to the application.
List of validation errors returned when the application data does not meet provider requirements.
The field that failed validation.
Human-readable explanation of the validation error.
Machine-readable error code for the validation failure.
Suggested fix for the validation error.
Timestamp when the application was submitted, in ISO 8601 format.
Timestamp when the application was processed by the provider, in ISO 8601 format.
Timestamp when the application was created, in ISO 8601 format.
Timestamp when the application was last updated, in ISO 8601 format.
Timestamp when the application was soft-deleted, if applicable.
One of the following variants:
Account kind.
Possible values: active, frozen, deleted, pending
- null (
null)
Processing stage where the error occurred.
Human-readable explanation of the processing error.
Machine-readable error code.
Suggested fix.
400 response
Human-readable error message.
Authorization
- ApiKeyAuth