Skip to main content

What is ABP?

The Automated Bet Placing (ABP) API by 55-Tech lets you place bets across 36 bookmakers through a single integration. Instead of building and maintaining individual bookmaker connectors, ABP handles the entire lifecycle from bet placement through settlement. Core capabilities:
  • Account management — Full CRUD for bookmaker accounts with priority-based selection, per-account stake limits, and multi-currency support
  • Betslip retrieval — Get real-time odds and limits for any fixture/outcome across all configured bookmakers before placing
  • Futures support — A separate /futures/* surface for outright markets, keyed by futureId + futureOutcomeId + participantId. Every futures endpoint answers 501 until OddsPapi’s db-v2 identifier scheme is live
  • Smart order routing — Place single or bulk orders; ABP automatically selects the best bookmaker by odds and limits
  • Bet tracking — Monitor every bet from placement through confirmation and settlement with full audit trail
  • Position & PnL analytics — Aggregated views of exposure and profit/loss grouped by bookmaker, account, or user reference

Data flow

1

Discover fixtures & odds via OddsPapi v5

Your app consumes the OddsPapi v5 API to discover fixtures, markets, outcomes, and real-time odds across all supported bookmakers. OddsPapi is the data layer — ABP is the execution layer built on top of it. Fixture IDs and outcome IDs are shared between both APIs.
2

Fetch betslip from ABP

Before placing, call GET /fixtures/betslip?fixtureId=...&outcomeId=...&playerId=... to get aggregated odds and limits from all your configured bookmaker accounts. Outright markets have their own path — GET /futures/betslip?futureId=...&futureOutcomeId=...&participantId=.... ABP resolves stake limits (account > bookmaker > odds) and returns the effective min/max per bookmaker.
3

Place orders through ABP

Send POST /fixtures/place-orders with one or more orders. ABP routes each order to the best bookmaker(s) based on price, available limits, and account priority. Each bookmaker integration places the bet and reports back confirmation or decline.
4

Receive real-time updates via WebSocket

Connect to WS /ws to receive real-time pushes for order status changes, bet confirmations, settlements, balance updates, and system events. No polling needed.
5

Query history & analytics

Use GET /fixtures/orders, GET /fixtures/bets for order/bet history with keyset pagination, and GET /positions, GET /pnl for aggregated exposure and profit/loss analytics.

Base URL

Two surfaces: fixtures and futures

A selection is either a fixture (a match, with a kickoff) or a future (an outright, which resolves when its season does), and the two are identified differently. Each has its own path prefix, so no endpoint has to guess which kind of identifier it was handed: Each surface rejects the other’s identifiers with 422, naming the path you wanted. The split applies to the four endpoint groups that carry a selection — betslip, orders, bets, markets. /accounts, /bookmakers, /positions and /pnl name no selection and stay unprefixed.
The pre-split paths keep working. /betslip, /place-orders, /cancel-orders, /cancel-all-orders, /orders, /bets, /bets/{bet_id} and /markets are unchanged aliases of their /fixtures/* equivalents — same handler, same request, same response — and are marked deprecated in the reference with no removal date. Nothing you have in production needs to change. New integrations should use /fixtures/*.One exception worth knowing if you were experimenting with outrights: the unprefixed fixture endpoints no longer accept futureId or participantId. They used to answer 501; they now answer 422 (placement) or 400 (betslip) and point you at /futures/*.

Key concepts

Orders vs bets

An order is your instruction to place a bet. A bet is the actual wager placed on a bookmaker. One order can result in multiple bets when using partial fills or multi-bookmaker routing.

Request deduplication

Each order requires a unique requestUuid (UUID format). ABP uses server-side deduplication (30-minute TTL) to prevent duplicate placements. A duplicate order is silently skipped; if every order in a request is a duplicate, the request returns 409 Conflict.

Order lifecycle

  • PENDING — Order received and queued
  • PROCESSING — Routing to bookmakers
  • FILLED — All stake placed successfully
  • PARTIALLY_FILLED — Some stake placed, remaining expired or no capacity
  • REJECTED — Failed validation (bad odds, invalid fixture, etc.)
  • EXPIRED — Order expiresAt time reached (default: 5 seconds, max: 24 hours)
  • CANCELLED — Explicitly cancelled by client
  • FAILED — Internal error during placement

Bet lifecycle

  • PENDING — Bet created, awaiting bookmaker response
  • PLACED — Sent to bookmaker, awaiting confirmation
  • CONFIRMED — Bookmaker accepted the bet
  • REJECTED — Bookmaker rejected the bet
  • CANCELLED — Bet cancelled before confirmation
  • FAILED — Internal error during placement
  • VOID — Bet voided by bookmaker

Settlement lifecycle

  • UNSETTLED — Bet is live, awaiting result
  • WON — Full win
  • LOST — Full loss
  • VOID — Bet voided (stake returned)
  • HALF_WON — Asian handicap partial win
  • HALF_LOST — Asian handicap partial loss
  • PUSH — Stake returned (tie on the line)
  • CASHOUT — Early withdrawal at negotiated price

Account priority

Each bookmaker account has a priority field (higher = preferred). When placing an order, ABP selects the highest-priority active account first for each bookmaker.

Limit cascade

Stake limits are resolved in priority order: account limits > bookmaker limits > odds limits. For example, if an account has minStake: 10, the bookmaker default is minStake: 1, and the odds entry shows limitMin: 5, the effective minimum is 10 (from the account override).

Futures (outright markets)

Futures live under /futures/*. A future is identified by a futureId and a selection is the pair (futureOutcomeId, participantId). There is no playerId — on a future, participantId names a team or a player alike — and no period. Two market shapes, told apart by futureOutcomeId: A pair that names nothing (futureOutcomeId=0 with participantId=0) is rejected. The whole futures surface answers 501 today, for two reasons that retire separately:
  1. The identifier scheme. ABP speaks OddsPapi’s db-v2 futures identifiers only — a futureId like id1012639310001. The current feed still publishes bare integers, which ABP refuses (400) rather than guessing at, so futures ingest is switched off and there is nothing cached to serve. This clears when db-v2 goes live (expected late 2026-10).
  2. Storage. Placement, cancellation, GET /futures/orders and GET /futures/bets additionally need futures identity columns the orders table does not have — and writing a futureId into a fixture’s column is exactly the conflation this split removes.
The routes, parameters and validation are final, and the 501 endpoints validate your payload first: a malformed futureId or an empty selection pair is a 422/400 even today. Integrate against them now and only the 501 changes. When futures do turn on, their odds are feed-authoritative — they come from the OddsPapi cache only, so verifyBetslip on an account has no effect on this surface.
Treat an oddsId as opaque. Store it and send it back; do not parse it. ABP always publishes the key that actually matched — a client that stores the id it was given is unaffected by any change to the format, while a client that splits it on : is not.

Bookmaker slugs

Bookmakers are identified by slug strings (e.g., pinnacle, betfair-ex, polymarket). Use GET /bookmakers to list all 36 supported bookmakers with their default stake limits.

Endpoints at a glance

The same selection endpoints are also reachable without the /fixtures prefix (/betslip, /place-orders, …) — deprecated aliases, unchanged behaviour.

Supported bookmakers

Traditional sportsbooks: pinnacle, pinnacleb2b, betamapola, betcris, bookmaker.eu, cloudbet, cloudbetb2b, justbet, kaiyun, matchbook, monkeyline.vip, novig.us, 198bet, paradisewager, sharpbet, singbet, sports411.ag, 3et, 3et++ Betting exchanges: betfair-ex, smarkets, limitless-ex Prediction markets: polymarket, polymarket.us, kalshi, predict.fun, prophetx, sx.bet, vertex, 4casters Punter platforms: punter.io, punter.io++

Resilience

ABP includes production-grade reliability features:
  • Circuit breakers — Per-bookmaker circuit breakers prevent cascading failures and auto-recover
  • Retry with exponential backoff — for transient failures
  • Emergency controls — Orders may be temporarily paused during system maintenance
  • Rate limiting — Per-API-key rate limits (configurable per client)

Data source

ABP consumes real-time odds data from OddsPapi v5. Fixture IDs and outcome IDs in ABP correspond directly to OddsPapi identifiers. Your app should use OddsPapi to discover fixtures and markets, then use ABP to execute bets.

Frequently asked questions

ABP places bets directly with bookmakers — it is not a hedging or market-making engine. You send an order, ABP routes it to the best account(s), places the wager, and tracks it through settlement. The data layer is OddsPapi v5; ABP is the execution layer on top.
An order is your instruction to place a wager. A bet is the actual wager placed at a bookmaker. One order can produce multiple bets when partial fills or multi-bookmaker routing apply. See Concepts.
Each order carries a unique requestUuid (UUID format). ABP deduplicates server-side for 30 minutes — a duplicate is silently skipped, and if every order in a request is a duplicate the request returns 409 Conflict. Deep dive in Concepts.
Yes. Set acceptPartialStake: true to let a single order fill across multiple bets, and pass a bookmakers list (or omit it for auto-selection) to spread across venues. ABP enforces a weighted-average price constraint so your effective price stays at or above orderPrice. See Order Placement.
36 bookmakers across traditional sportsbooks, betting exchanges, prediction markets, and punter platforms. Capabilities (sweep, settlement, betslip) vary per venue — see the Bookmaker capability matrix.
Yes. Set testOrder: true to run the full validation and routing path (limits, price checks, account selection) without sending a bet to the bookmaker — the fastest way to confirm your payload and IDs before going live. See Quickstart.
ABP runs per-bookmaker circuit breakers, retry with backoff, a two-tier emergency control, and reliable WebSocket delivery with ack/replay. Recovery from disconnects is bounded — reconcile any seq gaps via REST. See Reliability & Operations.

💬 Ask an AI Assistant

Want to explore or ask questions about this API using your favorite AI? Click one of the links below — each one opens the full docs bundle in the selected tool with a pre-filled prompt:

Next steps

Authentication

Set up your API key.

Quickstart

Place your first bet in 5 steps.

Order Placement

How fills, pricing, and limits work.

Currency & Limits

Denomination, conversion, and the limit cascade.