oddspedia.com APIoddspedia.com ↗
Access Oddspedia data via API: sure bets, value bets, dropping odds, match info, and odds comparison across dozens of bookmakers and multiple sports.
curl -X GET 'https://api.parse.bot/scraper/a6aad0cf-30f9-40ae-81b9-d90b84c0e01f/get_surebets?sports=1&geo_code=US' \ -H 'X-API-Key: $PARSE_API_KEY'
Extract arbitrage betting opportunities with details on match, sport, league, and bookmaker odds for each outcome. Returns sure bets sorted by profit percentage.
| Param | Type | Description |
|---|---|---|
| sports | string | Comma-separated sport IDs to filter by (e.g. '1' for Football, '2' for Ice Hockey, '3' for Basketball). Omitting returns all sports. |
| geo_code | string | Two-letter country code for geo-targeted odds (e.g. 'US', 'GB'). Omitting returns global odds. |
| language | string | Language code for response content. |
| bookmakers | string | Comma-separated bookmaker IDs to filter by. Omitting returns all bookmakers. |
| profit_range | string | Min,max profit percentage range as two comma-separated decimal values. |
{
"type": "object",
"fields": {
"data": "array of surebet opportunities with match, odds, and payout details",
"sports": "array of available sports with event counts",
"markets": "array of market types with counts",
"bookmakers": "array of bookmaker references",
"generated_at": "string timestamp of response generation"
},
"sample": {
"data": {
"data": [
{
"at": "Maaseik",
"ht": "Roeselare",
"id": 10061633,
"md": "2026-05-08 18:30:00+00",
"odds": [
{
"type": "Home",
"values": [
{
"odd": "1.81",
"bookie_name": "1xBet"
}
]
},
{
"type": "Away",
"values": [
{
"odd": "6.5",
"bookie_name": "BetVictor"
}
]
}
],
"payout": 141.58,
"match_key": 583540,
"sport_name": "Volleyball"
}
],
"sports": [
{
"id": 1,
"name": "Football",
"slug": "football",
"count": 10
}
],
"markets": [
{
"id": 3,
"count": 8
}
],
"bookmakers": [
{
"id": 170,
"name": "Stake.com",
"slug": "stake-com"
}
],
"generated_at": "2026-05-07 19:38:14"
},
"status": "success"
}
}About the oddspedia.com API
The Oddspedia API exposes 10 endpoints covering arbitrage opportunities, value bets, odds movements, and match metadata across sports including football, basketball, tennis, and ice hockey. The get_surebets endpoint returns live arbitrage opportunities sorted by profit percentage, while get_value_bets surfaces mathematically overpriced odds, and get_odds_comparison delivers a full bookmaker-by-bookmaker breakdown for any specific match and market.
Arbitrage and Value Bet Data
The get_surebets endpoint returns an array of current arbitrage opportunities, each containing match identifiers, sport and league context, per-bookmaker odds for each outcome, and a calculated profit percentage. You can filter by comma-separated sport IDs (e.g. '1' for Football), a geo_code for region-specific odds, and a profit_range to target a specific margin band. The get_value_bets endpoint follows the same structure but focuses on bets where offered odds exceed calculated fair probability, with an overvalue_range filter and odds_min/odds_max bounds.
Odds Movement and Trending Bets
The get_dropping_odds endpoint tracks matches where odds have declined significantly within a chosen period, returning current and previous odds alongside bookmaker details. Pagination is supported via page, and drop_range lets you target specific movement thresholds. The get_hot_bets POST endpoint surfaces statistically trending bets based on team form and historical hit rates, returning full league and category structures, a total_success_rate, and per-bet bookmaker references. A min_percent integer (51–100) constrains results to bets meeting a combined success threshold.
Match and League Context
The get_match_info endpoint accepts a match_key from any listing endpoint and returns venue, team form, scores, season, weather, and league metadata for that fixture. The get_odds_comparison endpoint takes the same match_key plus an optional market_group_id (Moneyline, Spread, or Total) and returns the full odds grid keyed by period and bookmaker. Upstream match keys are shared across get_surebets, get_dropping_odds, get_value_bets, and get_hot_bets, so results can be cross-referenced directly.
Reference and Listing Endpoints
The get_sports_list endpoint returns all tracked sports with their IDs, slugs, and current sure-bet event counts — useful for populating sport filter values. The get_leagues_by_sport endpoint lists competitions per sport with match counts and an optional top_only flag. The get_bookmakers_list endpoint returns bookmaker IDs, names, slugs, numeric ratings, user ratings, and brand colors, optionally filtered by geo_code. The get_matches_by_sport endpoint lists upcoming and live matches for a sport on a single calendar day, returning max odds and bookmaker details keyed by match ID.
- Build an arbitrage alert system using
get_surebetsfiltered byprofit_rangeand bookmaker IDs. - Track odds drift over time by polling
get_dropping_oddsfor specific sports anddrop_rangethresholds. - Populate a value-bet dashboard using
get_value_betswithovervalue_rangeandodds_min/odds_maxbounds. - Enrich betting data with venue, team form, and weather by calling
get_match_infofor eachmatch_key. - Compare full bookmaker grids for a given match using
get_odds_comparisonwith Moneyline, Spread, or Total market groups. - Filter available bookmakers by region with
get_bookmakers_listusing ageo_codefor market-specific coverage. - List today's fixtures for a sport and their current max odds using
get_matches_by_sportwith astart_date/end_datewindow.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Oddspedia have an official developer API?+
What does `get_surebets` return, and can I filter it by region?+
geo_code (two-letter country code) to receive region-specific odds, by sports to limit to certain sport IDs, and by bookmakers to restrict which bookmakers appear. A profit_range parameter accepts min and max decimal values.Does the API cover historical odds data or only current opportunities?+
get_dropping_odds tracks movements over up to one day (period: '1day'), and get_matches_by_sport is limited to a single calendar day per request. Historical odds archives are not currently exposed. You can fork this API on Parse and revise it to add historical data endpoints if that coverage is available on Oddspedia.Can I retrieve odds for in-play or live matches specifically?+
get_matches_by_sport returns both upcoming and live matches for the current day, and the odds data includes bookmaker details. There is no dedicated in-play-only filter parameter across the listing endpoints. You can fork this API on Parse and revise it to add an in-play filter endpoint.How do `match_key` values work across endpoints?+
match_key is a unique match identifier returned in the data arrays of get_surebets, get_dropping_odds, get_value_bets, and get_hot_bets. The same key is accepted by both get_match_info and get_odds_comparison, so you can chain any listing endpoint with detailed match or odds data without a separate lookup step.