Instruments Metadata API
Tick sizes, contract multipliers, base/quote currencies and expiration dates
Use the Instruments Metadata API to discover exchange-native symbol IDs and instrument details for replay, streaming, and CSV dataset workflows. It is most useful when you know the market shape you need, such as active BTC/USDT linear perpetuals or Deribit BTC options available during a historical replay window, but do not want to hardcode every exchange's symbol format.
Instrument fields such as symbol IDs, trading status, currencies, tick sizes, listing time, expiry and underlying asset class are sourced from exchange metadata APIs and normalized by Tardis where needed. availableSince, availableTo and datasetId are Tardis-side availability fields: when a symbol has appeared in exported metadata they reflect exported symbol state, while newly discovered active instruments can appear before replay or CSV dataset availability has caught up.
Authorization
Provide the Authorization header with your API key:
Authorization: Bearer YOUR_API_KEYGet one instrument
Returns one instrument for the provided exchange and symbol.
Use the id returned by the list endpoint as the symbol path segment. URL-encode the symbol when constructing URLs manually, especially for symbols that contain /, : or other reserved characters. The lookup is case-insensitive for the canonical symbol ID, while the response returns the exchange API symbol casing.
Endpoint URL
https://api.tardis.dev/v1/instruments/:exchange/:symbol_id
Example URLs
Response Format
Sample Response
List and filter instruments
Returns instruments for one exchange, optionally narrowed by a URL-encoded JSON filter query parameter.
Use this endpoint to find symbols for replay, streaming, and historical availability checks. Broad unfiltered responses can be large for options-heavy exchanges, so prefer filters when you know the market you need.
Endpoint URL
https://api.tardis.dev/v1/instruments/:exchange?filter={filter_payload}
Example URLs
Optional Filter Object
Provide filter as a JSON object. When used in a query string, it must be URL-encoded.
Filter Limits
Each array filter accepts up to 50 values.
String filter values must be between 1 and 150 characters.
type,contractType, andunderlyingTypemust use the allowed enum values documented above.The full request URL must be 12000 characters or shorter.
Sample Request in JavaScript
Response Format
Array of instruments objects as described for single instrument endpoint
Client helpers for symbol discovery
Client helpers find exchange-specific instrument symbol IDs from normalized market criteria, so you do not have to hardcode each exchange's symbol format. They use the Instruments Metadata API to return the correct id for each requested exchange, ready to pass to replay, streaming, or raw data feeds.
Returned id symbols are exchange-provided IDs and are not normalized by the clients. Returned datasetId symbols are CSV dataset IDs for instruments whose symbols appear in exported dataset metadata; official clients URL-encode them when downloading datasets. If you construct dataset URLs manually, URL-encode the symbol path segment.
Find active BTC/USDT linear perpetuals across exchanges with different native symbol formats.
Find active Tesla equity instruments by filtering on underlyingType.
Use the datasetId selector only when you need symbols for direct CSV dataset file downloads. Instruments without datasetId are omitted from selector results.
Find active BTC/USDT linear perpetuals across exchanges with different native symbol formats.
Find active Tesla equity instruments by filtering on underlyingType.
Use selector="datasetId" only when you need symbols for direct CSV dataset file downloads. Instruments without datasetId are omitted from selector results.
Last updated
Was this helpful?