- Socket.IO sends the token once in the connection handshake (
auth: { token }). - HTTP sends the token on every request in the
Authorizationheader, as the raw token with noBearerprefix.
Authentication Flow
- Obtain your API credentials (API URL and Auth Token)
- Provide the token: in the Socket.IO handshake, or in the HTTP
Authorizationheader - The server validates your token
- If valid, you can start making API requests
Connecting with Credentials
- Socket.IO
- HTTP
The token is validated once during the handshake.
Environment Variables
We recommend storing your credentials in environment variables:.env
- Socket.IO
- HTTP
Connection Events (Socket.IO)
These lifecycle events apply to the Socket.IO transport. HTTP is stateless and has no connection events, so handle errors per request from the response instead. Handle connection lifecycle events to ensure robust operation:Reconnection (Socket.IO)
Socket.IO automatically handles reconnection. You can configure the behavior:Security Best Practices
- Never expose tokens in client-side code - Use server-side proxies for browser applications
- Rotate tokens regularly - Contact us to regenerate compromised tokens
- Use environment variables - Never hardcode tokens in source code
- Monitor usage - Track API calls to detect unauthorized access
Rate Limits
API rate limits depend on your subscription tier. Contact us for details about rate limits and quotas.Next Steps
- Quick Start - Get started with your first request
- EVM Endpoints - Explore Ethereum, Base, and BSC endpoints
- SVM Endpoints - Explore Solana endpoints

