Response Format
All API errors follow a consistent JSON format: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:- Malformed JSON
- Missing required fields
- Invalid field types
- Invalid parameter values
401 Unauthorized
Returned when authentication is missing or invalid. Example Response:
Required Headers:
For Consumer API:
403 Forbidden
Returned when the user is authenticated but lacks permission. Example Response:- Accessing another organization’s resources
- Insufficient role/permissions
- Resource access restricted
- Session integrity validation failed
404 Not Found
Returned when the requested resource doesn’t exist. Example Response:- Invalid resource ID
- Resource was deleted
- Resource not yet created
- Typo in resource path
409 Conflict
Returned when the request conflicts with current resource state. Example Response:
Resolution:
422 Unprocessable Entity
Returned when request data fails validation. Example Response:429 Too Many Requests
Returned when rate limit is exceeded. Example Response:
Resolution:
500 Internal Server Error
Returned when an unexpected error occurs on the server. Example Response:requestId from the error response.
503 Service Unavailable
Returned when the service is temporarily unavailable. Example Response:- Planned maintenance
- Deployment in progress
- Capacity limits
- Upstream service issues
Database Error Codes
When database constraints are violated, specific error codes are returned.Unique Constraint Violations
Example Response:email- Email already registeredname- Name already in usesku- Product SKU already exists
Error Handling Best Practices
Global Error Handler
Retry Logic
Related Resources
- SDK Errors - SDK error reference
- Common Issues - Troubleshooting guide
- Contact Support - Get help