Errors

All error responses follow a consistent format.

Error Response Format

{
  "error": {
    "code": "USER_NOT_FOUND",
    "message": "User not found",
    "detail": null
  }
}

Field	Type	Description
`code`	`string`	Machine-readable error code for programmatic handling
`message`	`string`	Human-readable error description
`detail`	`object \| null`	Additional context when available

HTTP Status Codes

Status	Meaning
`400`	Bad Request. Invalid input or validation error.
`401`	Unauthorized. Invalid or missing API key.
`403`	Forbidden. Valid API key but insufficient permissions.
`404`	Not Found. Resource does not exist.
`409`	Conflict. Resource already exists or state conflict.
`429`	Too Many Requests. Rate limit exceeded. See Rate Limiting.
`500`	Internal Server Error. Contact support if persistent.

Handling Errors

Use the code field for programmatic error handling:

if (response.error.code === 'USER_NOT_FOUND') {
  // Handle missing user
} else if (response.error.code === 'DUPLICATE_PHONE_NUMBER') {
  // Handle duplicate phone
}

Retries

For 5xx errors, retry with exponential backoff. For 4xx errors, fix the request before retrying.

Setup

Users

Companies

Accounts

Virtual Asset Postings

Cards

Card Shipments

Card Designs

Crypto Deposits

Card Transactions

Activities

Policies

Simulation

Virtual Assets

Webhooks

Error Response Format

HTTP Status Codes

Handling Errors

Retries

​Error Response Format

​HTTP Status Codes

​Handling Errors

​Retries

Error Response Format

HTTP Status Codes

Handling Errors

Retries