API migration

The focused routes make every displayed parameter valid for its endpoint. Earlier combined read and token-metadata forms remain available during migration and return Deprecation and Link response headers. The earlier combined claim-write route is retired; use the matching focused claim route.

Route replacements

Existing request	Focused route
`GET /tokens?q=...`	`GET /tokens/search?q=...`
`GET /tokens?creator=...`	`GET /creators/{address}/tokens`
`GET /tokens/{chain}/{token}/activity?kind=trades`	`GET /tokens/{chain}/{token}/trades`
`GET /tokens/{chain}/{token}/activity?kind=announcements`	`GET /tokens/{chain}/{token}/announcements`
`GET /wallets/{address}/claims?kind=fee`	`GET /wallets/{address}/fee-claims`
`GET /wallets/{address}/claims?kind=vesting`	`GET /wallets/{address}/vesting`
Retired `POST /claims/prepare` with `kind=fee`	`POST /claims/fees/prepare`
Retired `POST /claims/prepare` with `kind=vesting`	`POST /claims/vesting/prepare`
`POST /tokens/{chain}/{token}/metadata/prepare` with `update_name`, `update_symbol`, or `update_extra_metadata`	`POST /tokens/{chain}/{token}/metadata/onchain/prepare`
`POST /tokens/{chain}/{token}/metadata/prepare` with `update_profile`	`POST /tokens/{chain}/{token}/metadata/document/prepare`
`POST /tokens/{chain}/{token}/metadata/profile/prepare`	`POST /tokens/{chain}/{token}/metadata/document/prepare`

Token browsing now uses self-contained sort values: newest, oldest, trending, liquidity, market_cap, or volume_24h. Do not send a separate order parameter. Metadata-document preparation removes the operation field. Send actor and document directly and continue supplying Idempotency-Key. No sunset date is currently announced. Integrations should migrate to the focused routes so unsupported parameter combinations cannot be constructed.

Overview

Create a token

Liquidity and fees

How the platform works

API

Developers

Reference

Route replacements

​Route replacements

Route replacements