/v1/{lang} (see Languages). The fixtureId, outcomeId and playerId you read in the odds are the ones you place orders on: there is no mapping between the data and the execution.
OddsPapi documents every field of this data in its own documentation, at docs.oddspapi.io. Moving a client that already uses OddsPapi? See Coming from OddsPapi.
Sports, tournaments, seasons
sportId. Integer. Its two digits start several other identifiers. List them withGET /v1/{lang}/sports.tournamentId. Integer. Belongs to one sport. List them withGET /v1/{lang}/tournaments.seasonId. Integer. Belongs to one tournament. List them withGET /v1/{lang}/seasons.
Entity hierarchy
Everything hangs off one tree:- The fixture. It carries the schedule and state:
startTime(epoch seconds),statusId,participant1Idandparticipant2Id,seasonId, venue. - Scores. They are per period, keyed
result,p1,p2, and so on. Theresultrow is the authoritative final or current score. - Odds. They attach to a fixture through the odds identifiers.
Markets and outcomes
Every selection follows a fixed hierarchy:
marketType → period → handicap → side, all encoded in the outcomeId. The same bet therefore always has the same marketId and outcomeId, whatever the bookmaker. The player is the one part not in outcomeId: it is playerId.How markets decompose
EveryoutcomeId comes from one deterministic decomposition:
Because every line value has its own
marketId, “Over 2.5” and “Over 3.5” are different markets. Within one marketId, the outcomes are only the sides of that exact line.
Worked example: soccer (sportId 10)
Worked example: soccer (sportId 10)
Each
marketId equals its first outcomeId, and each line value is its own market:The first row reads:
marketType=1x2, period=fulltime, handicap=0.0, outcomeName=1, the home side of the full-time result.GET /v1/{lang}/markets?sportId=10.
marketId and outcomeId
- Shared
marketId. All the outcomes of a market share itsmarketId. - First outcome. The first
outcomeIdof a market equals itsmarketId, so you can group outcomes without extra metadata. marketLength. The number of outcomes under amarketId: the sides that together form the full probability space.1x2has 3.- Structure. Both are integers built as
{sportId (2 digits)}{incrementing number}:11xxxxis basketball,14xxxxAmerican football.
marketId cover every result. Group odds by marketId for margin, overround and arbitrage calculations.
Participants and players
participantId. Integer, a team or competitor. List them withGET /v1/{lang}/participants.playerId. Integer, for player markets.0means a market that is not about a player. List them withGET /v1/{lang}/players.
Fixture IDs
fixtureId is a string that encodes several pieces of information:
id: namespace prefix; treat it as opaque11:sportId(2 digits)000132:tournamentId(6 digits)62926199: native fixture ID
fixtureId alone you can read the sport and the tournament.
Odds identifiers
A price is identified by itsoddsId:
id1400003160574217:sharpbet:141:0. Use it as the primary key of the prices you store.
Drop the bookmaker and you have the selection, {fixtureId}:{outcomeId}:{playerId}: the same bet at every bookmaker, which wins or loses the same way everywhere.
From odds to an order
An order names a selection with the same three identifiers. To back the price above:- Price floor.
minPriceis the lowest price you accept: the price you read, or a little below to allow for movement. - Bookmakers. Leave
bookmakersout to let Apexium split the stake across every bookmaker of your account. - Betslip price.
GET /v1/betslipgives the price after your account’s rules, which can differ from the market price. See Feed odds and the betslip.
Timestamps
The market data uses OddsPapi’s two units:- Epoch seconds for schedules:
startTime,startTimeFrom,startTimeTo. - Epoch milliseconds for odds updates:
changedAt,bookmakerChangedAt, and thesincefilters.
/v1 endpoints of the account and its orders use ISO 8601 strings in UTC instead.
Efficient polling
since. Onfixtures/oddsandfixtures/odds/main, pass the lastchangedAtyou saw to get only what changed since then.- Storage. Store prices keyed by
oddsId, so updates replace rows instead of adding them. - Limits. Market data counts against your key’s general budget; see Limits.
Historical odds and CLV
Both use the same
oddsId, so you can join your fills to their history:
- CLV. Compare the price you were filled at with the closing line to measure your edge.
- Fill auditing. Compare your fill prices with the recorded timeline.
- Backtesting. Replay the timeline against your strategy.
Reference
The market data endpoints are in the API → Reference sidebar, under Reference data, Fixtures and Odds. Their parameters and response schemas come from the OddsPapi v5 reference, limited to what Apexium forwards. For background on the data itself, see the OddsPapi documentation.Glossary
- sportId: numeric sport identifier; the first two digits of
marketId,outcomeIdandfixtureId. - fixtureId: string key of a match, encoding sport, tournament and a native ID.
- marketType: the kind of market (
1x2,totals,spreads, …). - period: the segment a market applies to (
fulltime,p1,p2). - handicap: the line value of a market; each line value is its own
marketId. - marketId: integer grouping the outcomes of one market; equals its first
outcomeId. - marketLength: the number of outcomes under a
marketId. - outcomeId: integer identifying one selection: market type, period, line and side.
- playerId: ties an outcome to a player;
0is a market not about a player. - participantId: integer identifying a team or competitor.
- oddsId: price key,
{fixtureId}:{bookmaker}:{outcomeId}:{playerId}. - OLV / CLV: opening and closing line value, the first and last recorded prices of an outcome.