Skip to main content

The error object

All error responses share the same structure:
string
required
The HTTP status code as a string, mirroring the response status header.
string
required
A human-readable description of what went wrong and what to do next. Safe to surface to your users.
string
required
A machine-readable error code. Use this to handle specific error cases programmatically. Follows the format error_{domain}_{specific_condition}.
array
Present only on validation errors (error_validation_error). Contains field-level details when multiple fields fail.

Validation error example

When a request fails validation on multiple fields, the validations array provides field-level detail:

HTTP status codes


Handling errors

Check the type field to handle specific error cases in your integration. Use the message field to surface a reason to your users.
Every error response includes an X-Request-ID header. Include this in any support request — it lets the Nuvion team trace the exact request in our systems.

Error reference

Error types follow the format error_{domain}_{specific_condition}. The domain indicates which part of the API the error originates from.

Authentication & authorization

Validation

Entities

KYC

KYB

Accounts

Transfers

Counterparties

Stablecoin wallets

Account details resolution

Card acquiring

Webhooks

Resources & system