Responses - Error Codes

The body of every response will include the following fields.

descriptionDescription of the response.
payloadThe object containing the actual data requested.
statusThe status of the response.
titleThe human readable name associated with the HTTP status according to the HTTP Status Code Registry.

Historical Data

Some endpoints have startDate & endDate parameters, but no pagination parameter. These endpoints have a limit to how much historical data can be returned per query depending on the granularity. In order to get more than the max, you must use the startDate & endDate parameters to move the time frame window to get the next n minutes/days/months of data.


In an erroneous response, the description field will indicate the reason for the error.

Status CodeRESTWebSocket
200Successful RequestSuccessful Connection
400Bad Request – Invalid request format or query results exceed 10 MB limitBad Request - Invalid request format, instrument is not supported or missing parameter
401Unauthorized – Invalid or missing API KeyUnauthorized – Invalid or missing API Key
403Forbidden – Access to endpoint is not authorized
404Not Found – Pair or address does not exist for example
429Too Many Requests – rate limit was exceeded
5xxInternal Server Error – We had a problem with our serverInternal Server Error – We had a problem with our server
502Bad Gateway
504Gateway Timeout – Exceeded 28 second limit


A successful response will be indicated by a HTTP status code of 200 and the payload will include the desired data.