---
title: "GET /api/v1/symbols"
method: GET
path: "/api/v1/symbols"
tags: ["v1"]
---

# GET /api/v1/symbols

`GET /api/v1/symbols`

## Request

- Base URL: `https://api.blackforge.so` (the document declares no server; this is the origin it was published from)
- URL: `https://api.blackforge.so/api/v1/symbols`
- Auth: API key in header `x-api-key`

## Query parameters

- `exchange` string, required

## Response `200`

Distinct symbols traded on one venue, ordered alphabetically, as a flat array of strings. Gated by the key plan (an unentitled venue returns 403); metadata only, not metered. KRAKEN ALIASES: kraken spells bitcoin XBT and dogecoin XDG, so this list also contains the BTC/DOGE spellings of those pairs (BTCUSD alongside XBTUSD, ETHBTC alongside ETHXBT) and both spellings are accepted as the `symbol` of any data request. LIMITS: the responses always echo the spelling YOU sent, never a rewritten one, and the `quoteAsset` COLUMN still reads "XBT" on the kraken pairs quoted in bitcoin. This is a single venue renaming two assets and nothing more: it does NOT make one symbol string work across venues, because the nine venues use three different separator conventions (dash on coinbase/kucoin/okx, underscore on gate, none elsewhere).

---

[API](https://skmtc.dev/blackforge/apis/blackforge-data-api.md) · [All operations](https://skmtc.dev/blackforge/apis/blackforge-data-api/llms.txt) · [OpenAPI document](https://skmtc.dev/blackforge/apis/blackforge-data-api/revisions/04eadd230b1b?raw)