adona-robot · market data by capacity

API changelog

Changes to the /v1 contract only: routes, fields, refusal codes and stream frames. Newest first. A breaking change says what your code must do.

Last change: · API reference · openapi.json

The prop reference no longer offers a trader's address.

Corrected in the reference

  • Creating a prop trader no longer lists an email field; one sent is still refused with TRADER_EMAIL_NOT_ACCEPTED.
  • A trader's email is null, except for a trader created before 04.11.2026.
  • TRADER_NOT_HELD_BY_TENANT reads: this trader's account was not created by you.

The prop-firm tenant API, in beta.

Added

  • The prop-firm tenant API is published in beta under /v1/prop. It has its own key, adp_live_…, which your server exchanges at POST /v1/prop/tokens for a twelve-hour prop token, sent as Authorization: Bearer on every other /v1/prop call. A data key or token is refused there, and a prop token on the data routes.
  • Its routes are in /v1/openapi.json under the prop tag, and in the reference's Prop firm API section: your tenant, your traders and their accounts, an account's status, your products, the monthly reports, the exposure, the share covered (H) and the funded accounts. Each refusal is documented per route, with what to do.
  • Trading through the API (orders, positions, executions and the confirmations stream) is not open yet. It will have its own entry on the day it opens.

A revoked key is told so on every request.

Breaking

  • A request with a revoked key answers 401 CUSTOMER_ACCESS_REVOKED every time. It used to answer 429 TOO_MANY_ATTEMPTS from the 61st request of a minute, and a refused request no longer counts against an end user's sixty a minute. Nothing to change in a client: the answer now names what you can act on.

The Swagger page is removed; the OpenAPI document stays

Breaking

  • /v1/docs no longer exists and answers 404. Read the reference at https://adona-robot.com/en/reference, or give /v1/openapi.json to your tools: it is the same contract, unchanged.

The event_id of a quote frame is an opaque identifier

Breaking

  • The event_id of quote.update and quote.snapshot frames is now an opaque identifier, q_ followed by 24 hexadecimal characters. It is still unique to one quote and the same if that quote is sent again. Code that compares it needs no change. Code that read anything into its former value should treat it as opaque.

The stream says when a market is closed.

Added

  • The subscribed and candle.watched frames of /v1/stream carry market: an object giving, for each symbol, its session as of that acknowledgement, open, closed or unknown. Outside trading hours (a weekend, a holiday, the daily break) a channel sends its snapshot and then nothing until the market opens; closed says so, where before the silence looked like a broken feed. unknown means we have no session signal at that moment, not that the market is shut. The field is not sent again when the session changes. It is added; nothing else in either frame changes.
  • /v1/openapi.json gives an example body for every refusal code of every route ({"detail": "CODE"}, and for a 422 the code, its reason and fields), and an example 200 for POST /v1/tokens, GET /v1/candles and POST /v1/ws-ticket. Every 429 and 503 declares its Retry-After header. The Bearer scheme says which secret goes where: the API key on POST /v1/tokens only, the access token everywhere else. Nothing a client sends or receives changes.

A 422 lists the fields it refuses.

Added

  • Every 422 from /v1 now carries fields beside detail: a list of {"loc": [...], "reason": "..."}, one per offending field, loc naming the field (["limit"], ["end_user_id"]). A client can point at the field without parsing the text. The list is empty when no field can be named, such as a body that is not JSON. detail is unchanged: branching on the code before its colon keeps working.

The reference says what volume counts.

Added

  • The volume field of a candle (GET /v1/candles, and v in the stream's candle frames) is a tick volume: the number of price updates received in the bar. It is not a traded volume. Some bars of the history come from another price feed and carry its tick volume, not counted the same way: on every timeframe, the last day holding one, by the bar's open time in UTC (its time), is other_feed_until for each symbol in /symbols.json, 2026-06-05 at the latest. The value itself did not change.

A rate-limit refusal says how long to wait.

Added

  • A 429 with the code TOO_MANY_ATTEMPTS from POST /v1/tokens, GET /v1/candles or POST /v1/ws-ticket now carries a Retry-After header: the seconds left in the window that refused the call. Waiting that long is enough; before, a client could only guess.
  • /v1/openapi.json names its base URL, https://api.adona-robot.com, in servers (it said /, which a client generated from a downloaded copy could not resolve), and its contact and terms of service in info.

Two corrections to the reference: how to open the stream, and what a refusal looks like.

Corrected in the reference

  • /v1/openapi.json and the POST /v1/ws-ticket response said to pass the ticket in the query string of /v1/stream. The API has never read it there: offer two subprotocols, adona.data.v1 and ticket.<ticket>, as in new WebSocket(url, ["adona.data.v1", "ticket." + ticket]). A ticket sent only in the URL is refused with an HTTP 403.
  • The reference said every refusal is {"detail": "CODE: text"}. The routes in the reference answer the bare code, {"detail": "CODE"}, and only a 422 adds a colon and the reason. Reading the part before the first colon works for both.

The reference is public.

Added

  • /v1/openapi.json and /v1/docs are public: the shape of every response, and every refusal code of every route with what to do about it (retry, wait for Retry-After, or stop).
  • The live stream is described there too: the ticket, the subprotocol, the five frames, the channels, and every close code with whether to reconnect.
  • Refusal and close codes that predate this changelog without an entry of their own are listed there, as of this date.
  • POST /v1/tokens declares its authentication: the API key goes as a Bearer token, so a client generated from the document sends it.

A trial ends, and reads only its own window of history.

Added

  • When a free trial ends, GET /v1/candles, POST /v1/ws-ticket and POST /v1/tokens answer 403 CUSTOMER_TRIAL_EXPIRED, and /v1/stream closes with 1008 CUSTOMER_TRIAL_EXPIRED, at connect and on a stream already open. It is not CUSTOMER_ACCESS_REVOKED: the same key works again on a paid plan. An account that is also revoked is answered as revoked.
  • A trial reads history back to the start of its window only. The bar containing that limit is served whole, the cursor stops there, and a page entirely before it comes back empty and is not billed.

The trial has a connection limit.

Added

  • On the trial, a stream opened past the plan's simultaneous connections is closed with 1008 CUSTOMER_CONNECTION_LIMIT, and the close reason carries only that code. The ticket is spent by then, so a retry needs a new one from POST /v1/ws-ticket.

Pacing per plan, and pages of up to 5000 bars.

Breaking

  • A request both revoked and over its daily budget answers 401 CUSTOMER_ACCESS_REVOKED, not 429: the answer that names what you can act on. A refused request is no longer counted against the daily budget, nor billed.

Added

  • 429 CUSTOMER_MINUTE_CEILING, with a Retry-After header carrying the wait, when the plan's per-minute allowance is spent; the stream answers it as an error frame. It clears by waiting, unlike CUSTOMER_DAILY_CAP, which does not.
  • limit on GET /v1/candles accepts up to 5000 bars, up from 500. INVALID_LIMIT moves with it.
  • A subscribe that is refused is rolled back, and the stream sends subscribed again with the channels the connection actually holds.

Every refusal on /v1 is a coded string, including a validation failure.

Breaking

  • A request that fails validation answers 422 with a coded string, {"detail": "CODE: reason"}, instead of a list of objects. Branch on the code.
  • TIMEFRAME_UNSUPPORTED is a 422, not a 400. No request could produce the 400, so no client can have relied on it.
  • END_USER_ID_REQUIRED is gone. A blank or overlong end_user_id on POST /v1/tokens answers INVALID_END_USER_ID.
  • A missing parameter answers INVALID_REQUEST, not TIMEFRAME_UNSUPPORTED.
  • A body that is not valid UTF-8 answers 422 INVALID_REQUEST instead of an uncoded 400.

Corrected in the reference

  • /v1/openapi.json no longer advertises HTTPValidationError, a shape /v1 does not send.
  • TIMEFRAME_UNSUPPORTED is never a close code. A bad step on candle.watch answers a candle.watch.rejected frame and the stream stays open.

Added

  • One code per field: INVALID_END_USER_ID on POST /v1/tokens; INVALID_SYMBOL, INVALID_LIMIT and INVALID_BEFORE on GET /v1/candles. A request wrong in two ways at once answers INVALID_REQUEST.

Two routes are callable from a browser.

Added

  • GET /v1/candles and POST /v1/ws-ticket answer cross-origin requests, without credentials, once your page's origin is declared on your account. The bearer token is the access control, not the origin. /v1 answers carry Vary: Origin, and Retry-After and X-Adona-Hint are exposed to the page.
  • POST /v1/tokens refuses a browser preflight, on purpose: it takes your API key, which belongs on your server.
  • api.adona-robot.com caps request bodies at 16 KB.

The API has its own hostname.

Added

  • https://api.adona-robot.com serves /v1.

First version of /v1.

Added

  • POST /v1/tokens exchanges an API key, sent as Authorization: Bearer, for a twelve-hour token per end user (end_user_id).
  • GET /v1/candles reads candle history with a cursor; POST /v1/ws-ticket issues a single-use ticket valid 30 seconds; /v1/stream is the live stream, on the subprotocol adona.data.v1.
  • API keys carry their prefix, adk_live_ or adk_test_, and the prefix is part of the key. A key sent where a token belongs answers EXPECTED_ACCESS_TOKEN, a token sent to POST /v1/tokens answers EXPECTED_API_KEY, and a trader token answers EXPECTED_DATA_TOKEN.