Skip to Content
Quickstart
View Markdown source

RPC Gateway quickstart

RPC Gateway gives applications a stable entry point to blockchain networks. Create an App to receive an API Key and Gateway Access Points, then add an Endpoint for full RPC coverage when your application needs it.

  • Creating an App gives you an API Key and a Gateway for each selected network.
  • Every Gateway checks the shared cache by default for supported Endpoint-free RPC reads.
  • An Endpoint-backed Route extends the same Access Point to writes, additional methods, and upstream data.

Before you start

  • You have an RPC Gateway account and can sign in to the dashboard.
  • Your target chain and network appear under Networks and hosts.

Set up access

Create an App and call its Gateway with a supported Endpoint-free RPC read. Every Gateway checks the shared cache by default.

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 in a secret manager or protected runtime environment. You can view it again, rotate it, or revoke it under App Settings → Access keys.

Copy the Access Point

Open the App Overview, select the target Gateway, and copy its complete Access Point. For server-side applications, use the Host-only Access Point with the API Key in the Authorization header:

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

SDKs that accept a complete RPC URL can use the Access Point that carries the API Key in its first path segment:

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

Make an Endpoint-free RPC read

This Ethereum Mainnet example uses the eligible eth_blockNumber method:

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"}

Use the exact method and parameter forms listed in Endpoint-free RPC.

Production checklist

  • Confirm the network with the target chain guide’s verification method.
  • For ID-bearing requests, inspect the JSON-RPC Response and branch on result or error independently of the HTTP status.
  • Configure an Endpoint for upstream methods, writes, uncached data, and stable fallback coverage.
  • Apply Retry-After, exponential backoff, random jitter, and a bounded attempt count to rate-limited requests.
  • Use Retries to understand which failures and operations can move to another Endpoint.
  • Keep API Keys in secret storage and use redacted identifiers in logs and support requests.

Next steps

Last updated on