RPC and WebSocket workloads
ThorEdge handles standard Solana RPC calls and WebSocket subscriptions. Supported account-query methods use the same URL and are routed through FastGate. Choose Yellowstone gRPC or Pulse Decoded Shreds when you need a persistent data stream instead of request-response RPC.Quick reference
Before you start
You need:- An active pass or rental with an enabled network and location
- A token for that location
curlandjqfor the first request- One stable public egress IPv4 if you want to restrict the token
Copy your endpoints
1
Select your access
Open Endpoints, keep the Endpoints tab selected, then choose the
pass or rental you want to use.
2
Choose a network and location
Select the network and an offered location for the access.
3
Create or select a token
Use a token for the selected location. You can optionally restrict it to one
stable public IPv4 address.
4
Copy both secure URLs
Copy the complete
https:// RPC URL and wss:// WebSocket URL. Do not
assemble either URL yourself.Send your first request
Follow the RPC and WebSocket quickstart to receive a blockhash over HTTPS and slot notifications over WSS. The HTTP method reference lists every method ThorEdge serves and which service answers it.Run in production
- Treat non-2xx HTTP responses and JSON-RPC
errorobjects as failures. - Retry only transient failures with bounded backoff and jitter.
- Recreate WebSocket subscriptions after reconnecting and reconcile state when gaps matter.
- Recopy a URL after its token is regenerated or revoked; other location tokens are unaffected.
- Read current throughput and concurrency values from Usage and Limits.