Selecting with DQL

DQL is how a request says what it is about — one language for selection across every endpoint, instead of a different set of query parameters per resource.

where: base = BTC and venue in (BYBIT-PERP, KRAKEN-FUTURES)

The same where selects for a snapshot, for history, for candles, for books and for the stream. What you may name in it — the fields, the operators, the layers, the timeframes and the limits — is not written into this page: it is published live at GET /v2/dql/catalogue, so it can never disagree with what the platform actually holds.

Before sending a query, POST /v2/dql/parse will check it and answer with the position of the first problem and what was expected there. It is free and needs no key, because a parser is a tool, not a measurement.

An instrument is named by its market code (BTC-PERP), a venue by its published code (BYBIT-PERP) — codes are permanent once published, so a saved query keeps working.