HTTPS
RPC
For Solana, a successful getHealth request returns a JSON-RPC result of “ok”. Check both the HTTP status and the JSON-RPC error field.
Service guide ↗Quickstart / from endpoint to application
Make the connection.
Build from there.
Set up your account, choose the right interface, and test a connection before adding it to your application. These examples follow the services available from cubestech.
01 / Before you begin
A few essentials.
Then you are ready.
Your endpoint and key belong to your configured node. Keep development and production credentials separate, and never expose them in browser JavaScript.
Open your dashboard ↗- 01
Choose your service
Confirm your plan includes the interface and network you need.
- 02
Prepare your node
Complete account and node setup in your dashboard.
- 03
Protect your key
Store the node credential in a backend environment variable or secret manager.
- 04
Copy your endpoint
Copy the endpoint for your selected service—not the storefront address.
[02] Built for developers
Your stack.
A clear path to the data.
Start with the endpoint and credential in your node dashboard. Follow a service-specific quickstart, make a small test request, and connect your application when you are ready.
Keep credentials in your backend or secret manager. Add timeouts, bounded retries, and reconnection handling before you put a consumer into production.
- Documented authentication and request formats
- Examples for the services available here
- Separate credentials for your environments
quickstart / rpcserver-side integration
request.shexample / RPC
# Keep NODE_API_KEY in your server environmentexport RPC_ENDPOINT="https://api.mainnet-beta.solana.com" curl "$RPC_ENDPOINT" \ -H "Content-Type: application/json" \ -H "x-api-key: $NODE_API_KEY" \ -d '{"jsonrpc":"2.0","id":1,"method":"getHealth"}'03 / Verify the connection
Know what success looks like.
A working connection is the first check. Validate the response or payload before you build on it.
WSS
WebSockets
Expect a subscription ID after subscribing, then notifications for matching changes. An open socket alone does not confirm a subscription.
Service guide ↗gRPC / TLS
gRPC
Confirm authentication, apply a narrow filter or permitted topic, and inspect the expected payload. A quiet filter may legitimately have no matching events.
Service guide ↗gRPC / TLS
Program & event streams
Confirm authentication, apply a narrow filter or permitted topic, and inspect the expected payload. A quiet filter may legitimately have no matching events.
Service guide ↗UDP
Shreds
Verify the destination challenge, then confirm your receiver is getting packets. Reconstruction and decoding happen in your consumer.
Service guide ↗Geyser
Geyser
Confirm the plugin configuration and expected output with the operator before running your consumer.
Service guide ↗04 / Make it production-ready
Handle the edges.
Not just the happy path.
- Set timeouts and bound your retry count.
- Monitor errors and usage without logging credentials.
- Test reconnects and shutdown behavior where applicable.
- Rotate exposed keys and remove old credentials safely.
Authentication
Check the node credential and the documented header or SDK token. Do not place your key in the URL or log it.
HTTP 429
Reduce request concurrency. Retry with bounded exponential backoff and jitter, then review your plan's request allowance.
Invalid request
Check the method, parameters, network, and JSON-RPC error body. Do not repeatedly retry an invalid request.
Stream disconnected
Handle keepalives and reconnects. Restore your subscription or filters after reconnection and close unused connections.
No UDP packets
Check the registered destination, reachable UDP port, firewall rules, and receiver verification. Confirm your plan includes a destination.