Skip to main content
Use the gRPC token from your RPC dashboard. gRPC authenticates with x-token; the Data API’s x-api-key header is a different interface.

Check your credentials

Install the dependencies and set the environment variables from the quickstart. Then save the following connection check as check-connection.mts.
check-connection.mts
A version response verifies the endpoint and token. Next, run the quickstart subscription to verify streaming access.

Choose a region

  • EU: https://grpc.solanatracker.io
  • US: https://grpc-us.solanatracker.io
Measure from your deployment host. Network distance, routing, processing time, and subscription load all affect delivery latency.

Troubleshoot connection errors

  • Unauthenticated: check that GRPC_API_TOKEN is set, contains no extra whitespace, and belongs to an active subscription.
  • Timeout or unavailable: verify the URL and outbound TLS/HTTP2 access; then try the other region.
  • Resource exhausted: inspect the error detail. Check connection allowances and message-size limits separately; increasing the receive limit does not fix a quota error.
  • Connected but no updates: start with blocksMeta: { blocks: {} }. Then reapply your filters one at a time.

Store the token

Read tokens from environment variables or your secret store. Keep them out of logs, client-side bundles, and committed examples. Restart or reconnect clients after rotating a token.

Quickstart

Reliability and performance