Blog
Page 7 of 8. The data layer behind matched betting, arbitrage and odds comparison, written by the team that maintains it.
Fundamentals
What every field in a good odds API response is for, walked one at a time: the event/market/selection keys, the back and lay blocks, rating and qualifying_loss, and the envelope around them.
· 6 min read
Exchange & lay data
Betfair delays data on a delayed application key; live, undelayed prices need a live key that meets Betfair's requirements. Here's what that means for your build, and when it matters.
· 5 min read
Matched betting & oddsmatcher
Matched betting runs on one thing: a bookmaker back price paired with the current exchange lay price, with a rating and qualifying loss attached. This is the complete picture of that data layer, and how to ship it without building the matcher.
· 7 min read
Matched betting & oddsmatcher
Each-way and extra-place offers can't be expressed as a single back/lay pair. Here is the extra data they need, and how an each-way feed carries the place terms and the two-part matched calculation.
· 6 min read
Buying vs building
A tipster platform lives or dies on the odds it prices tips with. Here is the data layer underneath: broad coverage with bet365, identifiers that hold across time, and freshness enough to record the price when a tip goes out.
· 5 min read
bet365 odds data
DIY bet365 looks like a one-off build and turns into a permanent maintenance job. Here's the true ongoing burden, what it costs your actual product, and when building is still the right call.
· 6 min read
bet365 odds data
Matched betting on bet365 isn't about the back price alone. Here's the data an oddsmatcher actually needs: the bet365 back paired with a live exchange lay, with rating and qualifying loss attached.
· 5 min read
Arbitrage & value betting
Arbitrage and value betting look similar from the outside and differ sharply underneath. Here is the comparison from a data angle: different risk profiles, different data needs, one feed that serves both.
· 5 min read
Fundamentals
Odds change continuously, not at discrete events, so polling with ETag/304 fits the data better than webhooks. Here's the plain comparison, and why OddsRelay is pull-based.
· 5 min read