Football odds API: current availability

If you arrived here looking for a football odds feed, the short answer is that we do not currently publish one. There is no odds path in the public catalogue, no odds fields in any published response we document, and no sample we can show you. Subscribing to Starter, Growth or Pro does not give you odds data, and there is no hidden switch or add-on that enables it on request today.

We would rather you learn that from this page than from a failed integration. Plenty of data providers list odds on a features grid and then deliver something narrower. We have chosen to say nothing is available until something actually is, and to keep the catalogue as the single source of truth for what you can call.

FootballAPI.net is a data provider, not a bookmaker. We do not take bets, publish tips or advise on wagering, and none of our published feeds should be read as an indication of likely results.

People search for odds APIs, and some of them are also evaluating fixtures, scores and statistics for the same product. A clear page about what is not available saves both sides time. It also gives us a place to describe how to plan a product so that a missing odds source does not block the parts you can build now.

Nothing on this page is a roadmap commitment. We are not announcing an odds feed, a date or a price. If that changes, the catalogue, changelog and this page will change with it.

Many products that eventually show prices start with the football data underneath them: the fixture list, match state and team context. Those parts are available today and can be built independently. Design your data model so that the match identifier is the anchor and any price information is an optional, separately sourced attachment that may be absent.

Concretely, that means your match record should not have required odds columns. A missing price should render as nothing, not as a zero or a dash that implies a market existed. If you later license prices from a separate supplier, you will need your own mapping between their match references and our source identifiers, and that mapping is your responsibility to verify.

Some published feeds can look adjacent to odds. Predicted line-ups describe expected starting players; they say nothing about result probabilities. The in-play mapping feed relates identifiers; it carries no prices. Head-to-head records describe past meetings; they are history, not a forecast. Please do not repackage any of these as betting signals, and do not describe our data as odds in your own marketing.

Statistics such as shots or possession are records of what happened. Turning them into probabilities is modelling work that you own entirely, along with any regulatory duties that come with publishing it.

Our standard plans are Starter at EUR 29 a month for five selected leagues and 5,000 successful requests per UTC day, Growth at EUR 99 for all available package leagues and 25,000 requests, and Pro at EUR 249 for all available package leagues and 250,000 requests. None of them includes odds. Starter additionally excludes global odds-related services, profiles, head-to-head and images, so if you see those listed elsewhere as Starter features, they are not.

Successful requests beyond the daily inclusion cost EUR 0.002 each on the monthly EUR invoice, and failed or denied requests are not billed. If you are subscribing only because you hope odds will appear, please do not; talk to us first.

If you look elsewhere for prices, a few questions will save trouble regardless of which supplier you choose. Ask how their match references are defined and whether they offer any documented way to relate them to other data sources, because you will need a reliable mapping to our string match identifiers. Ask what licence covers display, storage and redistribution of prices, and in which territories. Ask how quickly prices are withdrawn when a market closes, since showing a stale price can create real problems for your users.

Ask too about their handling of postponed and abandoned matches, and whether they can show you documentation for their status values. Those edge cases are where joins between two suppliers most often break. Finally, test the mapping yourself on a full round of matches before launch, and design your product so that a failed mapping hides the price rather than attaching it to the wrong game.

If odds are central to your product, contact support and describe the need precisely: the competitions, the kind of market information you mean, how fresh it needs to be, where it would be displayed and in which countries. That detail tells us whether there is anything sensible to discuss. It does not reserve capacity, create a waiting list position or commit us to building anything.

We will answer honestly, and the most likely answer today is that we cannot supply it. If that is the case you will hear it directly rather than after a contract. Use the contact page on this site; we do not take requirements through third-party forms.

Some teams need odds for one screen and ordinary football data for everything else. If that describes you, it is reasonable to evaluate FootballAPI.net for the non-price parts while sourcing prices elsewhere. Begin with the catalogue, request a fixtures schedule and a scores snapshot for a competition you care about, and check whether the identifiers, structure and coverage suit your product. Do that before you think about prices at all.

Then write down the boundary explicitly in your own design document: which screens use our feeds, which use another supplier, and how the two are joined. A written boundary prevents a common failure in which a developer assumes the same vendor supplies both, builds a combined model, and only discovers the gap at launch. It also makes your licensing review simpler, because each source can be checked against its own terms.

Finally, check your request budget without odds in it. A product that polls prices every few seconds has a very different traffic profile from one that refreshes fixtures a few times a day. Our plans are sized for football data, and the daily inclusion and per-second safety ceiling should be judged against the football-data traffic you will actually send us.

Any service that displays prices sits close to regulated activity in many places. Responsibility for licensing, age gating, advertising rules and consumer protection belongs to the business displaying the prices. Buying football data from us does not transfer or reduce those obligations, and nothing we publish grants rights to third-party odds content.