Skip to main content

Error Response Format

All API errors follow a consistent format:

Error Categories

Validation Errors (400)

Returned when request data fails validation.
How to handle:
  1. Parse the details.errors array
  2. Display field-specific errors to the user
  3. Do NOT retry automatically

Authentication Errors (401)

Returned when API key is invalid or missing.
How to handle:
  1. Check that API key is configured correctly
  2. Verify the key hasn’t been revoked in dashboard
  3. Contact support if issue persists

Rate Limit Errors (429)

Returned when you exceed request limits.
How to handle:
  1. Wait for retryAfter seconds
  2. Implement exponential backoff
  3. Consider request batching

Conflict Errors (409)

Returned when a resource conflict occurs.
How to handle:
  1. For duplicates, use the existing resource
  2. For locked resources, wait and retry
  3. Check idempotency key for accidental duplicates

Server Errors (500)

Returned when an unexpected error occurs.
How to handle:
  1. Retry with exponential backoff (up to 3 times)
  2. If persists, contact support with requestId
  3. Log the error for debugging

Error Code Reference

Order Errors

Manifest Errors

Validation Errors

Auth Errors

Retry Strategy

Implement exponential backoff for retryable errors:

Localization

Error messages are provided in both English (message) and Spanish (message_es). To request errors in Spanish, add the Accept-Language header:
Always save the requestId from error responses. Support can use this to investigate issues quickly.