---
title: "RAVN's listed token registry for one chain"
method: GET
path: "/api/v1/tokens"
tags: ["Tokens"]
---

# RAVN's listed token registry for one chain

`GET /api/v1/tokens`

## Request

- Base URL: `https://app.ravn.exchange`
- URL: `https://app.ravn.exchange/api/v1/tokens`
- Auth: one of:
  - API key in header `x-api-key`
  - none

Not every route or venue supports every listed token here — this is what RAVN knows about and might route, the same source retail's own token picker reads from, not a routability guarantee for a specific pair (get a quote to actually check that). See /v1/tokens/btc-coverage for the narrower BTC-source question.

## Query parameters

- `chainId` 1 | 10 | 56 | 130 | 137 | 324 | 480 | 999 | 143 | 8453 | 42161 | 59144 | 43114 | 4663 | 4217 | -1 | -2, required

## Response `200`

Tokens listed

- object
  - `data` TokenDTO[]
    - `symbol` string, required
    - `name` string, required
    - `address` string, required
    - `decimals` number, required
    - `chainId` number, required
    - `isNative` boolean, required
    - `logoUrl` string
  - `meta` Meta
    - `requestId` string, required
    - `version` string, required

## Other responses

- `400`: Invalid request / unsupported chain
- `401`: x-api-key present but invalid

---

[API](https://skmtc.dev/ravn/apis/ravn-swap-api.md) · [All operations](https://skmtc.dev/ravn/apis/ravn-swap-api/llms.txt) · [OpenAPI document](https://skmtc.dev/ravn/apis/ravn-swap-api/revisions/f1c5a0c63392?raw)