Skip to main content
All timestamps are UTC. Breaking changes are called out explicitly — subscribe to the status WebSocket channel and watch this page before upgrading.

2026-10-09

✨ Added

  • Two surfaces: /fixtures/* and /futures/*. Every selection endpoint now lives under an explicit prefix: GET /fixtures/betslip, POST /fixtures/place-orders, GET /fixtures/orders, GET /fixtures/bets, GET /fixtures/markets, and the /fixtures/cancel-* pair — plus the mirrored /futures/* set. See Overview → Two surfaces.
  • The /futures/* surface exists, and every endpoint on it answers 501 — including GET /futures/betslip and GET /futures/markets. Futures are switched off at the feed until OddsPapi’s db-v2 identifier scheme is live (expected late 2026-10): ABP speaks db-v2 futures identifiers only, so there is nothing to serve yet. The routes, the parameters and the request validation are final, so an integration written against them today needs no change on the day futures turn on. A bare-integer futureId from the current feed is refused (400).

🔁 Changed

  • The pre-split paths keep working as deprecated aliases (/betslip, /place-orders, /orders, /bets, /markets, /cancel-orders, /cancel-all-orders) — same handlers, same behaviour, no removal date. They are marked deprecated in the OpenAPI spec; migrate to /fixtures/* at your own pace.
  • requestUuid is normalised. ABP now rewrites the key to the canonical lower-case hyphenated form, so the value echoed back on an order may differ in spelling from the one you sent. This closes a real hole: a retry that changed case used to be accepted as a second distinct order. Match on the canonical form, not on a byte comparison. See Core Concepts → Idempotency.

⚠️ Breaking (futures fields only)

The fixture endpoints no longer accept futures identifiers. Both changes affect only fields that previously answered 501 Not Implemented, so no working call changes behaviour:
  • POST /fixtures/place-orders (and its deprecated alias POST /place-orders) rejects futureId / futureOutcomeId / participantId with 422 instead of 501.
  • GET /fixtures/betslip (and its deprecated alias GET /betslip) no longer declares futureId or participantId; a futures selection answers 400 instead of 501, pointing at /futures/betslip.

🚧 Still to come

  • Futures placement and futures order/bet reads — POST /futures/place-orders, POST /futures/cancel-orders, POST /futures/cancel-all-orders, GET /futures/orders, GET /futures/bets and GET /futures/bets/{betId} answer 501. They validate first (422 on a bad body, 400 on a bad filter), so an integration built against them today needs no change the day placement lands.

2026-06-17

🔁 Changed

  • Single source of truth for currency. An account’s trading currency now comes solely from accounts.currencyId; default-currency guessing has been removed. Order stakes are denominated in orderCurrency (default USD), while bets and balances use the account’s native currency. See Currency & Limits.
  • REST betslip path aligned with the WebSocket path so both transports return identical odds/limit shapes.

🔧 Improved

Earlier

✨ Added

  • 32 bookmaker integrations behind a single API — sportsbooks, betting exchanges, prediction markets, and punter platforms. See Bookmakers.
  • Smart order routing with single and multi-bookmaker placement, partial fills, and exchange sweep mode.
  • Reliable WebSocket delivery — opt-in at-least-once delivery with ack / ack_batch / replay and a 100-message buffer.
  • Request deduplication — per-order requestUuid idempotency with a 30-minute TTL.
  • Analytics — GET /positions and GET /pnl for aggregated exposure and profit/loss.

🚧 Coming soon

  • Futures / outright markets via futureId + futureOutcomeId + participantId. The routes and the request model are in place under /futures/*; every futures endpoint returns 501 Not Implemented until OddsPapi’s db-v2 identifier scheme is live.