CoinGecko DEX feed: swap events in a block range
https://api.bittensor.ai/api/v2/integrations/coingecko/events- Status
- Beta
- Auth
- API key or OAuth access token
- Scope
data:read- Rate limit
plan
{events: [...]}: every swap on a subnet pool (a buy, TAO in and alpha out, or a sell, alpha in and TAO out) in blocks fromBlock..toBlock (inclusive, at most 1000 blocks), by block then event index.
Full description
{events: [...]}: every swap on a subnet pool (a buy, TAO in and alpha out, or a sell, alpha in and TAO out) in blocks fromBlock..toBlock (inclusive, at most 1000 blocks), by block then event index. Each event names its block (blockNumber, blockTimestamp), the pair 0-<netuid>, the coldkey (maker), the amounts in whole tokens (the side not traded null), priceNative (alpha per TAO) and the pool's reserves after the block (the alpha reserve derived from the TAO reserve and the price). Swaps between subnets, basket rows, registrations, fee swaps and root (netuid 0) are not events. A range past /latest-block answers the blocks up to it. The genesis block (0) holds no swap: fromBlock=0&toBlock=0 is {events: []}, and a range from 0 is read from block 1. Cached as settled once every block of the range is final and its fee swaps classified (a fee paid in alpha reads as a sell until then); otherwise tip-cached. Errors are application/problem+json: INVALID_HEIGHT, INVALID_RANGE (toBlock below fromBlock), RANGE_TOO_LARGE (over 1000 blocks, or over 10000 swaps in the range: ask a narrower one), OUT_OF_COVERAGE (fromBlock before the first block the feed covers), UNKNOWN_PARAMETER, SOURCE_TIMEOUT (503), SOURCE_NOT_READY (503). External format: the 200 is CoinGecko's DEX integration's own wire format, not this API's {data, meta} envelope (member names, casing and number encoding are CoinGecko's DEX integration's); authentication, rate limits, metering and problem+json errors are this API's.
Beta: this route may change with one release's notice in the v2 changelog; additive changes need none (x-stability: beta).
Query parameters
- fromBlockquery, required· integer · 0 to 4294967295
The first block, inclusive. Not a block height: 400
INVALID_HEIGHT.- toBlockquery, required· integer · 0 to 4294967295
The last block, inclusive. Not a block height: 400
INVALID_HEIGHT.
Response headers
10 headers: ETag, Cache-Control, CDN-Cache-Control, X-BTAI-Stale, X-BTAI-Stale-As-Of, RateLimit-Policy, RateLimit, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset
- ETag
Strong validator of this answer. Send it back as
If-None-Match: an unchanged answer is a 304 Not Modified without a body. A settled answer's validator leaves the chain head out, so it stays valid as the head moves.- Cache-Control
One of three classes: settled
public, max-age=3600, stale-while-revalidate=86400(pinned to a block that cannot move), slowpublic, max-age=300, stale-while-revalidate=600(state that moves in minutes or days) or tippublic, max-age=6, stale-while-revalidate=12(follows the chain head); the label routes are cached until the next nightly copy (public, max-age=<seconds>, stale-while-revalidate=60). Neverimmutable.no-storeon an earlier answer served because the data source failed (X-BTAI-Stale).- CDN-Cache-Control
The same class for shared caches (RFC 9213; browsers ignore it): settled 24 h, slow 300 s, tip 6 s, each with
stale-while-revalidateandstale-if-error;no-storewithX-BTAI-Stale.- X-BTAI-Stale
Present only when the data source failed to answer (it timed out or was unavailable) and an earlier answer to the same request is served instead of a 503 (stale if error, RFC 5861). Then
if-error, withX-BTAI-Stale-As-Of,Age(its seconds since then) andWarning: 110 - "Response is Stale", andCache-Control: no-store: the answer is never kept as fresh, and a later request reads again. Prices and quotes are never served this way.- X-BTAI-Stale-As-Of
With
X-BTAI-Stale: when the earlier answer served was produced, an RFC 3339 UTC time (2026-10-21T12:00:00Z).- RateLimit-Policy
The tier's request quota of the current window (IETF draft), e.g.
"tier";q=600.- RateLimit
Requests left in the current window and the seconds until it resets (IETF draft), e.g.
"tier";r=597;t=42.- X-RateLimit-Limit
The tier's request quota of the current window.
- X-RateLimit-Remaining
Requests left in the current window.
- X-RateLimit-Reset
When the current window resets, Unix seconds.
Status codes
200 · 304 · 400 · 401 · 402 · 403 · 404 · 429 · 500 · 502 · 503
304 Not Modified: the If-None-Match validator still matches; no body.
Error codes
The codes this endpoint can return. Each links to what it means and what to do.
- AMBIGUOUS_CREDENTIALS
- BAD_GATEWAY
- BILLING_UNAVAILABLE
- BUDGET_EXCEEDED
- CONCURRENCY_LIMIT
- INSUFFICIENT_PERMISSIONS
- INTERNAL_ERROR
- INVALID_HEIGHT
- INVALID_RANGE
- OUT_OF_COVERAGE
- PAYMENT_REQUIRED
- RANGE_TOO_LARGE
- RATE_LIMITED
- REPEATED_PARAMETER
- SERVICE_UNAVAILABLE
- SOURCE_BUSY
- SOURCE_NOT_READY
- SOURCE_TIMEOUT
- UNAUTHORIZED
- UNKNOWN_PARAMETER
- VALIDATION_ERROR
From the API's published specification, version 1.165.0.