Skip to content
TAO$188.36
BTC0.002929
MCap$2.22B
Vol$86.25M

Using the API

API changelog

Every change to /api/v2 that you code against, newest first: new and changed fields, deprecations with their sunset dates, and route changes.

How changes are announced

  1. One entry per change you code against: a version bump, an additive or breaking change to a response, a route change, or a deprecation. Correcting a wrong value is not an entry.
  2. Each entry has a kind: additive, breaking, deprecation or route. Breaking means code written for the previous version would read the new one differently without being changed.
  3. An entry's date is the day its notice period starts.
  4. Entries contain no addresses, keys or per-account data.
  5. Additive changes can ship at any time, including a new value in an open list of values. A renamed field, a change of meaning, a removal or a narrower type ships next to the old field: the old one stays, marked deprecated with its sunset date, for at least 90 days from its entry here. An endpoint is removed only after at least 6 months' notice here. Operations and response fields marked x-stability: beta can change incompatibly with one release's notice: the entry for release N announces the change, which ships in N+1 or later.

A response's meta.data_version names its family and the version it serves, such as account/19. How deprecations show up in the spec and in response headers is under Versioning.

Baseline

Baseline: API 1.164.0

  • What changes: nothing. This is the starting point the rules above apply from: the public /api/v2 surface as served by API 1.164.0, 204 documented operations. An operation documented later is listed in its own entry the day it is announced. Each response's meta.data_version names its family and version; the table below lists the version each family serves and its routes. Later entries record changes against it.

  • Errors: every error is application/problem+json: a Problem object with type, title, status, detail, code, request_id, errors (more members per code, as the served document states). code is an open vocabulary: the served document's x-error-catalogue lists each code with its status, meaning and whether a retry can succeed (239 codes at 1.164.0); new codes may be added, so show an unknown one with detail.

  • Deprecated members (50): served now, marked deprecated in the served document with sunset 2027-02-15, and removed no earlier than that. Use the replacement named:

    Show the list
    • AccountColdkeySwapAnnouncement.announced_at_block: use executable_at_block (account)
    • AccountIncomePosition.locked_alpha_rao: use AccountDetail.subnet_locks (account)
    • AccountIncomePosition.locked_alpha_rao: use AccountPositionsMeta.subnet_locks (account_positions)
    • AccountPosition.locked_alpha_rao: use Account.subnet_locks (accounts)
    • AccountPosition.locked_alpha_rao: use AccountPositionsItem.subnet_locks (accounts_positions)
    • BasketsValidatorMeta.missing_reason: use validator_unavailable_reason (baskets)
    • Candle.carried: use is_carried (subnet_candles, subnets)
    • EvmAddressApprovalsMeta.fold_height: use computed_through_height (evm_token_allowances)
    • EvmAddressNftsMeta.fold_height: use computed_through_height (evm_nfts)
    • EvmAddressTokenBalance.price_null_reason: use price_unavailable_reason (evm_token_balances)
    • EvmAddressTokenBalance.value_null_reason: use value_unavailable_reason (evm_token_balances)
    • EvmAddressTokenTransfersMeta.fold_height: use computed_through_height (evm_token_transfers)
    • EvmAddressTokensMeta.fold_height: use computed_through_height (evm_token_balances)
    • EvmTaoCoverage.stage: use dataset (evm_tao_daily, evm_tao_holders)
    • EvmTaoDailyMeta.days_not_built: use days_unavailable (evm_tao_daily)
    • EvmTokenDetail.folded_supply_raw: use computed_supply_raw (evm_tokens)
    • EvmTokenDetail.price_null_reason: use price_unavailable_reason (evm_tokens)
    • EvmTokenDetailMeta.fold_height: use computed_through_height (evm_tokens)
    • EvmTokenHeader.folded_supply_raw: use computed_supply_raw (evm_nfts, evm_token_holders, evm_token_transfers)
    • EvmTokenHolder.share_of_supply_null_reason: use share_of_supply_unavailable_reason (evm_token_holders)
    • EvmTokenHoldersMeta.fold_height: use computed_through_height (evm_token_holders)
    • EvmTokenListItem.folded_supply_raw: use computed_supply_raw (evm_tokens)
    • EvmTokenListItem.price_null_reason: use price_unavailable_reason (evm_tokens)
    • EvmTokenNftsMeta.fold_height: use computed_through_height (evm_nfts)
    • EvmTokenTransfersMeta.fold_height: use computed_through_height (evm_token_transfers)
    • EvmTokensCoverage.stage: use dataset (evm_nfts, evm_token_allowances, evm_token_balances, evm_token_holders, evm_token_transfers, evm_tokens)
    • EvmTokensListMeta.fold_height: use computed_through_height (evm_tokens)
    • HotkeyEmission30d.days_built: use days_available (account, hotkey, validators)
    • HotkeyEmission30d.other_spot_tao_rao: use owner_cut_spot_tao_rao (account, hotkey, validators)
    • LifeSummaryData.page: use profile (subnet_life_summary)
    • PortfolioRootAccrualEra.built: use available (portfolio_series)
    • PortfolioSeriesDay.total_ex_basket_spot_tao_rao: use total_spot_tao_rao (portfolio_series)
    • RegistrationActivityRow.cost_pct_reason: use cost_percentiles_unavailable_reason (registration_analytics)
    • RegistrationCostRow.cost_pct_reason: use cost_percentiles_unavailable_reason (registration_analytics)
    • RegistrationTenureRow.tenure_pct_reason: use tenure_percentiles_unavailable_reason (registration_analytics)
    • SearchMeta.index_built_at: use index_updated_at (search)
    • StatusReadDelay.replica_replay_time: use data_as_of (coverage)
    • Subnet.owner_buyback_30d_alpha_rao: use owner_pool_buys_30d_alpha_rao (subnets)
    • Subnet.owner_buyback_30d_tao_rao: use owner_pool_buys_30d_tao_rao (subnets)
    • Subnet.owner_buyback_lifetime_alpha_rao: use owner_pool_buys_lifetime_alpha_rao (subnets)
    • Subnet.owner_buyback_lifetime_from_height: use owner_pool_buys_lifetime_from_height (subnets)
    • Subnet.owner_buyback_lifetime_tao_rao: use owner_pool_buys_lifetime_tao_rao (subnets)
    • Subnet.owner_buyback_share_of_owner_cut_30d_ratio: use owner_pool_buys_share_of_owner_cut_30d_ratio (subnets)
    • Subnet.page: use profile (subnets)
    • SubnetNetEmissionWindow.days_built: use days_available (subnet_life_summary, subnet_net_emission, subnets)
    • SubnetPage.owner_buyback_30d_alpha_rao: use owner_pool_buys_30d_alpha_rao (subnets)
    • SubnetPage.owner_buyback_30d_tao_rao: use owner_pool_buys_30d_tao_rao (subnets)
    • SubnetPage.owner_buyback_lifetime_alpha_rao: use owner_pool_buys_lifetime_alpha_rao (subnets)
    • SubnetPage.owner_buyback_lifetime_from_height: use owner_pool_buys_lifetime_from_height (subnets)
    • SubnetPage.owner_buyback_lifetime_tao_rao: use owner_pool_buys_lifetime_tao_rao (subnets)
    • SubnetPage.owner_buyback_share_of_owner_cut_30d_ratio: use owner_pool_buys_share_of_owner_cut_30d_ratio (subnets)
    • SubnetPage.page: use profile (subnets)
  • Routes with no data_version (4): integration feeds in a third party's format; the route promise covers them like any other:

  • Stability: each operation's x-stability in the served document says which notice in rule 5 applies: 70 operations are stable and 134 beta, and response members are marked x-stability: beta there too. The table's Stability column gives each family's value, and marks each route where a family's routes differ.

Families, their data_version and routes (162)

The changelog of record, export v0.2.67.