> For the complete documentation index, see [llms.txt](https://k4k3ru.gitbook.io/k4k3ru-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://k4k3ru.gitbook.io/k4k3ru-docs/api/market-hub/list-symbols.md). # List Market Symbols List the canonical symbols currently enabled for market-data venues. Omit the venue filter to query every venue that has enabled market metadata. Each venue is paginated independently, so you can control response size when querying multiple venues. ## Endpoint | Property | Value | | -------------- | ------------------------- | | URL | `https://api.k4k3ru.com/` | | HTTP method | `POST` | | RPC method | `MarketHub.ListSymbols` | | Authentication | Not required | ## Request ### Request Body This method uses the common [JSON-RPC request envelope](/k4k3ru-docs/api/json-rpc.md#request-envelope). Set `method` to `MarketHub.ListSymbols`. The `params` field is optional. When `params` is omitted or `null`, or when `venues` is omitted or empty, the method returns results for every venue that has enabled Spot or Perpetual market metadata. Default queries use page `1`, limit `100`, and include both market types for each venue. Venues without enabled market metadata are omitted, and results are ordered by venue name. ### Params Fields | Field | Type | Required | Description | | ---------------------- | ---------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `baseAsset` | string | No | Exact, case-sensitive canonical base asset, such as `PONS`. Omit or use an empty string to include all assets. | | `venues` | array | No | Venue queries. Omit this field or provide an empty array to query all venues with enabled market metadata. When specified, each venue may appear only once. | | `venues[].name` | string | Yes | Market-data venue. Currently supported: `binance`, `btse`, `bybit`, `coinbase`, `dydx`, `hyperliquid`, `okx`, and `uniswap-v4`. BTSE, Bybit, Coinbase, and OKX expose Spot and Perpetual markets; Uniswap v4 exposes Spot markets; dYdX currently exposes Perpetual markets only. | | `venues[].page` | number | No | One-based page number for this venue. Omit this field or use `0` to request page 1. | | `venues[].limit` | number | No | Maximum symbols returned for this venue. The default is `100`, and the maximum is `500`. Use `0` to select the default. | | `venues[].marketTypes` | array of strings | No | Include only these market types. Supported values are `spot` and `perp`. Omit the field to include both. Each value may appear only once. | Pagination is applied separately to each venue after the service filters by base asset and market type and orders canonical symbols in ascending lexical order. A symbol enabled for both requested market types appears once with both values in `marketTypes`. Coinbase uses one venue name across its supported public feeds. Spot symbols use USD quotes, while Perpetual symbols use USDC quotes. The enabled production configuration is discoverable through this method; a typical configuration includes `BTC/USD` and `ETH/USD` for Spot and `BTC/USDC` and `ETH/USDC` for Perpetual markets. An unknown base asset returns no matching symbols. Venues selected by the request (including all enabled venues when `venues` is omitted) remain in the response with `total: 0` and `symbols: []` when they have no matches. Matching uses the `BASE` component of `BASE/QUOTE`, not a prefix or quote-asset match. ### Example Request by Base Asset ```json { "id": "list-symbols-pons", "method": "MarketHub.ListSymbols", "params": {"baseAsset": "PONS"} } ``` ### Example Request for All Venues ```bash curl --request POST 'https://api.k4k3ru.com/' \ --header 'Content-Type: application/json' \ --data '{ "id": "list-symbols-1", "method": "MarketHub.ListSymbols" }' ``` ### Example Request with Venue Filters ```bash curl --request POST 'https://api.k4k3ru.com/' \ --header 'Content-Type: application/json' \ --data '{ "id": "list-symbols-2", "method": "MarketHub.ListSymbols", "params": { "venues": [ { "name": "dydx", "page": 1, "limit": 100, "marketTypes": ["perp"] } ] } }' ``` ## Response ### Response Body Successful requests use the common [JSON-RPC success response envelope](/k4k3ru-docs/api/json-rpc.md#success-response-envelope). Failed requests use the common [JSON-RPC error response envelope](/k4k3ru-docs/api/json-rpc.md#error-response-envelope). The response includes only enabled canonical symbols with available metadata for the requested venue and market type. A requested page beyond the available results returns an empty `symbols` array while preserving `total`. ### Result Fields | Field | Type | Description | | -------------------------------- | ---------------- | ----------------------------------------------------------------------------------------------------------------------------- | | `venues` | array | Venue results. Explicitly requested venues preserve request order. An all-venue query returns venues in ascending name order. | | `venues[].name` | string | Market-data venue. | | `venues[].page` | number | Effective one-based page number. | | `venues[].limit` | number | Effective maximum number of symbols on this page. | | `venues[].total` | number | Total distinct canonical symbols after applying the venue, base-asset, and market-type filters. | | `venues[].symbols` | array | Symbols on the requested page, ordered by canonical symbol in ascending lexical order. | | `venues[].symbols[].symbol` | string | Canonical symbol in `BASE/QUOTE` form. | | `venues[].symbols[].marketTypes` | array of strings | Requested market types for which this symbol is enabled. Values are ordered as `spot`, then `perp`, when both apply. | ### Errors | Code | When it occurs | | ----------------- | ---------------------------------------------------------------------------------------------------------------------- | | `invalid_request` | A specified venue or market type is invalid or duplicated; `limit` exceeds `500`; or the parameters cannot be decoded. | ### Example Success Response for All Venues ```json { "id": "list-symbols-1", "result": { "venues": [ { "name": "binance", "page": 1, "limit": 100, "total": 2, "symbols": [ { "symbol": "BTC/USDC", "marketTypes": ["spot", "perp"] }, { "symbol": "ETH/USDC", "marketTypes": ["spot", "perp"] } ] }, { "name": "btse", "page": 1, "limit": 100, "total": 2, "symbols": [ { "symbol": "BTC/USDC", "marketTypes": ["spot", "perp"] }, { "symbol": "ETH/USDC", "marketTypes": ["spot", "perp"] } ] }, { "name": "dydx", "page": 1, "limit": 100, "total": 2, "symbols": [ { "symbol": "BTC/USDC", "marketTypes": ["perp"] }, { "symbol": "ETH/USDC", "marketTypes": ["perp"] } ] }, { "name": "hyperliquid", "page": 1, "limit": 100, "total": 3, "symbols": [ { "symbol": "BTC/USDC", "marketTypes": ["spot", "perp"] }, { "symbol": "ETH/USDC", "marketTypes": ["spot", "perp"] }, { "symbol": "SOL/USDC", "marketTypes": ["spot", "perp"] } ] } ] } } ``` The symbols and pagination values shown above are examples. Use the values returned by the API. ### Example Error Response ```json { "id": "list-symbols-1", "error": { "code": "invalid_request" } } ``` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://k4k3ru.gitbook.io/k4k3ru-docs/api/market-hub/list-symbols.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.