Errors

Failures follow JSON-RPC 2.0: a response with an error object instead of a result.

Error shape

Responses are always a JSON array, so a failure arrives as a one-element array whose entry carries an error in place of a result. The error has a numeric code, a human-readable message, and sometimes a data field. In a batch, each entry succeeds or fails on its own.

[
  {
    "jsonrpc": "2.0",
    "id": 1,
    "error": {
      "code": -32602,
      "message": "unknown window '3m' (supported: 1s, 10s, 30s, 1m, 5m, 30m, 1h, 2h, 4h, 6h, 8h, 12h, 24h)"
    }
  }
]

Codes

Code-32700

MeaningParse error

WhenThe payload was not valid JSON.

Code-32600

MeaningInvalid request

WhenNot a valid JSON-RPC request, or a batch over 64 items.

Code-32601

MeaningMethod not found

WhenNo method by that name.

Code-32602

MeaningInvalid params

WhenA parameter is missing or invalid - a malformed mint or an unknown window, for example.

Code-32000

MeaningUpstream timeout

WhenThe data backend did not respond in time.

Code-32001

MeaningUpstream failure

WhenThe data backend returned an error.

Code	Meaning	When
`-32700`	Parse error	The payload was not valid JSON.
`-32600`	Invalid request	Not a valid JSON-RPC request, or a batch over 64 items.
`-32601`	Method not found	No method by that name.
`-32602`	Invalid params	A parameter is missing or invalid - a malformed mint or an unknown window, for example.
`-32000`	Upstream timeout	The data backend did not respond in time.
`-32001`	Upstream failure	The data backend returned an error.

PreviousRate limits