RPC Gateway quickstart

RPC Gateway gives applications a stable entry point to blockchain networks. Your application keeps one App API Key and calls the Gateway URL shown in the dashboard.

You can start without an Endpoint for a small set of read methods already cached by Accelerator. Configure your own Endpoint when you need complete method coverage, reliable fallback on a miss, writes, or uncached data.

Before you start

• A platform administrator has provisioned your account and you can sign in.
• Your target chain and network appear under Chains.
• For methods outside Accelerator, synchronize a network supported by both the vendor and the Gateway from Providers, or add a working upstream RPC URL manually.

Make your first call

1. Create an App

Open Apps in the dashboard, create an App, and select the networks you need. The system creates an API Key and the corresponding Gateways.

Store the API Key securely. You can view it again, rotate it, or revoke it from the App key-management page.

2. Copy the Gateway URL

Copy the complete Access Point from the App or Gateway page. The Host selects the chain, network, and protocol; the API Key selects the App. Do not construct a production domain yourself.

This example uses the Ethereum Mainnet Host format with Bearer authentication:

export RPC_URL='https://ether-jsonrpc.<gateway-domain>'
export APP_API_KEY='<app_api_key>'

You can also use the Path Key URL shown by the dashboard:

https://ether-jsonrpc.<gateway-domain>/<app_api_key>

3. Make an Endpoint-free first call

eth_blockNumber is an EVM Accelerator method. It can return a shared cached result even when the Gateway has no Endpoint:

curl "$RPC_URL" \
  -H "Authorization: Bearer $APP_API_KEY" \
  -H 'Content-Type: application/json' \
  --data '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}'

Example success response:

{"jsonrpc":"2.0","id":1,"result":"0x13a4f20"}

A cache miss returns -32004 No available Endpoint. This does not mean the Key or Gateway is invalid. Check the method and parameters in Accelerator, or continue by configuring an Endpoint.

4. Configure an Endpoint for complete method access

For methods outside Accelerator, fallback on a cache miss, or write calls:

1. In Endpoints, add an upstream with the same chain, network, and protocol as the Gateway.
2. Run the Endpoint health check to validate its URL and provider credentials.
3. Open the target Gateway and add the Endpoint to the default JSON-RPC route.
4. Choose priority failover or weighted load balancing.

After setup, use the network verification method in the chain guide, such as EVM eth_chainId.

Production checklist

• Use the target chain guide’s network verification method to confirm the network.
• Parse JSON-RPC error objects inside HTTP 200 responses; do not rely on HTTP status alone.
• Decide how to handle Accelerator misses: accept -32004, or configure an Endpoint for fallback.
• On rate limits, read Retry-After and retry with backoff and jitter.
• Do not replay write calls blindly. Read the retry boundaries in Routing and reliability.
• Never put an API Key in source code, logs, error reports, or public URLs.

Continue with Accelerator, your target chain guide, Authentication, and JSON-RPC. For native TRON endpoints, see TRON HTTP API.