MCP server
Tools for events, odds, line movement, and streams. Bets endpoints are support-approved.
Request normalized Betfair prices for covered pre-match events with bookmakers=betfair, then follow supported changes through SSE or WebSocket.
{
"event_id": "$EVENT_ID",
"items": [
{
"bookmaker": "betfair",
"bet_type": "moneyline 3w",
"period_str": "full time",
"side": "home",
"selection_name": "Manchester City",
"odds": 2.08
},
{
"bookmaker": "betfair",
"bet_type": "moneyline 3w",
"period_str": "full time",
"side": "draw",
"selection_name": "Draw",
"odds": 3.55
}
],
"resume": "1784092451749-0"
}
betfair bookmaker key.
Use the normalized bet_type values below when working with Betfair prices.
| Market | API bet_type | What it covers |
|---|---|---|
| Moneyline |
moneyline
|
Winner prices for covered two-way events. |
| Three-way moneyline |
moneyline 3w
|
Home, draw, and away prices for covered soccer events. |
| Handicap |
handicap
|
Line-based prices with the selection side and handicap value kept separate. |
| Total |
total
|
Over and under prices for supported full-event and period totals. |
| Team total |
team total
|
Over and under prices for one team's score where supplied. |
Betfair prices are returned only when Betfair is available for the selected event and market. Confirm the current catalog and event snapshot before depending on this source.
Tools for events, odds, line movement, and streams. Bets endpoints are support-approved.
Agent-ready instructions.
TypeScript, Python, Postman and example builds.
Sports and racing odds coverage for agent workflows.
Lightweight streaming updates for dashboards and alerts.
Bidirectional streams for richer pre-match products.
Find a covered event, confirm Betfair is attached, and request its current prices with bookmakers=betfair.
Create an API key and request GET /v1/bookmakers. Confirm that the canonical betfair key is available to your account and attached to the event you need.
Request GET /v1/events/{event_id}/odds/snapshot with bookmakers=betfair and retain the response freshness fields.
Keep the event, market, period, selection, price, availability, freshness, and resume fields your product needs.
Open the matching SSE or WebSocket odds stream, resume from the latest token after reconnecting, and reload the snapshot after a resync event.
Choose a monthly plan based on request volume, rate limits, and support.
Answers about Betfair coverage, bookmaker filters, normalized odds, streaming, and affiliation.
No. odds-api is an independent data service and is not affiliated with, endorsed by, or sponsored by Betfair. It provides market data only and does not place bets or manage Betfair customer accounts.
Request GET /v1/events/{event_id}/odds/snapshot with bookmakers=betfair. Covered rows use the same normalized market, period, selection, price, and freshness fields as other bookmaker odds.
Use bookmakers=betfair on supported sports odds endpoints after confirming the betfair key is available to your account and attached to the event.
Yes, for covered pre-match odds. Start with the REST snapshot, then use its resume token with the matching SSE or WebSocket odds endpoint. Reload the snapshot after a resync event.
No. odds-api currently provides pre-match Betfair coverage rather than in-play odds after an event has started.
Choose a plan, confirm Betfair coverage, and request current pre-match prices.