🚦 Status Codes & Responses

DexCheck uses standard HTTP status codes to indicate the outcome of REST API requests. When an error occurs, responses include a uniform JSON error object. Below are the standard HTTP status codes you can encounter when working with the DexCheck API:

200 OK	Request succeeded.	Valid endpoint, parameters, and authentication (if required).
400 Bad Request	Malformed request or invalid parameters.	Missing required field, bad JSON, unsupported value.
401 Unauthorized	Missing or invalid API key.	No X-API-KEY header or malformed key.
403 Forbidden	Valid key but insufficient privileges.	Key doesn’t grant access to this endpoint or plan limits hit.
404 Not Found	Resource does not exist.	Unknown pair_id, token_id, or wrong path.
429 Too Many Requests	Rate limit exceeded.	Exceeded requests/minute or concurrent WS connections.
500 Internal Server Error	Unexpected server failure.	Transient backend error; retry with back-off.
502 Bad Gateway	Upstream service error.	Gateway timed out or upstream dependency failed.
503 Service Unavailable	API temporarily unavailable.	Maintenance, deployments, or overloaded conditions.

Error Response Example:HTTP/1.1 400 Bad RequestContent-Type: application/json​{"error": {"code": 400,"message": "Invalid query parameter: 'chain' must be one of ['eth','bsc','sol',…]"}}

Tip: Always inspect the error.message for details and implement retry/back-off logic on 429, 502, and 503 responses.