All API errors return a structured problem detail object conforming to RFC 9457. This makes errors machine-readable and consistent across every endpoint.
Problem Detail Fields
Field
Type
Present
Description
type
string
Always
A URI that identifies the problem type.
title
string
Always
A short, human-readable summary of the problem.
status
number
Always
The HTTP status code.
detail
string
Optional
A human-readable explanation specific to this occurrence.
intentId
string
Optional
The intent ID related to the error, if applicable.
field
string
Optional
The request field that caused the validation failure.
HTTP Status Codes
Status
Meaning
Typical Scenarios
400
Bad Request
Malformed JSON or missing required headers.
401
Unauthorized
Missing x-api-key header.
403
Forbidden
Invalid API key, or the key's environment does not match the requested chain.
404
Not Found
Resource does not exist for the given ID.
409
Conflict
Resource state conflicts with the requested operation.
422
Unprocessable Content
Validation failure, blockchain simulation failure, or unsupported chain.
429
Too Many Requests
Rate limit exceeded. Retry after the Retry-After header value.
500
Internal Server Error
Unexpected server-side failure. Contact support if persistent.
