Docs
PricingDashboard

Platform errors

Auth & invalid endpoint

JSON-RPC full-node calls authenticate with the endpoint UUID in the URL path and the network/environment subdomain — no API key header on those URLs. (The separate signed Public API / Address Watch uses X-Api-Key and HMAC headers instead.) Misconfigured hosts or UUIDs return JSON-RPC -32000 with an explanatory message.

HTTP 400HTTP 403HTTP 404-32000

← All errors

Example response

Example

HTTP/1.1 404 Not Found
Content-Type: application/json

{
  "jsonrpc": "2.0",
  "id": null,
  "error": {
    "code": -32000,
    "message": "endpoint not found"
  }
}

Causes

  • Typo in the endpoint UUID path segment.
  • Wrong subdomain: network or environment does not match the endpoint record.
  • Endpoint was paused in the dashboard.
  • Invalid Host header / wrong root domain (not a trusted RpcNode host).

How to fix

  • Copy the full HTTPS URL from the dashboard — do not rebuild the host by hand unless you know the slug and environment.
  • URL shape: https://{prefix}-{network}-{environment}.{brand}/{endpoint-uuid}
  • If the endpoint is paused, resume it in the dashboard or create a new one.
  • Treat the URL as a secret: anyone with it can use your RPS and credits.

Common -32000 messages

invalid host — Host is not a valid {prefix}-{network}-{environment}.{trusted-domain} form.

network not served by this instance — this gateway process is not configured for that network slug.

endpoint not found — UUID missing, malformed path, unknown endpoint, or host prefix does not match this UUID (HTTP 404). Same body for a wrong vanity + real UUID, so the pair is not leaked.

resolver unavailable — temporary control-plane lookup failure (HTTP 502).

Related