Ethereum JSON-RPC
The Ethereum JSON-RPC surface on
POST https://triport.io/eth— the standardeth_*set plusdebug_,trace_,txpool_,net_andweb3_namespaces, with node-admin namespaces explicitly documented as not supported.
Choosing an endpoint or a plan rather than a method? See Ethereum RPC endpoint. Chain ID, RPC URL and network config: Ethereum chain ID & RPC URL.
- Method / Endpoint
POST https://triport.io/eth- Network
- Ethereum
- Authentication
x-tokenheader (recommended); see Authentication- Required scope
- — (tier-gated per method)
- Tier / rate limit
- Any tier;
debug_/trace_sit in heavier categories — see Rate Limits
How to call
Every method takes the same envelope — only method and params change:
curl https://triport.io/eth \
-H "x-token: $TRIPORT_API_KEY" \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"eth_getBalance",
"params":["0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045","latest"]}'Batching (a JSON array of request objects) is supported; each entry is tier-checked and rate-limited individually.
Support semantics
| Status | Meaning |
|---|---|
| Supported | Routed to an upstream node, result returned unchanged (eth_*, debug_*, trace_*, txpool_*, net_*, web3_*). |
| Extension | Provider-specific additions that are not base chain RPC (e.g. bundle submission). |
| Not supported | Node-admin namespaces (admin_*, personal_*) return -32601 (method_unknown) by design; their pages document that behavior so the response is never a surprise. |
See Errors for the full error envelope.
Method reference
The pages below are grouped by namespace — eth_, debug_, trace_,
txpool_, net_, web3_, and the documented-unsupported admin_/personal_
set. Subscriptions (newHeads, logs, newPendingTransactions, syncing)
live on the WebSocket channel — see Ethereum WS.