RPC error HTTP 404: endpoint_not_found

Last updated:

At a glance

Error details
PropertyValue
Applies toEvery network, HTTP and WebSocket
HTTP status404
REST body{"error":"endpoint_not_found","code":404}
Unknown networkJSON-RPC -32601: Unknown network "<name>"
RetryableNo: fix the URL

Cause

Routing happens before the body is read. An unregistered REST path gets the fixed body {"error":"endpoint_not_found","code":404}, and an unknown network name gets a JSON-RPC -32601 with the name quoted back. The body deliberately does not list valid routes. The usual causes are a copied example from another provider, a missing /rpc/ or /sol segment, or /ws/ paths used over plain HTTP.

Solution

  1. Check the URL against the endpoint list for your network: https://triport.io/sol, /rpc/<network>, or /r/<API_KEY>/<network>.
  2. If the error is Unknown network, compare the name in the message with the network IDs in the docs.
  3. On TRON, confirm the method is on the wallet method list. The catalog is read-only, and methods outside it answer 404.
  4. For a WebSocket path, connect with wss:// and an upgrade. A plain POST to a /ws/ route is not a request that route serves.

404, 403 or -32601?

Each answer comes from a different stage, which tells you where to look.

Three ways to be told something does not exist
AnswerStageWhat it means
404 endpoint_not_foundRouterThe URL is not a route
403 method_unknownMethod gateThe URL is fine; the method is not part of the product on this chain
-32601 on HTTP 200NodeThe node does not implement the method

Example

{
  "error": "endpoint_not_found",
  "code": 404
}

FAQ

Is a 404 the same as method not found?
No. A 404 is about the URL. An unknown method on a valid URL gets 403 method_unknown from the gateway, or -32601 from a node.
Why does a TRON wallet path answer 404?
Our TRON catalog is read-only and lists specific methods. Paths outside it, such as walletsolidity routes and transaction broadcast, are not served.