Skip to content
Account

What DEBYKO is

Crypto derivatives data from every venue that quotes an instrument, stored as each venue published it: each value carries the venue that published it, the time DEBYKO received it and its age.

What this API will not do to your data

Section titled “What this API will not do to your data”
  • A missing value is never a zero. A venue that does not publish a field is absent from the answer, and the answer says which of the five it is: the value is there and fresh, there and stale, the layer is collected but nothing has arrived, the venue publishes no such field, or nobody is collecting it for that listing. Nothing is filled in.
  • Venues are never averaged. There is no “the price of BTC” here. There is what Bybit published, what Kraken published, and the age of each.
  • Values come back as the venue published them. Prices are not rounded, rescaled or re-serialised on the way through; a derived figure (a spread, a rate) says so and carries its own definition.
  • Gaps are not filled. History is stored with its holes intact, and an answer about a period nobody quoted is empty rather than interpolated.

What this reference covers

Section titled “What this reference covers”

/v2, which is the platform: selection in DQL, point-in-time replay, per-second history, candles in any of the stored periods, books, screening and a live stream.

Most measurement endpoints need a key. The venue and instrument catalogues, DQL catalogue and parser, plan list, public operational budgets, and public anchors do not; you can see what exists and what a query may ask before deciding to pay for measurement data.

The unkeyed /v1 display API and /lab demo were removed as part of issue 307. Use the V2 reference and the generated clients for platform integrations. Spot listings are available through the V2 market-data endpoints when kind is spot or all; DQL and Agent selection remains perpetual-only.

Getting started

Section titled “Getting started”
Terminal window
# what is collected, no key needed
curl "https://api.debyko.com/v2/venues"
curl "https://api.debyko.com/v2/dql/catalogue"


# a measurement, with a key
curl -H "Authorization: Bearer $DEBYKO_KEY" \
  -H "content-type: application/json" \
  -d '{"where":"base = BTC","layers":["mark","funding","book"]}' \
  "https://api.debyko.com/v2/snapshots"

A key is issued at studio.debyko.com/account; the Free plan needs no card. Send it as Authorization: Bearer <key> — never in a URL, where it would be written into logs and browser history. A key sent as a query parameter is refused with KEY_IN_URL.

On debyko.com

Section titled “On debyko.com”