What DEBYKO is

Crypto derivatives data from every venue that quotes an instrument, with the evidence attached: 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

• 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.
• A gap stays a gap. History is stored with its holes intact, and an answer about a period nobody quoted is empty rather than interpolated.

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 of it needs a key. The endpoints that describe the platform rather than measure a market — coverage, the catalogue and the parser — do not, because you should be able to see what exists and what a query may ask before you decide to pay for the answers.

There is also a /v1 surface, which is what debyko.com and Studio are drawn with. It still answers and nothing about it is changing, but it is not documented here: it is a display surface, not a thing to build on, and meeting eleven of its endpoints before reaching DQL would send you into the wrong half of the platform.

Getting started

# 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.