# The New Taostats API

The new Taostats API launches October 8. It's a ground-up rebuild: written entirely in Rust and backed 100% by ClickHouse. It's faster, lighter, and handles years of historical chain quirks correctly.

_Source: https://taostats.io/blog/taostats-new-api-launch_  
_Author: Doug Sillars, Head of Community and Education_  
_Published: 2026-10-08_  
_Category: Annonces_

> [!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

1. Keep your key. The host (`https://api.taostats.io`), the key and the header (`Authorization: <your key>`, no `Bearer` prefix) are all unchanged.
2. Switch your paths from `/api/` to `/v1/`. The version comes first, the `/api` prefix goes, names are plural, and sorting splits into `order_by` and `order_dir`.
3. 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](https://taostats.io/blog/api-migration-guide) maps every old endpoint to its replacement. We checked each pair by calling both APIs and comparing the answers field by field.

## Timeline

| Period | Old API (`/api/…`) | New API (`/v1/…`) |
| --- | --- | --- |
| 8 Oct – 9 Nov 2026 | Live | Live |
| From 9 Nov 2026 | Switched off | Live |

## What's new for you

| 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`](https://api.taostats.io/openapi.json), so you can generate a client from it. |
| Clear empty values | `null` means unknown and `"0"` means zero, so a failed read never looks like an empty balance. |
| 124 endpoints | Blocks, extrinsics, events, accounts, subnets, validators, baskets, miners, tax and EVM, plus TradingView, CoinGecko and CoinMarketCap feeds. |
| JSON-RPC proxy | Send raw RPC calls to Bittensor lite and archive nodes through the same host and key. |

> [!TIP]
> Migrating with an AI agent? Give it the plain-text [migration guide](https://taostats.io/blog/api-migration-guide.md) and the [OpenAPI spec](https://api.taostats.io/openapi.json). Together they cover every old path, its replacement, and every parameter the new API accepts.

## Get started

Start with the [migration guide](https://taostats.io/blog/api-migration-guide), then look up anything else in the [API reference](https://taostats.io/docs/new). Your keys are on the [API keys](https://taostats.io/pro/api-keys) page, and the one you have already works. If you get stuck, ask us on [Discord](https://discord.taostats.io).