Error Handling

Standard HTTP Status Codes

Status Code	Meaning	Common Causes
200	Success	Request completed successfully
400	Bad Request	Invalid request format, missing required fields
401	Unauthorized	Invalid or expired access token
403	Forbidden	Insufficient permissions for the requested resource
404	Not Found	Resource does not exist
429	Too Many Requests	Rate limit exceeded for your account or source IP
500	Internal Server Error	Server-side error

Error Response Format

{
  "statusCode": 401,
  "message": "Unauthorized",
  "error": "Invalid or expired token",
  "timestamp": "2024-03-18T10:30:00.000Z",
  "path": "/v3/users/list",
  "requestId": "abc123-def456-ghi789"
}

Handling Common Errors

401 Unauthorized - Token Expired

400 Bad Request - Validation Errors

403 Forbidden - Insufficient Permissions

429 Too Many Requests - Rate Limit Exceeded

Rate limits are applied per billing account and per source IP address, using a fixed one minute window. Every response carries X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset so you can track your usage without waiting for an error.

The account limit is shared across every user and integration under your billing account, so running additional workers in parallel will not increase your throughput.

See Rate Limits for full details.

Error Handling

Standard HTTP Status Codes#

Error Response Format#

Handling Common Errors#

401 Unauthorized - Token Expired#

400 Bad Request - Validation Errors#

403 Forbidden - Insufficient Permissions#

429 Too Many Requests - Rate Limit Exceeded#

Retry Logic for 5xx Errors#