Migrate to v1.7

This guide moves a Token API integration from v1.2 or v1.3 to v1.7, the recommended version. Every endpoint you call on v1.2 and v1.3 still exists on v1.7; the changes are one new optional parameter, a wider chain list, and four added endpoints.

v1.2 and v1.3 are deprecated. The sunset date is the one the API publishes; check the Token API reference for the current status of each version.

What changes

GET /v1.7/{chainId}/trending-tokens and GET /v1.7/multi-chain/trending-tokens add an optional sortingMode parameter: standard sorts by 24-hour trading volume, safe puts tokens without a risk flag first and then sorts by volume. The default is safe.

Supported chains: 18 chains

GET /v1.7/multi-chain/supported-chains returns a JSON array of chain IDs: [1, 137, 10, 56, 42161, 43114, 100, 324, 8453, 59144, 146, 130, 501, 4663, 143, 25, 999, 5042]. v1.2 returns 10 of those chains and v1.3 returns 11, in the same array shape.

More chains

The aggregate endpoints GET /{version}/multi-chain, GET /{version}/multi-chain/token-list and GET /{version}/multi-chain/trending-tokens include tokens for every chain the version supports, so they return more data on v1.7. Search matches tokens only on the version's own chain set: GET /{version}/search and GET /{version}/{chainId}/search on v1.2 and v1.3 do not return tokens from the chains added later.

What does not change

Every other endpoint keeps the same path, parameters and response shape:

  • GET /{version}/multi-chain
  • GET /{version}/multi-chain/token-list
  • GET /{version}/multi-chain/trending-tokens (apart from the added sortingMode)
  • GET /{version}/search
  • GET /{version}/{chainId}
  • GET /{version}/{chainId}/custom
  • GET /{version}/{chainId}/custom/{address}
  • GET /{version}/{chainId}/search
  • GET /{version}/{chainId}/token-list
  • GET /{version}/{chainId}/trending-tokens (apart from the added sortingMode)

Endpoints added in v1.4

Four endpoints have no v1.2 or v1.3 equivalent. They exist from v1.4 onward, so v1.7 serves them too. They are additions, so nothing you already call needs to change:

  • GET /v1.7/{chainId}/pairs — trading pairs for a chain.
  • GET /v1.7/chipssearch and GET /v1.7/{chainId}/chipssearch — token search by chip, such as usd or defi.
  • GET /v1.7/{chainId}/chipssearch/pairs — pairs for the tokens a chip matches.

Migrate

  1. Replace the version segment in every request path: /v1.2/... or /v1.3/... becomes /v1.7/....
  2. Expect the aggregate endpoints to return tokens for the 18 chains.
  3. Re-run your test suite against v1.7 and compare the token payloads with what you store today.

Next steps

Did you find what you need?