Skip to main content
TL;DR — An order is your instruction; a bet is the wager that lands at a bookmaker. Identifiers (fixtureId, outcomeId, playerId, participantId) are shared with OddsPapi v5. Every order carries a unique requestUuid for idempotency. Three independent lifecycles track an order, each of its bets, and each bet’s settlement.

Identifiers

ABP shares its identifier space with OddsPapi v5 — the same fixtureId and outcomeId you discover via OddsPapi are the ones you send to ABP. No translation layer is needed. The two vocabularies never mix. A /fixtures/* endpoint rejects futureId, futureOutcomeId and participantId; a /futures/* endpoint rejects fixtureId, outcomeId and playerId. Both answer 422 with a message naming the other surface.

Futures market shapes

A futures selection is the pair (futureOutcomeId, participantId), and it comes in exactly two shapes: futureOutcomeId=0 and participantId=0 names nothing and is rejected. Note there is no playerId on futures — participantId names a team or a player alike — and no period.

Market keys

Internally, every priced selection is addressed by a composite market key:
Treat an oddsId as opaque. Store the value a betslip response or WebSocket delta gives you and send it back verbatim — never split, concatenate or reconstruct it. ABP always publishes the key that actually matched, so a client that stores the oddsId is unaffected by a change to the format; one that parses it is not. (OddsPapi is migrating its futures identifier scheme, which is why the whole /futures/* surface answers 501 today — see Overview → Futures.)
You rarely build these by hand — GET /fixtures/betslip and GET /futures/betslip return them keyed and ready — but understanding the shape helps when reading WebSocket betslip payloads.

Orders vs bets

This distinction is the single most important thing to internalize. One order can produce multiple bets when partial fills or multi-bookmaker routing apply. For example, a single order for 5,000 USD might fill as three bets across two bookmakers. See Order Placement for how fills are distributed.

Idempotency & request deduplication

Network retries are unavoidable, and a retried placement must never double-stake. ABP guarantees this through request deduplication.
1

Assign a unique requestUuid per order

Each order in a POST /fixtures/place-orders batch carries its own requestUuid (standard 8-4-4-4-12 UUID). Generate it client-side, once, and reuse the same value on every retry of that order.
2

ABP fingerprints it server-side

The server records each requestUuid it has seen with a 30-minute TTL. Within that window, a repeat of the same requestUuid is recognised as a duplicate.
3

Duplicates are silently skipped

A duplicate order is not placed again and is not returned as a decline. It is simply skipped, so the rest of the batch processes normally.
4

All-duplicate batches return 409

If every order in a request is a duplicate, there is nothing to do, so the request returns 409 Conflict with the offending UUIDs.
Reusing a requestUuid for a different order within 30 minutes will cause that order to be skipped. Always generate a fresh UUID for each distinct placement, and only reuse it verbatim when retrying that exact placement.
requestUuid is normalised before it is stored. ABP parses the value and rewrites it in the canonical lower-case hyphenated form, so the value echoed back on the order (and on the WebSocket orders payload) may differ in spelling from the one you sent. {EB45B192-317B-42D5-9F65-AF497B9FA8C1}, EB45B192317B42D59F65AF497B9FA8C1 and urn:uuid:eb45b192-… all land on the same key — which is the point: a retry that changes case is still recognised as the same order instead of becoming a second real bet. Match orders on the canonical form, not on a byte comparison with what you sent.

Order lifecycle

Bet lifecycle

Settlement lifecycle

Once a bet is CONFIRMED, settlement tracks the financial result:
Settlement changes are pushed over the settlements WebSocket channel. See Order Placement and WebSocket.

Account priority & the limit cascade

Each bookmaker account has a priority (higher = preferred). When routing, ABP selects the highest-priority active account first for each bookmaker. Stake limits resolve in priority order — account limits > bookmaker limits > odds limits — with the first non-null value winning:
Full detail and worked examples live in Currency & Limits.

Glossary

Next steps

Order Placement

How fills, pricing, and the limit cascade work.

Currency & Limits

Denomination, conversion, and limits in depth.

Quickstart

Place your first bet in 5 steps.

Bookmakers

Capability matrix across all 36 bookmakers.