Skip to main content

Getting Your API Key

1

Subscribe to Service

Subscribe to the standalone gRPC service at €200/month, or get it bundled free with RPC Business and Professional plans. See Pricing & Limits for details.You get access to:
  • EU endpoint: https://grpc.solanatracker.io
  • US endpoint: https://grpc-us.solanatracker.io
  • Accelerated by Jito Shreds
  • No bandwidth charges
2

Receive Credentials

After subscription, you’ll receive:
  • Your API token
  • Endpoint URLs
  • Configuration guidelines
3

Test Connection

Verify your credentials work by creating a simple test connection

Authentication Methods

Header-Based Authentication

Add your API token to the request headers:
string
required
Your API token for authenticating gRPC requests

Client Configuration

TypeScript/JavaScript

Rust

Go

Endpoint Selection

Choose the endpoint that provides the best latency for your infrastructure:

Primary Endpoint

https://grpc.solanatracker.io
  • Best for global applications
  • Automatic routing
  • High availability

US Endpoint

https://grpc-us.solanatracker.io
  • Optimized for North America
  • Lower latency for US-based apps
  • Direct US routing
Test both endpoints and use the one with lower latency from your deployment region.

Configuration Best Practices

Message Size Limits

Set appropriate message size limits to handle large blocks and transaction batches:

Keepalive Settings

Configure keepalive to maintain persistent connections:

Connection Timeouts

Set reasonable timeout values:

Testing Your Connection

Create a simple test to verify your setup:

Troubleshooting

Error: UNAUTHENTICATED or Invalid tokenSolutions:
  • Verify your API token is correct
  • Check token is properly set in headers
  • Ensure subscription is active
Error: Connection times out or fails to establishSolutions:
  • Verify endpoint URL is correct (include https://)
  • Check firewall allows outbound gRPC connections
  • Try alternative endpoint
  • Increase connection timeout settings
Error: RESOURCE_EXHAUSTED or message size errorsSolutions:
  • Increase max_receive_message_length to 64MB
  • Increase max_send_message_length to 64MB
  • Use data slicing to reduce message sizes
  • Apply more specific filters

Security Best Practices

Protect Your API Token
  • Never commit tokens to version control
  • Use environment variables for tokens
  • Rotate tokens periodically
  • Implement token management system

Environment Variables

Store your credentials securely:

Next Steps

Quickstart Guide

Build your first streaming application

Account Monitoring

Learn to monitor account changes