Errors

Landed returns standard JSON-RPC 2.0 error objects for protocol-level errors, and standard HTTP status codes for transport-level and plan-level errors.

HTTP status codes

Status	Meaning
401 Unauthorized	Missing or invalid x-api-key.
403 Forbidden	The key’s subscription is inactive or access is suspended. Check Plan & billing in the Console.
429 Too Many Requests	You've exceeded your plan's rate limit. Back off and retry.
502 Bad Gateway	The upstream RPC service or WebSocket handshake could not be reached.
503 Service Unavailable	The regional endpoint is temporarily unable to serve requests.

JSON-RPC error object

A request that reaches the RPC layer but fails returns a standard JSON-RPC error:

{
  "jsonrpc": "2.0",
  "id": 1,
  "error": {
    "code": -32602,
    "message": "Invalid params: ..."
  }
}

Error codes follow the same conventions as Solana core. See the Solana JSON-RPC error reference for the full list.

Retrying

429 responses are safe to retry with backoff. 401 responses won't resolve on retry: check that your API key and header name (x-api-key) are correct.