Skip to article
relayOpen console
Authentication
On this page

Start

Authentication

Use Relay credentials, manage application access, and keep keys out of public code.

Bearer authentication

Send your Relay key in the Authorization header. Dashboard sign-in and API authentication are separate: your login session does not authorize an RPC request.

Request headers
Content-Type: application/json
Authorization: Bearer YOUR_RELAY_KEY

Use your Relay key to authenticate with Relay. An active paid Mainnet period and an eligible key are required.

SDKs that accept an RPC URL

The HTTP RPC endpoint also accepts ?api-key=YOUR_RELAY_KEY. Use this form when an SDK accepts a URL but cannot set authorization headers.

RPC URL format
https://relayrpc.top/rpc?api-key=YOUR_RELAY_KEY

Choose one authentication method. Duplicate query keys, malformed authorization headers, or a header and query containing different keys are rejected.

Manage and replace keys

Name keys for their application or environment. To rotate a secret, create a replacement within your plan limit, update your application, then revoke the old key in API keys.

Revoked keys cannot be restored. A key can also become unusable when account access is inactive or it exceeds the purchased plan’s key limit. Creating more keys does not increase credits or throughput.

Search documentation

Find what you need

Search article headings, methods, and explanations.