[!WARNING] The old
/api/endpoints switch off on 9 November 2026. Until then both APIs run side by side, and your existing API key works on both.
What you need to do
- Keep your key. The host (
https://api.taostats.io), the key and the header (Authorization: <your key>, noBearerprefix) are all unchanged. - Switch your paths from
/api/to/v1/. The version comes first, the/apiprefix goes, names are plural, and sorting splits intoorder_byandorder_dir. - Run your calls and read any
400. The new API is stricter than the old one, and every error message names the parameter at fault and lists what the endpoint accepts.
Here is the same request on both APIs:
bash
# Old API: switches off 9 November 2026
curl -H "Authorization: $TAOSTATS_API_KEY" \
"https://api.taostats.io/api/transfer/v1?order=amount_desc&limit=10"
# New API
curl -H "Authorization: $TAOSTATS_API_KEY" \
"https://api.taostats.io/v1/transfers?order_by=amount&order_dir=desc&limit=10"The migration guide maps every old endpoint to its replacement. We checked each pair by calling both APIs and comparing the answers field by field.
| Period | Old API (/api/…) | New API (/v1/…) |
|---|---|---|
| 8 Oct – 9 Nov 2026 | Live | Live |
| From 9 Nov 2026 | Switched off | Live |
| Feature | What it means for you |
|---|---|
| Rust and ClickHouse | History queries come back fast, because ClickHouse is built to scan years of chain data. |
| The whole timeline, done right | Bittensor has been through runtime upgrades, migrations and storage format changes. A figure from 2023 and a figure from today are now calculated the same way. |
| Live chain reads | Some fields come straight from the chain at the finalized head, such as root_basket_claimable_tao on /v1/accounts/{address}. |
| A full OpenAPI spec | Every endpoint, parameter and sort option is in openapi.json, so you can generate a client from it. |
| Clear empty values | null means unknown and means zero, so a failed read never looks like an empty balance. |
[!TIP] Migrating with an AI agent? Give it the plain-text migration guide and the OpenAPI spec. Together they cover every old path, its replacement, and every parameter the new API accepts.
Start with the migration guide, then look up anything else in the API reference. Your keys are on the API keys page, and the one you have already works. If you get stuck, ask us on Discord.
