Solana archival JSON-RPC passthrough
Transparent JSON-RPC 2.0 passthrough to an archival (“historical”) Solana RPC, for queries that
need state older than a standard node retains — e.g. getTransaction, getSignaturesForAddress
or getBlock against old slots.
The request body is forwarded verbatim and the upstream response is returned verbatim, so this accepts anything the upstream accepts. Point a Solana client straight at this URL.
Upstream behaviour worth knowing (all relayed to you unchanged, not imposed by us):
- Batches are supported — send an array — but every request in one batch must use the same
method. A mixed-method batch returns
-32602 Invalid params. - The archival endpoint serves a subset of Solana RPC. An unsupported method returns
-32601 Method not foundwith HTTP 403. - Archival queries are slow: a simple call is typically 5-8s, and the upstream occasionally
stalls. Requests are given 60s before we give up and return
504. Set client timeouts accordingly and retry on504.
Requires an active Premium or Enterprise API key. Usage counts against your plan’s rate limit.
Body
A JSON-RPC 2.0 request object, or an array of them for a batch.
- object
- object[]
The body is of type object.
Response
Upstream response, passed through unchanged.
The response is of type object.