Docs
PricingDashboard

Platform errors

Invalid JSON-RPC or HTTP request

Before forwarding, the gateway parses the HTTP request for the network family. Invalid JSON-RPC envelopes, disallowed verbs, oversized bodies, and illegal batches return standard JSON-RPC parse / invalid-request codes.

HTTP 400HTTP 405HTTP 413-32700-32600

← All errors

Example response

Example

HTTP/1.1 400 Bad Request
Content-Type: application/json

{
  "jsonrpc": "2.0",
  "id": null,
  "error": {
    "code": -32700,
    "message": "invalid json-rpc payload"
  }
}

Causes

  • Body is not valid JSON or not a JSON-RPC object/array.
  • Missing method field (missing json-rpc method).
  • Empty batch or batch larger than the gateway max batch size.
  • HTTP verb not allowed (most families require POST; some TRON paths allow GET).
  • Request body exceeds MaxBodyBytes (body too large → HTTP 413, code -32600).
  • Catalog row forbids the HTTP verb for that method (HTTP 405, -32600).

How to fix

  • Send Content-Type: application/json and a JSON-RPC 2.0 object with jsonrpc, id, method, and params.
  • Prefer POST for JSON-RPC families (EVM, Solana, Bitcoin, …).
  • Keep batches within the documented/gateway limit; split large batches.
  • For TRON Full Node HTTP paths, use the exact path and verb from the method docs.

Other parse messages you may see

empty json-rpc batch / json-rpc batch too large — batch array issues (-32700).

method not allowed — wrong HTTP verb for the family or method (-32600, often HTTP 405).

body too large — payload over the gateway limit (-32600, HTTP 413).

HTTP {VERB} not allowed for {method} — method catalog rejects that verb (-32600, HTTP 405).

Related