Endpoints and authentication
All rpc edge hosts, ports, regional aliases, and the API-key authentication forms for HTTP, WebSocket, and gRPC in one place.
Every rpc edge product, its endpoint, and how to authenticate - the canonical reference. Access is issued as a UUID API key; treat it like a password.
Endpoints
| Product | Endpoint | Protocol |
|---|---|---|
| Solana RPC (HTTP) | https://rpc.rpcedge.com | JSON-RPC over HTTPS |
| Solana RPC (WebSocket) | wss://rpc.rpcedge.com | JSON-RPC subscriptions |
| Yellowstone gRPC | grpc.rpcedge.com:443 | Geyser gRPC (TLS) |
| Decoded Shreds | grpc.rpcedge.com:443 | gRPC SubscribeDeshred (Desk+) |
| Transaction sender | https://relay.rpcedge.com | JSON-RPC / raw HTTP / QUIC |
Regional aliases
Every host has a Frankfurt-pinned alias - prefix the hostname with frankfurt. to force traffic to
Frankfurt explicitly:
https://frankfurt.rpc.rpcedge.com
wss://frankfurt.rpc.rpcedge.com
frankfurt.grpc.rpcedge.com:443
https://frankfurt.relay.rpcedge.comAuthentication
Your key is a UUID (e.g. 10bcb316-cd81-47d2-89c4-375354a8c54f). Send it in whichever form fits
your transport.
HTTP and WebSocket
A query parameter (matches normal Solana SDK endpoint patterns):
https://rpc.rpcedge.com?key=YOUR_UUID_KEY
wss://rpc.rpcedge.com?key=YOUR_UUID_KEYOr a header (server-side clients):
Authorization: Bearer YOUR_UUID_KEY
x-api-key: YOUR_UUID_KEY
x-token: YOUR_UUID_KEYgRPC
Pass the key as gRPC metadata:
x-api-key: YOUR_UUID_KEY
authorization: Bearer YOUR_UUID_KEY