What an extrinsic changed in storage
https://api.bittensor.ai/api/v2/extrinsics/{id_or_hash}/changes- Status
- Stable
- Auth
- API key or OAuth access token
- Scope
data:read- Rate limit
plan
The storage entries the extrinsic changed, one row per entry, netted over the extrinsic.
Full description
The storage entries the extrinsic changed, one row per entry, netted over the extrinsic (ExtrinsicChangesResponse): the item, the key (named fields, accounts SS58), what happened (created, removed, set), the value before its first write and after its last write that was not rolled back (stored bytes, their exact decoding and whether they decoded: decoded false is an entry present but not decodable, null where the entry is absent), the unit of a numeric value, how many writes there were and how many were rolled back, and the calls that made them. An entry whose final value equals the one before is not listed. Rows by item, then key, with a dense 1-based position and an exact meta.page.total; pages continue through meta.page.next_cursor. include=all_writes answers one row per write instead, in execution order (ExtrinsicWritesResponse, meta.data_version extrinsic_writes/...): its sequence number, the item and key, put or kill, the value before and after that write, whether it was rolled back, its phase (fee, dispatch, refund) and its call. system (default false) hides the runtime's bookkeeping (block weight, event counters, extrinsic data and the other per-extrinsic system entries) and the writes made before or after dispatch, except the fee payer's (which can differ from the signer: proxy real-pays), kept with item.class fee: its balance entry (the transaction fee debit and any refund) or, for a fee paid in alpha, its alpha position; system=true shows every write. call (a call id of this extrinsic, e.g. 9185000-14.1) keeps the writes made inside that call and its children only; a failed extrinsic's rolled-back dispatch writes carry their call too, so call with include=all_writes lists them. item (Pallet.Item, a comma list) keeps the changes to those storage items. Alpha positions in alpha: an Alpha / AlphaV2 row (pool shares) carries alpha_before_rao / alpha_after_rao, the shares sized against the pool's totals changed by the same extrinsic, or null with alpha_unavailable_reason. Numeric values carry their unit, the same as GET /storage/{pallet}/{item}. meta.attribution: full, or none for a block whose trace format never recorded write phases or calls (older blocks, below 9,000,001 here): then no fee class, no call ids, no phase, system=false hides only the bookkeeping items, and call is a 400 CALL_ATTRIBUTION_UNAVAILABLE. A recent block whose writes do not carry their phases yet is a 503 NOT_READY (extension member phases_through_height: the height phases are written through, to poll on; never cached), and a block whose writes are not indexed a 404 CHANGES_NOT_INDEXED. An extrinsic at or below meta.at is final, so its pages are cached as settled. Ids: an extrinsic or an event is {height}-{index}, a call {height}-{extrinsic index} then .{child} per level (9190000-5.0.1); leading zeros are dropped. Anything else is a 400 INVALID_ID. Earlier id forms are accepted too: zero-padded (0009190000-000005), and on /calls/{id} the call ids {height}-{extrinsic}-{n} (an executed call; n counts the extrinsic's executed calls in postorder, not a position:0009190005-000006-000001 is 9190005-6.1) and {height}-{extrinsic}-s{path} (a never-dispatched call: 0009155314-000010-s000000.000003 is 9155314-10.0.3). The answer is the canonical id's, and a Content-Location header names the canonical URL whenever the path's id was not in canonical form (no redirect). Errors are application/problem+json: INVALID_ID (the path, or a malformed call), INVALID_CALL (a call of another extrinsic), CALL_ATTRIBUTION_UNAVAILABLE (a call on a block without per-call attribution), INVALID_BOOLEAN, INVALID_INCLUDE, INVALID_STORAGE_ITEM (item), TOO_MANY_CHANGES (item on an extrinsic with too many changes), INVALID_LIMIT, INVALID_CURSOR, CHANGES_NOT_INDEXED (404), EXTRINSIC_NOT_FOUND (404; asked by hash, an extrinsic not seen yet carries extension member indexed_through_height, the newest finalized block processed: a later retry may find it), EXTRINSIC_OUT_OF_COVERAGE (404, below meta.coverage.from_height while earlier history is still being prepared), EXTRINSIC_NOT_YET_INDEXED (404, above the indexed head; extension members head_height and indexed_through_height), AMBIGUOUS_HASH (409: more than one extrinsic has this hash; extension member candidates, their ids, oldest first: ask by id), NOT_READY (503, the block's write phases are not written yet; extension member phases_through_height), UNKNOWN_PARAMETER, SOURCE_TIMEOUT (503), SOURCE_NOT_READY (503).
Path parameters
- id_or_hashpath, required· string
The extrinsic id,
{height}-{index}(e.g.9190000-5), or its hash, 0x + 64 hex (any case). A hash is a lookup alias: when several extrinsics share it, the answer is a 409AMBIGUOUS_HASHlisting their ids.
Query parameters
- systemquery· enum · one of true, false
true: every write, the runtime's bookkeeping included.false(the default): the bookkeeping is hidden, the fee payer's fee writes kept (item.classfee).trueorfalse(lower-case; anything else is a 400INVALID_BOOLEAN).- includequery· string
all_writes: one row per write, in execution order (rolled-back writes included), instead of one row per changed entry. Anything else is a 400INVALID_INCLUDE.- callquery· string
Only the writes made inside this call (and its children): a call id of this extrinsic,
{height}-{index}then.{child}per level. Malformed: a 400INVALID_ID; a call of another extrinsic: a 400INVALID_CALL; a block without per-call attribution (meta.attributionnone): a 400CALL_ATTRIBUTION_UNAVAILABLE.- limitquery· integer · default 100 · 1 to 1000
Page size, 1..1000 (default 100).
- cursorquery· string · up to 200 characters
meta.page.next_cursorof the previous page, passed back unchanged with the same other parameters. It is opaque and bound to them: a cursor used with different parameters, or altered, is a 400INVALID_CURSOR.- itemquery· string
Only the changes to these storage items:
Pallet.Item(e.g.SubtensorModule.TotalHotkeyAlpha), a comma list of at most 20 (OR), any case. The filter reads every change of the extrinsic and keeps the rows of those items, each at its ownposition;meta.page.totalcounts the rows kept and pages continue throughmeta.page.next_cursoras usual. On the net view the alpha amounts ofAlpha/AlphaV2rows are sized over every change of the extrinsic, so naming only those items still sizes them. A malformed entry is a 400INVALID_STORAGE_ITEM; an extrinsic with more changed entries than one request reads is a 400TOO_MANY_CHANGES.
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 · 409 · 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
- AMBIGUOUS_HASH
- BAD_GATEWAY
- BILLING_UNAVAILABLE
- BUDGET_EXCEEDED
- CALL_ATTRIBUTION_UNAVAILABLE
- CHANGES_NOT_INDEXED
- CONCURRENCY_LIMIT
- EXTRINSIC_NOT_FOUND
- EXTRINSIC_NOT_YET_INDEXED
- EXTRINSIC_OUT_OF_COVERAGE
- INSUFFICIENT_PERMISSIONS
- INTERNAL_ERROR
- INVALID_BOOLEAN
- INVALID_CALL
- INVALID_CURSOR
- INVALID_ID
- INVALID_INCLUDE
- INVALID_LIMIT
- INVALID_STORAGE_ITEM
- NOT_READY
- PAYMENT_REQUIRED
- PLAN_REQUIRED
- RATE_LIMITED
- REPEATED_PARAMETER
- SERVICE_UNAVAILABLE
- SOURCE_BUSY
- SOURCE_NOT_READY
- SOURCE_TIMEOUT
- TOO_MANY_CHANGES
- UNAUTHORIZED
- UNKNOWN_PARAMETER
- VALIDATION_ERROR
From the API's published specification, version 1.165.0.