Get Snapshots
GET/v1/cryptodata/backtesting/snapshots
Query historical JSON snapshots for a data type. Streamed row-by-row so peak memory stays ~one row regardless of ``limit``. A limit=1000 pull of fat types (coinglass_oi / coinglass_funding / stablecoins) otherwise decompressed ~300MB and ballooned ~1GB through serialization, OOM-looping the 2.5GiB container. The JSON response shape is unchanged, so consumers need no changes. Streaming also means bytes start flowing immediately — no more 60s nginx 504 on large pulls. No heavy-read semaphore needed here: memory is now bounded by the stream itself, and the request rate is bounded by nginx/Cloudflare on the /backtesting route.
Price
$0.01/ callEdge cache
Off
Uptime 24h
100.00%
p95
991ms
Parameters
| Name | In | Type | Description |
|---|---|---|---|
| data_type* | query | string | Snapshot type, e.g. market_health, fear_greed, coinglass_etf_flows |
| start* | query | string | Start time (ISO 8601 or unix ms) |
| end | query | string | End time (ISO 8601 or unix ms, defaults to now). EXCLUSIVE — the range is [start, end), so consecutive windows do not repeat a boundary row. |
| bounds | query | string = half-open | Interval convention for `start`/`end`. `half-open` (default) is [start, end) — `end` is EXCLUSIVE, so consecutive windows tile without repeating a boundary row. `closed` is [start, end] — `end` INCLUSIVE, the pre-2026-08-08 behaviour; use it only to keep an existing integration byte-identical. |
| limit | query | integer = 100 | |
| universe | query | string | For dex_trending: filter to hl_perps |
Code
# 1. No key, no payment: the gateway answers 402 with the price
curl -i "https://api.realtimeapi.ai/v1/cryptodata/backtesting/snapshots?data_type=altcoin_breadth&start=2026-10-28"
# 2. Pay: retry with a signed x402 payment (any x402 client builds this header)
curl "https://api.realtimeapi.ai/v1/cryptodata/backtesting/snapshots?data_type=altcoin_breadth&start=2026-10-28" -H "PAYMENT-SIGNATURE: $X402_PAYMENT"// npm i @x402/fetch @x402/core @x402/evm viem
import { wrapFetchWithPayment } from "@x402/fetch";
import { x402Client } from "@x402/core/client";
import { ExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
const client = x402Client.fromConfig({ schemes: [{ network: "eip155:8453", client: new ExactEvmScheme(privateKeyToAccount(PRIVATE_KEY)) }] });
const pay = wrapFetchWithPayment(fetch, client);
const data = await (await pay("https://api.realtimeapi.ai/v1/cryptodata/backtesting/snapshots?data_type=altcoin_breadth&start=2026-10-28")).json();
console.log(data);# pip install x402 eth-account requests
from eth_account import Account
from x402.clients.requests import x402_requests
session = x402_requests(Account.from_key(PRIVATE_KEY))
print(session.get("https://api.realtimeapi.ai/v1/cryptodata/backtesting/snapshots?data_type=altcoin_breadth&start=2026-10-28").json())curl "https://api.realtimeapi.ai/v1/cryptodata/backtesting/snapshots?data_type=altcoin_breadth&start=2026-10-28" -H "X-API-Key: $RTAPI_KEY"Frequently asked questions
How do I get get snapshots from CryptoDataAPI?
Send GET https://api.realtimeapi.ai/v1/cryptodata/backtesting/snapshots. Pay $0.01 per request with x402, or send an X-API-Key header.
What does GET /backtesting/snapshots cost?
$0.01 per successful request in USDC on Base. Failed requests are never charged.
Can I call this endpoint from an MCP client?
Yes. Connect any MCP client to the RealtimeAPI server and use call_feed with this endpoint's URL, or get_quote to check the price first.