Guide
Authentication & endpoints
Every request is authenticated with an API key. RPC and Data API use separate keys.
Endpoints & where the key goes
| Service | Endpoint | Key |
|---|---|---|
| RPC (HTTP) | https://solrpc.infinityblocks.io/<API_KEY> | in the URL path (also ?api-key= / x-api-key) |
| RPC (WebSocket) | wss://solrpc.infinityblocks.io/<API_KEY> | in the URL path |
| Data API (REST) | https://solindex.infinityblocks.io/v1 | header x-api-key: <API_KEY> (also ?api-key=) |
Rate limits
50 requests/second per key. Exceeding it returns 429 Too Many Requests — back off and retry. Need a higher limit? Ask the operator.
Errors
Errors are JSON: { "error": "…" } (RPC errors follow the standard JSON-RPC error shape). Status codes:
| Code | Meaning |
|---|---|
400 | Bad request — invalid mint/wallet, bad query param. |
401 | Missing or invalid API key. |
403 | RPC method not supported on this node (see Solana RPC). |
404 | Unknown route / resource not found. |
429 | Rate limit exceeded. |
502 | Upstream node/database error — retry shortly. |
Conventions
- Data API responses are wrapped in
{ "data": … }. - Token amounts are returned in human units (decimals applied), prices in USD.
- Timestamps are unix milliseconds.