Errors

Author profile photo
Team Quickex
August 29, 2025
~1 min read

2xx Success

4xx Client Error

5xx Server Error

Quickex uses standard HTTP status codes to indicate the result of a request:
2xx — success,
4xx — error in request data/permissions,
5xx — server-side error (rare).

Some 4xx responses include a short
error.code and message for programmatic handling.

Handling recommendations

  • Log the HTTP status and the response body.
  • For 429 and temporary 5xx, use retries with exponential backoff (backoff + jitter).
  • Validate required parameters before sending the request.

Code Title Description
200 OK Everything worked as expected.
400 Bad Request Invalid request (often a required parameter is missing).
401 Unauthorized No valid token/key provided.
402 Request Failed Parameters are valid, but the operation was not completed.
403 Forbidden Insufficient permissions to perform the request.
404 Not Found The resource does not exist.
409 Conflict Conflict with the current state (duplicate, inconsistency, etc.).
424 External Dependency Failed A failure in an external dependency prevented the request from being completed.
429 Too Many Requests Rate limit exceeded — reduce frequency and apply backoff.
500, 502, 503, 504 Server Errors Server-side error. Retry later (with backoff).

Information summary 
Quickex uses standard HTTP codes. 2xx — success; 4xx — validation/permission/client errors; 5xx — server errors (rare). Handled 4xx responses include an error code and message. For 429 and temporary 5xx, use exponential backoff with jitter. Always log the status and response body.
Share this article: