Skip to main content
This reference documents HTTP API error responses, their meanings, and how to handle them in your integration.

Response Format

All API errors follow a consistent JSON format:
For validation errors:

HTTP Status Codes

2xx Success

4xx Client Errors

5xx Server Errors

400 Bad Request

Returned when the request is malformed or contains invalid data. Example Response:
Common Causes:
  • Malformed JSON
  • Missing required fields
  • Invalid field types
  • Invalid parameter values
Resolution:

401 Unauthorized

Returned when authentication is missing or invalid. Example Response:
Response Variants: Required Headers: For Consumer API:
For Admin API:
Resolution:

403 Forbidden

Returned when the user is authenticated but lacks permission. Example Response:
Common Causes:
  • Accessing another organization’s resources
  • Insufficient role/permissions
  • Resource access restricted
  • Session integrity validation failed
Resolution:

404 Not Found

Returned when the requested resource doesn’t exist. Example Response:
Common Causes:
  • Invalid resource ID
  • Resource was deleted
  • Resource not yet created
  • Typo in resource path
Resolution:

409 Conflict

Returned when the request conflicts with current resource state. Example Response:
Common Scenarios: Resolution:

422 Unprocessable Entity

Returned when request data fails validation. Example Response:
Handling Validation Errors:
Common Validation Types:

429 Too Many Requests

Returned when rate limit is exceeded. Example Response:
Response Headers:
Rate Limit by Endpoint: Resolution:

500 Internal Server Error

Returned when an unexpected error occurs on the server. Example Response:
Resolution:
When contacting support, provide the requestId from the error response.

503 Service Unavailable

Returned when the service is temporarily unavailable. Example Response:
Common Causes:
  • Planned maintenance
  • Deployment in progress
  • Capacity limits
  • Upstream service issues
Resolution:

Database Error Codes

When database constraints are violated, specific error codes are returned.

Unique Constraint Violations

Example Response:
Common Fields:
  • email - Email already registered
  • name - Name already in use
  • sku - Product SKU already exists

Error Handling Best Practices

Global Error Handler

Retry Logic