Skip to main content
The Chariow API uses conventional HTTP response codes to indicate the success or failure of requests.

Response Format

All API responses follow a consistent format:

HTTP Status Codes

Common Errors

Authentication Errors (401)

Causes:
  • Missing Authorization header
  • Invalid API key format
  • Revoked or expired API key
Solution:

Resource Not Found (404)

Causes:
  • Invalid resource ID
  • Resource belongs to a different store
  • Resource has been deleted
  • Product is not published (for public endpoints)

Validation Errors (422)

Causes:
  • Missing required fields
  • Invalid field format
  • Business rule violations

Rate Limit Exceeded (429)

Solution: Wait for the specified time and retry. See Rate Limits for details.

Handling Errors

JavaScript Example

PHP Example

Error Codes Reference

Checkout Errors

License Errors

Best Practices

Don’t assume success - always check the HTTP status code before processing the response.
Log error responses for debugging and monitoring purposes.
Translate API errors into user-friendly messages for your customers.
For 5xx errors and rate limits, implement automatic retry with exponential backoff.