Get RPC endpoints for chains
GET/v1/data/rpcs
Returns RPC URLs for the requested chains.
Plain-text reference — GET /v1/data/rpcs
Parameters
| Parameter | In | Type | Required | Description |
|---|---|---|---|---|
chains | query | string[] | yes | Chain IDs to fetch RPCs for (repeatable) |
Response 200
| Field | Type | Description |
|---|---|---|
success | True | |
data | object | Chain ID to array of RPC URLs. Keys are chain IDs; values are arrays of RPC endpoint URLs. |
actions | null |
Example response
{
"success": true,
"data": {}
}
Request
Responses
- 200
- 400
- 404
- 429
- 500
- 502
RPC endpoints for requested chains
Validation error
None of the requested chains exist in the data
Rate limited. Unauthenticated callers share a per-IP budget; send an x-api-key header to lift it. Retry with exponential backoff.
Unexpected server error. Safe to retry with backoff.
An upstream data source or protocol origin failed (error.code is ORIGIN_FAILED). error.details carries the per-origin status. This is also what a missing or malformed required parameter currently returns, rather than a 400.