How to get Betfair lay odds (and the alternatives)

Betfair publishes a developer API, so you can get its lay odds directly. You register, get a key, and request the exchange's prices. But those prices arrive raw and single-exchange: you still have to pair each lay to a bookmaker back price yourself, and you only see one exchange. The alternative is a feed that delivers lay already matched across Betfair, Smarkets and Matchbook, paired to the bookmaker back price, with a rating attached. This guide covers both routes and which one fits which team.

Does Betfair have a public API for lay odds?

Yes. Unlike bet365, Betfair runs a documented developer programme with a real API for its exchange. You register for an application key, authenticate, and request market prices, including the available lay prices and the size behind them. This is a legitimate, supported route, and for a team that only needs Betfair it is a reasonable place to start.

It is worth being clear about what the API gives you and what it leaves to you. It gives you Betfair's own prices. It does not give you anyone else's exchange, and it does not give you the bookmaker back price you need to make a lay price mean anything for matched betting or arbitrage.

What the Betfair API route costs you

The direct route is real, but it comes with four trade-offs that most teams underestimate when they scope it.

• Single exchange. You see Betfair and only Betfair. The best lay price for a selection is often on Smarkets or Matchbook, and you cannot see it. That gap is exactly what exchange and lay coverage is about.
• Raw data you must parse. The response is market and price data you have to map into your own model: markets, selections, and the price ladder. Useful, but it is a starting point, not a finished signal.
• A delay on delayed-data keys. The free application key returns delayed prices, not live ones. We cover what that means in practice in the Betfair API 5-second delay. It shapes what you can honestly build.
• Integration and upkeep stay with you. Authentication, session management, market mapping, and following the API's changes are all your ongoing responsibility, for one exchange.

None of this makes the API a bad choice. It makes it a partial one. You get one exchange's lay prices, cleanly, and you own everything that turns them into something a matched-betting or arbitrage product can use.

Why lay odds only matter paired to a back price

A lay price on its own is not an opportunity. The signal a matched-betting or arbitrage product runs on is a relationship: the bookmaker back price and the exchange lay price for the same selection, plus enough liquidity for the lay to be real. If you understand that pairing, back and lay explained covers it fully.

This is the work the Betfair API leaves undone. It hands you the lay side. You still have to source the bookmaker back prices, pair them to the right selection, compute the position between them, and check the lay is liquid enough to place. Doing that across 60+ books, against three exchanges, is the whole job.

The alternative: lay already matched across three exchanges

A managed feed delivers the lay side already consolidated across Betfair, Smarkets and Matchbook, and already paired to the bookmaker back price. Instead of one exchange's raw prices, you receive the best lay for each selection, matched to the back odds from 60+ UK books with bet365 included, with a rating and the qualifying_loss computed for you. Here is the shape of a single row (illustrative, not live data):

{
  "event": "Arsenal vs Chelsea",
  "market": "match_odds",
  "selection": "Arsenal",
  "back": { "bookmaker": "bet365", "odds": 2.10 },
  "lay":  { "exchange": "betfair", "odds": 2.14, "liquidity": 1840 },
  "rating": 98.1,
  "qualifying_loss": -0.12
  // ... region, feed_type and freshness fields elided
}

The lay block carries the exchange the price came from, the lay odds, and the liquidity behind it. Because the feed consolidates three exchanges, that exchange is whichever offered the best usable lay, not just Betfair. The back block is the paired bookmaker price. The direct Betfair API can give you the lay block for one exchange only, and never the pairing, the rating, or the qualifying_loss. That pairing is the product.

Our honest posture on speed is pre-match polling on roughly a few-second cycle, which suits pre-match matched betting and pre-match arbitrage. Freshness, uptime and coverage are published on the coverage dashboard rather than asserted, so you can check the claim before you rely on it.

Which route fits your team?

The decision comes down to how many exchanges you need and how much of the pairing you want to own.

If Betfair alone is genuinely all you need, and lay prices without the back pairing are enough for your use, the direct API is a fair choice. For a matched-betting or arbitrage product, where the opportunity is the back/lay pair and the best lay may sit on any of three exchanges, the managed feed removes the part that never finishes: the pairing, the multi-exchange consolidation, and the upkeep.

The short answer

You can get Betfair lay odds directly from Betfair's public API, cleanly, for one exchange, with the pairing and upkeep left to you. Or you can license a feed that delivers lay already matched across Betfair, Smarkets and Matchbook, paired to bookmaker back prices from 60+ UK books with bet365 included. OddsRelay delivers the second, and it powers a leading UK matched-betting platform today. You can start with a free trial, or see what is live right now on the coverage dashboard.