Data · Football data
Football fixtures, prices and results
Association football is usually the largest sport in a coupon. This page is about the data an operator needs to render that coupon: fixtures, competitions, prices, scores and results.
What a football record has to contain
It is not a hosted sportsbook, and it is not a claim that every league is included.
A fixture needs a stable id, a competition, a kickoff in a stated timezone, and the two sides. Prices hang off markets on that id: 1X2, totals, handicaps, and whatever else the feed actually covers for that competition. If your coupon shows a market the feed did not send, you invented it. Map markets explicitly. Do not assume every league has the same set.
In-play prices move when something happens on the pitch. A goal, a red card or a VAR review should be able to suspend the market. The score message and the price message are different records. If you only listen to prices, you will be late on the event that made them change. Results are a third record, used to settle, and they can be corrected. Settlement should follow the corrected result, with the correction visible in the file.
Coverage is a rights question. A feed that includes a competition in one contract may omit it in another. We do not publish a league list on this page, because the list you can use is the one in your contract. The sports data page explains the feed as a whole. The sportsbook page is the alternative when you want a hosted coupon instead of building one.
Half-time, extra time and a postponed kickoff
Half-time and full-time prices share a fixture and still close on different clocks. Shut the interval market when the half ends, and keep the period on the price. Paying that interval from the final score is a mapping error.
A postponement overwrites the kickoff on the same fixture id. Extra time and penalties arrive for competitions that use them, usual in cups and rare in a league. Booking, corner and scorer prices appear only where that competition's file includes them.
Football records the coupon has to keep apart
| Record | Keep on it | If the field is thin |
|---|---|---|
| Fixture | Id, competition, kickoff with a timezone, both clubs | A renamed club forks one match into two coupons |
| Price | Selections, period, and whether the market is open or suspended | The 1X2 still looks tradeable after a goal |
| Incident | Goal, red card or VAR review, with the match minute | The coupon hears about the stoppage only from a later price |
| Result | Official score, status, and a correction that replaces an earlier file | Finance pays the first number after officials change the score |
Building the football coupon
- 01
Stable fixture id
Key every market and every score update to the fixture id, not to the team names.
- 02
Suspend on events
Use score and incident messages to suspend prices. Do not wait for the next price tick.
- 03
Corrected results
Settle from the corrected result message, and keep both versions in the audit log.
Not every competition is in every contract
Ask which football competitions your data contract includes. A public page cannot promise the Premier League, a domestic cup or a youth league.
Six questions before you build the football coupon
- Which competitions, by name and tier, and which of those carry in-play prices. A second-division fixture priced pre-match only behaves differently from a top-flight in-play one.
- Whether line-ups and incidents arrive for the competitions you plan to show first-goalscorer or card markets on. Without them those markets are display furniture.
- How the feed behaves around a delayed kickoff, meaning the same fixture id with a replaced time, and when prices lock before kickoff.
- Whether accumulators across competitions are permitted by the data terms, since some rights carve-outs apply per competition.
- What the status message set is, exactly: open, suspended, closed, abandoned, postponed. Enumerate them before you code against them.
- Who applies the void rule on an abandoned match, your trading policy or a supplier default. The sportsbook frame settles that inside the frame; a data route settles it in your own rules.
Cases that break a naive accumulator engine
Worked from a four-fold coupon. Each row is a real shape, not a hypothetical.
| Case | What the engine should do | What naive engines do |
|---|---|---|
| One leg's match is postponed | Void that leg, reprice the coupon as a treble, show the change to the player | Settle on the original four results and wait for the complaint |
| A leg is abandoned before half-time | Apply your void policy to that leg and keep the others live | Void the entire coupon, paying nothing on three settled matches |
| Two legs kick off at once | Track each leg on its own fixture id | Poll one combined endpoint and mix the two matches' states |
| A goalscorer leg voids on its own rule | Void that leg alone and state the rule beside it | Void every goalscorer leg in the coupon because one was unclear |
| A corrected result arrives after payment | Re-run settlement from the corrected file and adjust the ledger visibly | Treat the correction as an error and hide it |
Small fields that decide whether the coupon is trusted
A kickoff printed without a timezone is a complaint generator for any brand with players in more than one country, which is most of them. Store the kickoff in one canonical timezone, display it in the player's, and label the convention on the coupon. The sports data page treats the fixture record as the anchor for everything else; the kickoff field is the part of it players actually read.
The other small field is the competition name as the feed spells it. Free-texting your own labels forks the fixture list the first time a supplier renames a cup. Display the name the feed sent, keep your internal labels mapped separately, and the coupon survives a supplier reorganisation without a data migration.
FAQ
Questions operators ask
Is this the same product as the hosted sportsbook?
No. The hosted sportsbook draws the coupon for you. This page is for teams who render fixtures and prices in their own product and only need the data.
Are cards, corners and scorer prices included for every league?
Only when that competition's file carries them. Leave off any market the feed did not send.
Who sets the void rule when a match is abandoned?
Your trading rules, applied to the status on the result message. The feed reports an abandonment or a correction. It does not publish one void policy for every competition.
Can we run cards and corners markets from this feed?
Where that competition's file includes them. Ask per competition, and price nothing the feed did not send. A corner market without corner events in the file is a market you invented.
How do we handle a match with no result message yet?
Bets stay open until a result or an abandonment status arrives. Do not settle from a score you saw elsewhere; the result message, corrections included, is the settlement input.
Is this feed enough for an in-play football book?
Enough for a modest one, if your suspension is driven by incidents and your pricing tolerates seconds of lag. A heavyweight in-play operation should compare this against the hosted sportsbook before committing either way.
Keep reading
Related pages
- Product · Sports dataSports dataFixtures, pre-match and live odds, scores and results for operators who build their own sportsbook front end and settle bets themselves.Read
- Product · SportsbookSportsbookAdd pre-match, in-play, esports and virtual sport as a wallet iframe, or take the odds feed and build a betslip your traders run.Read
- Data · Tennis dataTennis dataTennis fixtures, set scores and prices for your own coupon. A mid-match retirement does not settle like a completed match.Read
- Catalogue · Virtual eventsVirtual eventsScheduled virtual football, racing and tennis run on a fixed clock. They are not a sportsbook, not a slot, and not in-play.Read
Get a written quote and sandbox access
Tell us your licence, target markets and products. You get the GGR rate in writing, the studio list for your markets and sandbox credentials.