Odds API

bet365 odds feed

Start with GET /odds to get the matches and current prices. Then connect to /ws to keep receiving odds updates.

Get a free API key on your account page; see section 9.

More docs: Sports · Markets · WebSocket · Bet Builder · Python client · History · moviodds.com

1. Load all matches and their odds

curl --compressed https://moviodds.com/odds

Example response:

{
  "matches": [{
    "id": "123456",
    "home": "Team A",
    "away": "Team B",
    "league": "Example League",
    "kickoff_utc": "2026-09-11T18:00:00Z",
    "in_play": false,
    "quotes": [{
      "fixture_id": "123456",
      "group_id": "981",
      "market_id": "100",
      "sel_id": "9001",
      "label": "Team A",
      "odds_dec": 2.5,
      "ts": "2026-09-11T12:00:00Z"
    }]
  }]
}

Save each match under its id, along with its names and odds

If quotes is empty, there are no cached odds for that match yet

Only need part of the board? /odds?in_play=1 returns just the matches in play, and /odds?groups=40 returns just the markets you list (comma-separated group ids; Full Time Result is 40 before kickoff and 1777 in play). Each match always carries market_count, the number of markets priced for it.

Once a soccer or e-soccer match is in play, its pre-match markets (like group 40) stay on the board suspended at their last price and stop updating. Read the in-play groups instead, for example 1777 for Full Time Result.

Soccer is the default. Add sport for any of the other 23 sports, for example /odds?sport=tennis, or sport=all for every sport at once; every match carries its own sport field. The keys and each sport's main markets are on the sports page.

A match in play carries a score field. It is always written home-away, the home side first, for every sport (for example "2-1"). Cricket is the one that does not use a plain number-to-number score: it uses bet365's own wickets/runs form, for example "7/199" (7 wickets, 199 runs), with each innings separated by a comma.

Want a link straight to the match on bet365? Add /odds?links=1 and every match gains a links object: match (open this: the live page while the match is in play, otherwise the pre-match page), prematch and live. They are bet365's own in-browser routes, so the same link works on any regional bet365 domain. It's opt-in so the default board stays small. To find a specific selection on that page, use the quote's sel_id.

Ask for gzip. The full soccer board is about 100 MB of JSON, around 8 MB gzipped, so send Accept-Encoding: gzip. Most HTTP clients already do it for you (Python requests and httpx, Node fetch, Go, browsers). Plain curl needs --compressed, and Python's built-in urllib needs the header plus a decompress:

import gzip, json, urllib.request

req = urllib.request.Request("https://moviodds.com/odds?sport=soccer",
                             headers={"Accept-Encoding": "gzip"})
with urllib.request.urlopen(req) as r:
    body = r.read()
    if r.headers.get("Content-Encoding") == "gzip":
        body = gzip.decompress(body)
odds = json.loads(body)

You can still get it uncompressed, but without a key a response bigger than about 5 MB sent raw is limited. Each IP gets one of those per minute; ask again sooner and you get 429 {"error":"raw_rate_limited"} with a Retry-After header telling you how many seconds to wait. Only a few big raw responses go out at once across all users, so you can also get 503 {"error":"raw_busy"} with Retry-After: 5. Ask for gzip and neither limit applies. Small responses (one sport like tennis, a few groups, in_play=1 on most sports) aren't limited either way. With an API key big raw responses aren't limited this way, but gzip is still much faster.

If the response has "warming": true (and few or no matches), the service has just restarted and is still loading the board. Wait about 30 seconds and fetch again. Matches and odds arrive within a couple of minutes.

2. Subscribe to all matches on one WebSocket

wss://moviodds.com/ws

Once the connection opens, send:

{"op":"subscribe"}

Leave out fixtures and groups to get updates for all matches and markets. New matches are included as their odds come in.

Plan limits apply soon. From then the WebSocket starts at the Pro plan: 5 connections. Business: 25.

You'll first get a snapshot for each match with cached odds. After that, delta messages arrive whenever quotes change. Matches without cached odds won't have a snapshot yet.

3. Apply each message to your match list

The fixture value tells you which match to update. It matches the id from the first request.

{
  "type": "delta",
  "fixture": "123456",
  "quotes": [{
    "fixture_id": "123456",
    "group_id": "981",
    "market_id": "100",
    "sel_id": "9001",
    "label": "Team A",
    "odds_dec": 2.6,
    "ts": "2026-09-11T12:00:05Z"
  }]
}

When a snapshot comes in, use it as the match's new odds list. A delta only contains changes, so update or add those quotes without clearing the rest

Within each match, use [group_id, market_id, sel_id] to identify a quote. If market_id is missing, use "".

Replace the whole quote when an update arrives. If suspended is missing, treat it as false.

A remove message tells you a market has closed or the match has left the board, so those selections are no longer bettable. {"type":"remove","fixture":"123456","quotes":[{"group_id":"981","market_id":"100","sel_id":"9001"}]} means drop those selections; {"type":"remove","fixture":"123456"} with no quotes means the whole match is gone, so drop it. Without it a stale last price would look bettable. If your client ignores remove, you are still covered: just before each remove we send the same selections in a delta marked suspended.

4. Handle new matches and reconnects

Check /catalog about once a minute for updated names, kickoff times and the current match list. Keep the odds you already have, and remove matches that have left the catalog. The socket also pushes a remove (see section 3) the moment a market closes or a match leaves the board, so you do not have to wait for the next catalog refresh to drop a stale price.

If odds arrive for a match you haven't seen yet, save them under its ID. The next catalog refresh will give you its details.

If a sport looks empty, check last_fixture_seen_by_sport on /health before assuming it is broken. It gives the last time we saw a fixture in each sport. A recent time means a quiet week; an old or missing one is worth reporting.

If the socket disconnects, reconnect and subscribe again. If you get a lagged message, fresh snapshots of the matches affected follow on their own; don't subscribe again. A connection's first 3 subscribe/unsubscribe messages apply at once, then one every 2 seconds; extra ones are merged and the latest wins. Each subscribe sends a full snapshot of every match you subscribe to, suspended selections included, so replace your copy of each match with it. Missed updates can't be replayed.

Close code 1001 means we restarted. Wait about 3 seconds, then retry at 3, 6, 12 and 24 seconds, then every 30. Code 1008 means our ping, sent every 30 seconds, went unanswered for 10 seconds, or your socket wasn't being read. In Node.js and browsers, keep long synchronous work off the event loop. More on the WebSocket page.

Two timestamps tell you different things. ts is when a price last changed. polled_at (per fixture, on /odds and /snapshot) is when we last successfully read fresh prices for that fixture, whether or not any price moved. To judge whether a match is still being priced, compare polled_at to server_time, not ts: a stable price (normal for pre-match and far-off matches) keeps an old ts while it is still being checked, so a large server_time − ts by itself does not mean stale. polled_at advances whenever we read a fixture's current prices, including when every price is suspended (a suspended market is still a successful read). Live matches are re-confirmed on a short cadence even when nothing is moving, so a suspended or quiet match keeps a recent polled_at. Only an empty or failed read leaves it where it was. On /ws, every snapshot carries the fixture's polled_at, and after each read a polled message confirms it: {"type":"polled","fixtures":{"202138001":"2026-10-14T21:40:05Z"},"groups":{"202138001":{"1777":"2026-10-14T21:40:05Z"}},"server_time":"..."}. groups comes when you subscribe to specific groups: it lists the ones a read covered, each with the time it was read. A polled always comes after every delta and remove of the reads it confirms on the same connection; you get at most one every 250 ms, covering every match read since the last one. A fixture that keeps showing up is being refreshed, even if no price moves; one that stops showing up is not. For a live match, a group is listed on every full re-read of the match and on every live update to it (the live feed covers all of a match's markets, so an update means that group's feed is current). If your connection falls behind you get {"type":"lagged","dropped":N} and fresh snapshots of the matches affected follow on their own. If we lose updates on our side you get {"type":"resync","server_dropped":N} and fresh snapshots of your matches follow on their own; you do not need to resubscribe. Suspended quotes are unavailable. While disconnected, mark your saved prices as stale.

Each market also has its own read time. polled_at on a fixture moves whenever we read any of its markets (one market a list or the live Full Time Result feed carries is enough), so it cannot tell you that Correct Score was last read yesterday. group_status can: per market group, {"polled_at": the last read that carried that market, "stale": true}, for example "group_status":{"40":{"polled_at":"2026-10-20T11:39:32Z"},"43":{"polled_at":"2026-10-15T17:19:59Z","stale":true}}. stale (sent only when true) means no read has confirmed that market's prices for 30 minutes. Matches more than 72 hours out are read every 30 minutes, so theirs is flagged at 60 minutes, and a market read on schedule never flips. Treat a stale market's prices as unconfirmed: they are the last ones bet365 showed us, kept because an empty answer from bet365 does not mean a market closed. A market that stays unconfirmed for longer (2 hours, or 4 hours for matches more than 72 hours out) may also be served suspended at its last price; it reopens as soon as a read carries it again. Read times survive our restarts, so a market comes back after a restart exactly as old as it was, never as freshly read. group_status is on every match of /odds (only the markets your groups filter keeps), on /snapshot, and on /quotes and /markets; a live fetch there reports the time of that fetch. On /ws it is on every snapshot and delta (the markets in that message), and a status message reports a market whose stale flag changed without a price change: {"type":"status","fixture":"201641238","group_status":{"43":{"polled_at":"2026-10-15T17:19:59Z","stale":true}},"server_time":"..."} (once a read confirms it again, the same message comes without stale). The times in a polled message's groups are the same per-market read times. /stream adds polled_at to its snapshot and sends event: polled {"fi","polled_at","markets"} after each re-read.

5. Price a bet builder

POST /betbuilder/price returns bet365's own Bet Builder (same-game multi) price for a set of legs on one match. bet365 correlates the legs, so the price is not the legs' odds multiplied together. Pre-match matches only. Send up to 50 slips per request, each with 2 to 12 legs; one request may mix slips from different matches.

Pricing (/betbuilder/price) needs Bet Builder access: a Bet Builder key (bb_…), or your account API key with Bet Builder. Bet Builder: not on Free; add-on $79/month on Starter, $50/month on Pro; included from Business. Questions: open a ticket on our Discord.

Find your legs in /odds

A leg is a quote's sel_id from the match's quotes in /odds. Find it by group_name (the market) plus the selection fields, which depend on the market:

Market typeSelection is inExample
Result-style (Full Time Result, Both Teams To Score, Double Chance, Draw No Bet, Half Time Result, Total Corners)labelgroup_name "Both Teams To Score", label "Yes"; "Total Corners", label "Under 6"
Totals (Goals Over/Under, Alternative Total Goals, Match Goals, Corners)side = Over/Under, line = the numberside "Over", line "2.5"
Correct Scorelabel = the score, side = the team it favourslabel "1-0"
Team Total Goalsside = the team, label = Over/Under and the lineside "Arsenal", label "Over 1.5"
Team Goals Rangeline = the team, handicap = the range, side = Yes/Noline "Wales", handicap "2-4", side "Yes"
Player props (Shots, Shots On Target, and the same layout in other sports: handball Player to Score, esports Player Total Kills/Deaths)line = the player name, side = the threshold, n2 = the player's teamline "Aitana Bonmati", side "2+"
One block per team (To Score In Half, Alternative Team Totals, Team TD Scorers)n2 = the team, the other fields as usualn2 "Arsenal", line "1st Half", side "Yes"

Most quotes have no label, so check which fields a market fills before mapping it. sel_ids belong to one match and can change, so re-read /odds before each pricing run rather than storing them for days.

Request and response

curl -X POST https://moviodds.com/betbuilder/price   -H 'Content-Type: application/json' -H 'X-API-Key: YOUR_KEY'   -d '{"slips":[{"fixture":"201750116","legs":["63643981","91275799"]}]}'

YOUR_KEY is your Bet Builder key (bb_…), or your key from the account page with the Bet Builder add-on.

{"server_time":"2026-09-30T05:10:00Z","results":[{
  "fixture":"201750116","home":"Roma (W)","away":"Barcelona (W)",
  "legs":[{"sel_id":"63643981","market":"Full Time Result","label":"Barcelona (W)","odds_dec":1.083},
          {"sel_id":"91275799","market":"Both Teams To Score","label":"Yes","odds_dec":1.8}],
  "status":"priced","odds_dec":2.15,"odds_frac":"23/20","naive_odds_dec":1.95,
  "priced_at":"2026-09-30T05:10:00Z"}]}

Results come back in request order, one per slip. The bet builder price is only ever odds_dec / odds_frac on a priced slip. Each leg's own odds_dec is that single selection's price, and naive_odds_dec (priced slips only) is the singles multiplied, for comparison; never bet at either. priced_at is when bet365 answered.

statusMeaningWhat to do
pricedbet365's current price for this exact combination.Use odds_dec.
unavailablebet365 declined this combination right now: suspended, contradictory legs, or a leg that can't be combined.Try later or change the legs.
errorNot priced; error says why.If retryable is true (a temporary error, markets still loading, or busy), retry in a minute. If false (invalid slip, unknown match or leg, match already started), retrying won't help: fix the slip or re-read /odds.

A request counts once against the rate limit however many slips it carries, so batch your slips.

6. Results of finished matches

GET /results?sport=<key> returns the matches that have finished, newest first, with the final score and, where the sport exposes them, the per-period scores (halves for soccer, sets for tennis, table tennis, volleyball and badminton, quarters for basketball and American football, periods for ice hockey, innings for baseball). Add &date=YYYY-MM-DD (UTC) to limit to one day, or &fi=<match id> for one match. For baseball, when we can't split the innings ourselves, they come from bet365's own inning scores, and only when those add up to the final score.

curl 'https://moviodds.com/results?sport=soccer'
{"sport":"soccer","count":1,"results":[{
  "fixture_id":"201150821","sport":"soccer","home":"Kosovo","away":"Austria",
  "league":"UEFA Nations League B","final_score":"1-0","status":"finished",
  "periods":[{"name":"1st Half","score":"0-0"},{"name":"2nd Half","score":"1-0"}],
  "finished_at":"2026-10-04T19:40:00Z"}]}

Each result's status is finished when the match reached full time (a player or side won the required sets, baseball reached the 9th inning, or in darts, snooker and esports a player or team won the legs, frames or maps the match format needs). It is unknown when the match stopped before that, usually because it was abandoned, suspended or postponed, or the sport has no finish model; the last score is still returned. finished_at is the last time the match was seen live, which is close to when it actually ended. When a match was decided beyond regulation the result adds "overtime":true, and for a tied ice-hockey score it adds a note that the shoot-out or overtime winning goal is not part of bet365's score feed.

source says where the list was read from: postgres (the full archive), or memory (only the last 72 hours or so; served when the archive is briefly unreachable, so older matches may be missing). A busy or timed-out read returns 503 with Retry-After; retry shortly rather than treating it as "no results".

Notes on specific sports:

Last score and match stats: bet365 removes a match from the live index seconds after it ends, so a score in the final seconds (a walk-off field goal, a buzzer-beater, a late e-soccer goal) can be missing from the last live score. When the match stats were following the match and are ahead of the last live score by one or two scoring plays (sport-specific: up to 2 goals in soccer and ice hockey, 6 points in basketball, 4 runs in baseball, 8 points in American football and rugby), updated no more than 3 minutes after the match was last seen live (1 minute for e-soccer), final_score is taken from the stats and the note says so. When the stats are further ahead, too late, or could be read either way round (for example 1-1 at the end and 2-1 in the stats, without confirmation of which team scored), a finished result becomes unknown with the last live score. On an unknown result a score taken from the stats is noted as "score from the match stats; end not confirmed". The stats in a result always use the result's home and away sides.

Ties: a tied basketball, baseball or American football result is returned unknown with a note, because those games do not end tied (the last score was most likely not seen). Exceptions: American football preseason, and baseball leagues that stop tied after extra innings (Korea after 11, Japan and Taiwan after 12). Some real ties are therefore returned unknown: NFL and CFL regular-season games tied after overtime, MLB spring training and other exhibition games called tied, and the first leg of a two-leg basketball tie that ends level. A tied ice-hockey result stays finished with "overtime":true, as described above.

A match that was only ever seen at 0-0 in its opening period, with no scoring and no period change, is treated as a bet365 placeholder that never really started and is not returned as a result.

Reference
FieldUse
home, away, leagueMatch names and competition, supplied by /odds and /catalog.
in_playTrue while the match is actually under way. A match bet365 lists on a court/table but has not started is not in play, and a finished match is dropped from in play once bet365 stops streaming it live or the results tracker records it finished. So in_play tracks real live play, not a stale "started" flag.
scoreLive scoreline while in play, in home-away order. One pair for goal/point sports ("1-0"). For the set sports it is the full set list: completed sets then the current one: tennis "6-4,2-3" (games), and table tennis, volleyball and badminton combine the completed games with the current game's points, e.g. "11-7,6-11,12-14,11-9,2-6" (four games won, current game 2-6). Absent before kickoff and when bet365 sends none.
linksbet365 deep links for the match, only when the request sent ?links=1. match is the one to open (live page in play, else pre-match page); prematch and live are the specific routes. Same link on any regional bet365 domain. Use a quote's sel_id to find a selection on the page.
group_id, group_nameMarket group ID and its display name. A group ID is global, so its group_name is the one stable English name for that market across every match, even when bet365's own feed labels it differently or in another language on some matches. It is absent only for a market bet365 never names anywhere.
period, market_keyOnly on markets whose name says which game, set, goal, over or time window they cover. bet365 keeps one group ID for the whole run and renames it as the match moves on, so period is the part that changes ("Game 2 Player Totals" gives "2", "Next 10 Minutes (50:00 - 59:59)" gives "50:00-59:59", "Asian Handicap (1-3)" gives "1-3") and market_key is group_id|period. Settle on market_key + sel_id; when market_key is missing, the group_id is the key.
market_id, sel_idSub-market and selection IDs. Keep IDs as strings.
labelSelection name. Use IDs for storage keys, not labels.
line, handicap, side, n2Optional market-specific details. n2 is the team a selection belongs to on player markets (the player's team) and on markets split into one block per team, like To Score In Half, Alternative Team Totals and Team TD Scorers, where both teams' rows otherwise look the same. On table tennis, volleyball and badminton grids, the Race to, Lead After and Odd/Even cells carry their target in line, with the player or team in side (for example line "5", "10 Points" or "Set 2").
odds_dec, odds_fracDecimal price and optional fractional price.
suspendedTrue means unavailable. Missing means false.
phaseWhich feed a price comes from: "inplay" for the live in-play market, "prematch" for a pre-match one. Only sent on matches that are in play, where a live match can show both, for example the pre-match Full Time Result (group 40, usually suspended by then) next to the live one (1777). Matches that haven't started leave it out, so no phase means pre-match. Sent on /odds, /snapshot and WebSocket snapshot and delta frames (not on remove keys, and not on /history or /closing).
tsWhen the price last changed, in UTC. An unchanged price keeps its old ts, so a large server_time − ts means "hasn't moved", not "stale". For liveness use polled_at.
polled_atWhen we last successfully read fresh prices for this fixture (whether or not any price moved), in UTC. Per fixture on /odds, /snapshot, WS snapshot frames and WS polled frames; absent until the match is first priced. A suspended market still advances it (a suspended price is a successful read), and live matches are re-confirmed on a short cadence even while quiet; only an empty or failed read does not advance it, so a rising server_time − polled_at means "not re-confirmed lately".
group_statusPer market group: polled_at, the last read that carried that market (whether or not a price moved), and stale: true when no read has confirmed it for 30 minutes (60 minutes for matches more than 72 hours out). On /odds (per match), /snapshot, /quotes, /markets and WS snapshot, delta and status messages. A stale market's prices are unconfirmed; one unconfirmed much longer may be served suspended until a read carries it again. Use it rather than the fixture's polled_at to judge one market: the fixture's moves when any of its markets is read.
last_seen, last_live_seenWhen the match was last listed (last_seen) and last seen in play (last_live_seen). For how fresh the odds are, use polled_at and ts.
server_timeThe server's UTC clock at send time, on /odds and /snapshot it is the moment of the response; on WS frames it is the batch time (≈ send time). Compute ages without trusting your own clock: server_time − ts = time since the price last moved; server_time − polled_at = time since we last re-confirmed the fixture's prices (the staleness signal, on /odds, /snapshot and WS snapshot/polled frames).

Without a key, limits are per IP: /odds 300 requests per minute; /history and /closing 120 per minute; /markets, /quotes, /fixtures and /inplay 120 per minute; the WebSocket 25 connections. Over the limit you get 429 (the body may be HTML, not JSON). Back off and retry. A big /odds response requested without gzip can get 429 raw_rate_limited or 503 raw_busy (see section 1). /markets, /quotes, /fixtures and /inplay can also return 429 with a Retry-After header when the server is busy. In both cases back off and retry, and use /odds, /snapshot and the WebSocket where you can. Check the HTTP status before parsing the body as JSON. With an API key the limits are per key instead; see section 9.

Send {"op":"ping"} to receive {"type":"pong"}. Send {"op":"unsubscribe"} to stop updates. Protocol errors arrive as {"type":"error","error":"..."}.

After reconnecting, each snapshot replaces that match's prices. If you keep your own copy of the odds, also reload /odds to drop matches that ended while you were away.

7. Historical odds and closing lines

Every price change we record is kept, so you can pull a selection's whole price timeline and its closing line after a match. Two read-only endpoints, limited to 120 requests per minute per IP.

A match can have a separate live id from its pre-match id. Both endpoints accept either one and return the whole record; fixture_ids lists the ids included and prematch_id names the pre-match one.

Plan limits apply soon: then Free gets the last 24 hours, Lite 7 days, Starter 30 days with closing lines, and full history needs Pro. Until then everyone gets everything.

Price timeline: GET /history

GET /history?fi=<match> returns the recorded price points for a match, oldest first. Narrow it with group (a market-group id), sel (a selection id), and a from/to time window (RFC3339 like 2026-10-04T12:00:00Z, or Unix seconds). Results are capped at limit rows (default 5000, max 50000); the newest rows within your window are kept, so pass a from/to or a sel to page back through a busy match.

curl 'https://moviodds.com/history?fi=201150680&sel=63643981&from=2026-10-04T00:00:00Z'

Race ids work too. GET /history?fi=<race_id> returns every recorded change of a runner's Fixed Win and Fixed Place price, scratching and suspension ("kind":"racing", oldest first, sel = the runner's sel_id), and GET /closing?fi=<race_id> each runner's last recorded price at or before the jump. Racing prices are recorded from 13 November 2026; earlier races have no history. The plan's history window applies the same way.

{"fixture_id":"201150680","fixture_ids":["201150680"],"count":3,"truncated":false,"limit":5000,"sel":"63643981","points":[
  {"ts":"2026-10-04T15:06:11Z","group_id":"40","group_name":"Full Time Result","market_id":"","sel_id":"63643981","label":"Home","odds_dec":2.00,"odds_frac":"1/1","suspended":false},
  {"ts":"2026-10-04T16:31:11Z","group_id":"40","group_name":"Full Time Result","sel_id":"63643981","label":"Home","odds_dec":1.90,"odds_frac":"10/11","suspended":false},
  {"ts":"2026-10-04T16:46:11Z","group_id":"40","group_name":"Full Time Result","sel_id":"63643981","label":"Home","odds_dec":3.50,"odds_frac":"5/2","suspended":false}]}

bet365 keeps one group_id for a market that rolls from period to period and renames it, for example "Next 10 Minutes (40:00-49:59)" becomes "(50:00-59:59)", or "Game 1 Race to" becomes "Game 2 Race to", and sometimes the same sel_id carries on under the new name. So when you store prices for these, keep group_name next to the ids, it's what tells the periods apart.

To make that easier, rows of these markets (on /odds, the WebSocket, /history and /closing) carry two extra fields. period is the bit of the name that changes: "2" for "Game 2 Race to", "40:00-49:59" for the ten minute window, "1/2/1" for "Set 1 - Game 2 1st Point". market_key is group_id and period glued with a |, like "2776|2". If you settle bets, key them on market_key + sel_id, and fall back to group_id when a row has no market_key (most markets don't have a period, so they don't get one).

Totals and handicap markets add the fields that pin the number: side ("O"/"U", or "H"/"A"), line and handicap (e.g. "side":"O","line":"2.5" for Over 2.5), and n2 (the second participant, where a market names one).

Each point carries ts (when that price was captured, UTC), the selection identity, odds_dec, and suspended. The identity fields are the same ones /odds quotes carry, so a point maps to a team/side/line without re-fetching /odds: group_id and group_name (the market), market_id, sel_id, label, and, on markets that use them, side, line, handicap and n2. Each identity field is present only when it has a value. odds_frac is a derived display fraction: the archive stores the decimal price, so treat odds_dec as authoritative. truncated is true when you hit the row cap; add a tighter window or filter and page back. fixture_ids lists every id the timeline was merged from; when it holds more than one, each point also carries a fixture_id telling you which id recorded it.

Closing line: GET /closing

GET /closing?fi=<match> returns, per selection, its pre-match close (pre_close: the last price recorded for it before kickoff, taken from the pre-match record) and its last recorded price (last: the final in-play price for a settled match, taken from whichever id recorded it last). Selections are keyed by (group_id, market_id, sel_id, group_name), so a period market bet365 renamed as the match went on (see above) gives one closing row per period name instead of only the last one; bet365 sometimes prices a winner market under one group id before kickoff and another in play, so a market's pre_close and last can appear on two selection rows: the pre_close always comes from the pre-match group.

Each selection row, and the pre_close/last points inside it, carry the same selection-identity fields as /odds and /history: group_name, plus side, line, handicap, n2 where the market uses them. A row maps to a team/side/line without a /odds round-trip. Each is present only when it has a value.

pre_close_basis says how the close was found: "kickoff" (the last price at or before the scheduled kickoff), "prematch-records" (the last price recorded under the pre-match id, when the scheduled kickoff isn't known) or "omitted" (no pre-match close is reported, because the match was only seen in play, or no price was recorded at or before the kickoff). When the basis is "omitted" the selections carry no pre_close. kickoff_estimated is true when the kickoff is an estimate (a live-clock reading, not bet365's scheduled start); an estimate is never used to pick the close. kickoff_known is false when no kickoff is known.

closed says whether the close is final or still provisional. It is false for an upcoming match, where pre_close just mirrors the current pre-match price and keeps moving until kickoff. It is true once the match has kicked off, gone in play, or finished. Treat a pre_close as a settled closing line only when closed is true.

curl 'https://moviodds.com/closing?fi=202266307'   # a live id, merged with its pre-match twin
{"fixture_id":"202266307","fixture_ids":["202266307","201714830"],"prematch_id":"201714830",
 "kickoff_utc":"2026-10-04T20:05:00Z","kickoff_known":true,"kickoff_estimated":false,
 "pre_close_basis":"kickoff","in_play":true,"closed":true,"selection_count":2,"selections":[
  {"group_id":"1441","group_name":"Match Lines","sel_id":"59223314","label":"Home","fixture_id":"201714830",
   "pre_close":{"ts":"2026-10-04T20:00:01Z","group_name":"Match Lines","label":"Home","odds_dec":5.5,"odds_frac":"9/2","suspended":false}},
  {"group_id":"1777","group_name":"Match Lines","sel_id":"59223314","label":"Home","fixture_id":"202266307",
   "last":{"ts":"2026-10-04T21:40:00Z","group_name":"Match Lines","label":"Home","odds_dec":12.0,"odds_frac":"11/1","suspended":false}}]}

Find a selection's sel_id the same way as for the bet builder (section 5): from a match's quotes in /odds. Both endpoints answer 503 with a Retry-After header if history is briefly unavailable (a busy or timed-out archive read); back off and retry.

8. Futures / outright markets

GET /outrights?sport=<key> returns season-long outright (futures) markets: a field of participants priced for one winner question, kept separate from the head-to-head /odds board. Covered sports: motor racing (formula1), golf, cycling, and the team-sport season futures american_football (NFL, NCAAF and CFL: to win outright, conference, division, MVP, regular season awards, Heisman, winning conference, team perfect / winless record, team undefeated, final exact forecast and the other markets bet365 lists on the Futures tab), basketball (NBA championship, conference, division, MVP, season awards and alternate win totals), ice_hockey (Stanley Cup, conference, division, awards), baseball (World Series, league, MVP), rugby_union and rugby_league (World Cup / NRL winner) and australian_rules (AFL Grand Final, Brownlow Medal, plus the AFL Women Grand Final winner), and soccer (each top league's winner, top goalscorer and relegation for the Champions League, Premier League, La Liga, Serie A, Bundesliga and Ligue 1). The per-team grid futures are served too: to make the playoffs (a Yes/No selection per team) and regular season wins (an Over/Under selection per team, each carrying that team's line). Omit sport or pass all for every enabled sport.

curl https://moviodds.com/outrights?sport=american_football

Each event carries its markets; each market has a market_id, a market_name, optional each_way terms, and a variable-size selections array of {sel_id, name, odds_dec, odds_frac} (a suspended runner has odds_dec 0). A grid market's selection also carries side (Yes/No or Over/Under) and, for an over/under line, line. Outright prices update every few minutes. Each event's polled_at is when its prices were last read successfully; a failed or empty read leaves it where it was (the last good prices keep being served), and last_attempt_at is the most recent read attempt of any outcome.

Key and dedupe markets on market_id, not group_id: group_id repeats across markets in the same event (the eight NFL division winners share one, and MLB lists two distinct World Series markets under one), while market_id is distinct and stable per market; where two markets share a name, column_name tells them apart. each_way.places is the real paying-place count read from the terms (E/W 1/2 1-2 pays 2, 1-2-3 pays 3, 1-2-3-4 pays 4).

bet365's featured outright widget first serves only a market's 12 shortest-priced runners. For those markets the feed follows bet365's own "Show more" request and serves the complete field, so the Super Bowl (all 32 teams), the conferences, NBA and NHL championships, NCAAF, MVP and the soccer Top Goalscorer come through in full. A market keeps "field_truncated": true with runners_shown only when bet365 offers no "Show more" for it (for example the MLB World Series during the postseason) or when that follow-up request was empty this cycle, in which case treat the field (and its below-100% book) as a partial top 12. A complete field (most markets, a 4-team NFL division, AFL/AFLW/rugby, F1/golf/cycling, or any market of 12 or fewer runners) omits both.

An unknown sport key returns 400 {"error":"unknown sport key: X"}. A valid sport with no futures (covered but warming, or a sport the feature does not cover) returns a 200 with an empty events list. When the feature is off entirely the response is {"enabled":false}. Full schema in openapi.json.

9. API keys

Get a free API key on the account page: sign in with your email and create one, it takes about 30 seconds. A key is optional for now: requests without a key keep working within the per-IP limits (section 6).

Send the key in the X-API-Key header on every request (or, where a header is not possible, as the ?key= query parameter):

curl -H "X-API-Key: YOUR_KEY" "https://moviodds.com/odds?sport=soccer"
import requests

KEY = "YOUR_KEY"
r = requests.get("https://moviodds.com/odds", params={"sport": "soccer"},
                 headers={"X-API-Key": KEY})
r.raise_for_status()
odds = r.json()
const res = await fetch("https://moviodds.com/odds?sport=soccer", {
  headers: { "X-API-Key": "YOUR_KEY" },
});
const odds = await res.json();

For the WebSocket, send the same header when you connect. Browsers can't set headers on a WebSocket, so there you can put the key in the URL instead: wss://moviodds.com/ws?key=YOUR_KEY. Use the header everywhere else, because a URL can end up in logs and browser history.

import websockets
ws = await websockets.connect("wss://moviodds.com/ws", additional_headers={"X-API-Key": KEY})

With a key you can also get big /odds boards uncompressed without the per-IP raw limit from section 1, though asking for gzip is still a lot faster.

A free key has no request limit (except /betbuilder/price: 120 a minute per IP), and you can hold 25 WebSocket connections per key. Plan limits apply soon: then Free gets 5,000 requests a month per account (all your keys together, UTC), on every endpoint, up to 30 a minute per key, and the main lines only (match result, handicap and total, plus double chance and both teams to score in soccer); Lite 1,000 a day on the main lines; a reply trimmed to the main lines carries "markets":"main". No WebSocket on Free; one connection for up to 3 leagues on Lite and Starter; 5 connections on Pro, 25 on Business. Over the connection limit you get 429 with a Retry-After header in seconds. Wait that long, then continue.

Business and Enterprise can pin leagues and single matches on the account page; pinned matches are re-read at the 30-second cadence however far away kickoff is. Other matches follow the normal schedule by time to kickoff.

If the key is wrong, revoked or mistyped you get an Unauthorized response with {"error":"invalid or revoked API key"}. A bad key is not treated as "no key", so fix it or remove the header. Bet Builder keys (bb_…, section 5) keep working: they unlock /betbuilder/price and are accepted as a key on every other endpoint too (25 WebSocket connections per key).

Keep the key out of public code and front-end bundles. If it leaks, revoke it on the account page and make a new one.

10. Live match stats

Every in-play match bet365 tracks in soccer, basketball, tennis, ice hockey, American football, rugby union, baseball, darts, volleyball, e-soccer, e-basketball, Counter-Strike and VALORANT can carry live stats. They are opt-in everywhere: add stats=1 to /odds or /catalog (for example /odds?sport=soccer&in_play=1&stats=1) and each in-play match carries a stats object; add stats=1 to /results for each result's full-time stats, baseball and American football results included; on the WebSocket, subscribe with "stats":true to get a {"type":"stats","fixture":"<id>","stats":{…},"server_time":"…"} message (see below). Without stats=1 (or "stats":true) no stats field or message appears. stats.sport names the shape; a value bet365 doesn't track for a match is left out.

On the WebSocket, stats are opt-in: {"op":"subscribe","stats":true} (with or without fixtures/groups; the group filter doesn't apply to stats). Each subscribed match's stats follows its snapshot, then comes on each change, at most one per match per second: changes inside that second are merged and you get the latest. Each message carries the match's complete stats, so replace your copy. A subscribe without "stats":true turns them off, as does {"op":"unsubscribe"}. Stats are best effort: a dropped one may not be re-sent and needs no resync; the next change brings the current values.

{"sport":"basketball","period":2,
 "home":{"points":32,"three_pointers":2,"two_pointers":11,"free_throws":4,"free_throw_pct":66.7,
         "timeouts_remaining":5,"fouls":4,"periods":[30,2]},
 "away":{"points":20,"three_pointers":2,"two_pointers":6,"free_throws":2,"free_throw_pct":100,
         "timeouts_remaining":4,"fouls":4,"periods":[20,0]},
 "summary":["Score After 1st Quarter - 30-20"]}
{"sport":"tennis","current_set":2,"surface":"Hard","format":"best_of_3",
 "home":{"aces":2,"double_faults":0,"first_serve_win_pct":59,"break_point_conversion_pct":100,
         "games":0,"point":"40","serving":true,"sets":[2,0]},
 "away":{"aces":2,"double_faults":1,"first_serve_win_pct":87,"break_point_conversion_pct":60,
         "games":1,"point":"30","sets":[6,1]},
 "summary":["Game 8 - Nikoloz Basilashvili - breaks to 40","Game 9 - Nikoloz Basilashvili - holds to 30"]}
{"sport":"baseball",
 "home":{"periods":[0,0,0],"runs":0,"hits":1},"away":{"periods":[1,1,1],"runs":3,"hits":7},
 "players":[{"id":"bat-home-delauter","name":"DeLauter","team":"home","batting_order":3,
             "batting":{"at_bats":1,"runs":0,"hits":1,"rbi":0}},
            {"id":"pitch-home-herrin","name":"Herrin","team":"home",
             "pitching":{"innings_pitched":"1.0","hits":2,"runs":1,"earned_runs":1,"walks":0,"strikeouts":0}}, …]}
{"sport":"american_football",
 "away":{"points":12,"first_downs":17,"third_down_conversions":4,"third_down_attempts":10,
         "time_of_possession_secs":1622, …},
 "players":[{"id":"13296","name":"J Brissett","team":"away",
             "passing":{"completions":18,"attempts":25,"yards":176,"avg":7.04,"touchdowns":0,"interceptions":1,"rating":74.75},
             "rushing":{"attempts":1,"yards":1,"avg":1,"touchdowns":0,"long":1}}, …]}

Match tracker

The match tracker is what bet365 draws on its in-play pitch or court: where the ball is, who has it, and the play, such as "Attack" or "Dangerous Attack". To get it, subscribe with "tracker":true.

{"op":"subscribe","sports":["soccer"],"tracker":true}

You get the current play of each match you follow, then a message each time the play changes or the ball moves:

{"type":"tracker","fixture":"204463436",
 "tracker":{"code":11001,"state":"attack","team":"home","ball":{"x":0.7,"y":0.77},"player":"L Lin","seq":12},
 "server_time":"2026-11-14T12:19:41.2Z"}

Most messages move the ball within the same play. Expect one every few seconds per match, and at most four per match per second. A subscribe without "tracker":true stops them, and so does {"op":"unsubscribe"}. You get tracker messages for the matches whose odds you receive.

Soccer

Basketball

Tennis

Volleyball

Ice hockey

Handball

Darts

{"type":"tracker","fixture":"204350912",
 "tracker":{"code":21133,"state":"visit_total","team":"away","seq":58,
  "darts":{"thrown":["I20","I19","T19"],"left":405,"visit_total":96,"next":"home"}},
 "server_time":"2026-11-14T13:27:36.4Z"}

Cricket

{"type":"tracker","fixture":"204600001",
 "tracker":{"code":21168,"state":"runs","team":"away","seq":31,"detail":"4",
  "cricket":{"over":2,"ball":6,"deliveries":["1","0","6","1","0","4"]}},
 "server_time":"2026-11-14T13:36:20.8Z"}
{"type":"tracker","fixture":"204551757",
 "tracker":{"code":11206,"state":"bowling","team":"home","player":"SH Johnson","seq":58,
  "cricket":{"over":4,"ball":1,"deliveries":["2","0","4","0","0","0"],
   "batters":[{"name":"T Banton","runs":5,"balls":4,"on_strike":true},{"name":"BM Duckett","runs":8,"balls":14}],
   "bowler":"SH Johnson"}},
 "server_time":"2026-11-15T03:43:01.1Z"}

11. bet365.com odds (site=com)

By default every price comes from www.bet365.com.au. Add site=com to read the www.bet365.com board instead. Leaving the parameter out, or sending site=com.au, gives exactly the responses described above.

curl -H "Accept-Encoding: gzip" "https://moviodds.com/odds?sport=soccer&site=com"
wss://moviodds.com/ws?site=com

The response has the same shape, plus a top-level "site":"com". On the WebSocket you choose the site when you connect: /ws?site=com gets the .com snapshots and changes, and every message on that connection carries "site":"com". The subscribe message is the same as in section 2. You can also add "site":"com" to it, but a subscribe that names a different site from the connection's is refused with an error message. Messages on a plain /ws connection have no site field. One connection reads one site, so open a second connection to follow both. Each one counts toward your connection limit.

12. Virtual sports

bet365 runs computer-generated ("virtual") sports around the clock: football, football match day, horse racing, greyhounds, trotting, motor racing, speedway, cycling, tennis, basketball, ice hockey, American football, baseball, cricket, darts, Counter-Strike and golf. Each competition produces an event every 1 to 8 minutes with a fixed-price coupon. The prices are set when the event is created and never move, so there is no price timeline and no WebSocket topic for them. /virtuals is a separate feed from /odds and uses its own ids.

GET /virtuals is the catalogue: every class with its competitions, each competition's cadence_s (seconds between events), next (the next start and its event id), current_event_id, and how many of the last hour's events were priced. coupon is false for golf, whose markets bet365 publishes in-running instead of on a coupon.

curl 'https://moviodds.com/virtuals'

GET /virtuals/events?comp=<competition_id> (or class=<class_id>) lists events newest first with their start time, status and markets. The default window is the last hour plus the next 10 minutes. from and to (RFC 3339 or unix seconds) move it. status=pending|priced|unavailable|nocoupon filters, and markets=0 leaves the markets out. The default limit is 200 (1 to 2000). A window older than two hours also reads the event archive ("source":"db+memory").

curl 'https://moviodds.com/virtuals/events?comp=20940364&status=priced&limit=5'

GET /virtuals/event/<event_id> returns one event. status is pending while bet365 has announced the event but not yet served its coupon. Events are announced about 5 minutes ahead. The status turns priced once the coupon is stored, and unavailable when bet365 answered empty until two minutes after the start. Each market lists its selections with sel_id, name, the fractional odds and decimal, and for totals and handicaps the line and side. participants are the two sides of a head-to-head event, home first. fixture_id is bet365's fixture id for the event. The event id is the one in the URL.

A race has one Win market. Its selections are the runners, with the saddle or trap number in line. Horse racing and trotting runners also carry jockey (the driver in trotting) and silk, the URL of the silk image bet365 shows on its race card. The silk follows the saddle number. It is a public PNG of 45 by 34 pixels. Greyhound runners have no jockey and no silk.

curl 'https://moviodds.com/virtuals/event/141216426'

GET /virtuals/results?comp=<competition_id> (or class=) lists the events that have a result, newest start first. The default window is the last 6 hours. The default limit is 1000 (1 to 2000). markets=1 adds the coupon. The same result object sits on /virtuals/event/<event_id> once known. A match has home, away and score, and winners lists the winning selection and its price per market. A race has placings (position, number, runner, price, jockey) and dividends (forecast and tricast). seen_at is when we stored the result.

Golf results have the course in title, the hole's par, and each player's strokes on the hole in score, first player first. They name no players. A tied hole lists Tie in winners. Golf winners carry no price, only the selection.

To read the results as they come in, poll GET /virtuals/results?since=<time>. since is an RFC 3339 time such as 2026-11-14T17:20:00Z. The reply holds the results stored after it, oldest first, and next_since. Send next_since as since on your next poll. An empty reply gives back your own since. When more is true the limit cut the reply, so poll again straight away. A result can come again, for example after our server restarts. Skip one whose event_id you already have.

For your first poll, take server_time from any reply and go back as far as the history you want. An older time works too, even the zero time 0001-01-01T00:00:00Z. The results then come oldest first, a page at a time. A since more than a minute after server_time gets 400. If the archive cannot be read, the reply is 503 with Retry-After. Poll again with the same since.

A since poll has no start window of its own. comp, class and status filter it. from and to filter it too if you send them, but then a late result for an event outside them is never served, so leaving them out is the safe choice.

curl 'https://moviodds.com/virtuals/results?since=2026-11-14T17:20:00Z'

A result arrives a few minutes after its event starts. On the products that run every minute it usually takes 2 to 3 minutes. On slower products such as cricket and Counter-Strike it usually takes 6 to 8 minutes. A client that reads result from /virtuals/events, or polls by start time, can miss the late ones. bet365 lists only the last two results per competition, so a few events never get a result.

Virtual events are not on /odds, /catalog, /history or the WebSocket. Virtual sports are part of the Pro plan and above. Plan limits apply soon: from then a Free, Lite or Starter key gets 403 plan_required on /virtuals. Requests count toward your plan's budget like any other endpoint.