Error Handling
The API uses standard HTTP status codes to indicate success or failure of requests.
Status Codes
| Code | Description |
|---|---|
200 |
Success - Request completed successfully |
201 |
Created - Resource created successfully |
204 |
No Content - Request successful, no response body |
400 |
Bad Request - Invalid request parameters or validation error |
403 |
Forbidden - Unauthorized access or insufficient permissions |
404 |
Not Found - Requested resource does not exist |
500 |
Internal Server Error - Server encountered an unexpected error |
Error Response Format
Error responses include a descriptive message to help diagnose the issue:
{
"timestamp": "2026-02-13T10:30:00Z",
"status": 400,
"error": "Bad Request",
"message": "Validation failed for field 'name': must not be blank",
"path": "/api/private/v2.0/events"
}Best Practices
-
Always check the HTTP status code before processing the response
-
Implement retry logic for 500-series errors with exponential backoff
-
Log error responses for debugging
-
Handle validation errors (400) by checking the message field