2026-09-27 — Purchase id and price on generated accounts
POST /v1/firm-control/accountsaccepts an optionalidempotency_key. The value is unique among that firm’s accounts. Repeating it returns the original account (200) instead of creating a second one.GET /v1/firm-control/accountsacceptsidempotency_keyto look up that account.POST /v1/firm-control/accountsaccepts an optionalprice_paid. Tradara stores that purchase amount on the account. A bulk create divides it across the accounts in the request, and each account keeps its share.
2026-09-18 — Firm live risk-state read
- Added
GET /v1/firm-control/accounts/{account_id}/risk-stateso a firm can ingest live max-loss floor, trailing cap, peaks, daily/weekly triggers, and lockout for one account.
2026-09-17 — Firm account replacement
- Added
POST /v1/firm-control/accounts/{account_id}/replaceso a firm can flatten and close one account and mint a replacement from the same evaluation template.
2026-09-16 — Daily-loss migration re-anchor
- Added
POST /v1/balances/{account_id}/daily-loss/reanchorso a firm can reset today’s DLL anchor to current cash after migration while preserving the existing dollar allowance.
2026-09-14 — Firm cash adjustments and account max-loss cap
- Documented
POST /v1/balances/{account_id}/adjustfor firm deposits and withdrawals, plus adjustment list routes. The endpoint was already reachable with a firm API key. - Added
PATCH /v1/firm-control/accounts/{account_id}/max-loss-limitto move one existing account’s max-loss cap after a payout. Shared plan profiles are cloned before the write. - Firm API keys can call
POST/DELETE /v1/accounts/{account_id}/lockout. The key still needsaccounts:writeand can only act on accounts in its firm.
2026-08-30 — Firm event catalog
- Added
positions.createdtoFirmEventType. Positions already dual-published this type; the enum and docs omitted it. - Footprint now dual-publishes
fingerprints.flaggedon the same shared-device trigger asdevices.flagged/ip_logs.flagged. - Catalog changelog lives on Event catalog.
2026-08-30 — Per-account trading control in Prop Firm docs
- Documented lock/unlock, flatten, cancel, and live order/position reads under Per-account trading control. These routes already existed on the gateway with a firm API key; they were not listed next to emergency halt.
- Flatten returns cancel/close counts after the OMS submits offset orders. Resulting positions are read with
GET /v1/accounts/{account_id}/positions.
2026-08-24 — Per-account rule overlays on generate
POST /v1/firm-control/accountsaccepts optionalinitial_balance,currency,risk_profile, andpassing_criteria.- When those overlays are present, Tradara clones the template risk profile and/or passing criteria so the new account does not share catalog rows with other accounts on the same plan.
PUT /v1/firm-control/offeringsremains a product-family enablement toggle, not a SKU rule editor.
2026-06-27 — Realtime WebSocket reference
- Added Trading API realtime reference for the trader-scoped
/v1/wsstream. - Added Prop Firm realtime reference for the firm-scoped
/v1/firm-wsstream, including AsyncAPI playground. - Removed the legacy per-resource SSE pages —
/trading/orders/streaming,/trading/fills/streaming, and/trading/positions/streamingnow redirect to the realtime overview.
2026-06-15 — OCO link & companion endpoints
- Documented
POST /v1/orders/groups/oco/linkandPOST /v1/orders/groups/oco/companion. Both were in the implementation; the OpenAPI spec is updated to match.
2026-06-01 — Idempotency window extended
Idempotency-Keyretention onPOST /v1/ordersextended from 1 hour to 24 hours. No request changes required.
2026-05-10 — Prop Firm API GA
- Promoted
/v1/firm-control/*to general availability. - Added Account provisioning as the canonical onboarding entry point.
- Introduced firm API keys with the
tdr_live_prefix.
2026-04-22 — Trading API public beta
- First public release of
/v1/orders,/v1/fills,/v1/positions,/v1/trades,/v1/balances,/v1/stats. - Cursor pagination across all list endpoints.
- Standard error envelope rolled out across all services.
Have feedback on the public API or a deprecation timeline that doesn’t fit your roadmap? Reach out to your Tradara account contact.

