Get ready-made pre-match value bets with bookmaker prices, estimated fair odds and calculated edge. REST and streaming included. From $50/month.
/v1/bets/snapshot?strategies=pos_ev&price_fields=odds,fair&limit=1{
"items": [
{
"id": "example-positive-ev",
"strategy": "pos_ev",
"event_id": "3704597661",
"bookmaker_name": "Bet365",
"selection_key": "moneyline:home",
"odds": 2.18,
"fair_odds": 2.02,
"ev": 7.9
}
],
"resume": "{\"pos_ev\":\"1792886400000-0\"}"
}A value bet offers a higher price than its estimated fair odds. We compare the prices and deliver the selection with its calculated expected value.
Illustrative example
| Price source | Selection | Odds |
|---|---|---|
 | Home to win | 2.18 |
| Estimated fair price | Home to win | 2.02 |
Copy a request or give the prompt to your AI agent.
X-API-Keypos_ev/v1/bets/snapshot?strategies=pos_ev&price_fields=odds,fair
Build a positive EV alert board using https://api.odds-api.net/v1. Keep ODDS_API_KEY server-side and send it in the X-API-Key header.
Load /bets/snapshot?strategies=pos_ev&price_fields=odds,fair&limit=50. Display the bookmaker, selection, offered odds, fair_odds and ev for each opportunity. Treat fair_odds as optional and handle an empty items array.
Retain resume and pass it as since to /bets/stream?strategies=pos_ev&price_fields=odds,fair. Apply upsert and delete events by ID so expired opportunities leave the board. Your application can filter the returned ev values before sending alerts.const apiKey = process.env.ODDS_API_KEY;
if (!apiKey) throw new Error("Set ODDS_API_KEY first.");
const response = await fetch(
"https://api.odds-api.net/v1/bets/snapshot?strategies=pos_ev&price_fields=odds,fair&limit=50",
{ headers: { "X-API-Key": apiKey } }
);
if (!response.ok) throw new Error(await response.text());
const { items, resume } = await response.json();
console.log(items);
// Retain resume for the matching bet stream.import os
import requests
response = requests.get(
"https://api.odds-api.net/v1/bets/snapshot",
headers={"X-API-Key": os.environ["ODDS_API_KEY"]},
params={"strategies": "pos_ev", "price_fields": "odds,fair", "limit": 50},
# Include fair-price fields for compact API responses.
timeout=20,
)
response.raise_for_status()
data = response.json()
print(data["items"])
# Retain data["resume"] for the matching bet stream.curl --fail-with-body --get \
'https://api.odds-api.net/v1/bets/snapshot' \
--header "X-API-Key: $ODDS_API_KEY" \
--data-urlencode 'strategies=pos_ev' \
--data-urlencode 'price_fields=odds,fair' \
--data-urlencode 'limit=50'Paid plans include positive EV feeds. Your bet-feed bookmaker limit is separate from odds-catalog access.
Enterprise grade
Custom projects, scoped with your team.
Yes. The feed returns prepared positive expected value opportunities with the bookmaker, selection, offered odds and calculated EV. Request price_fields=odds,fair to include stored fair odds in the response.
It expresses estimated expected profit as a percentage of the stake. With decimal odds of 2.18 and estimated fair odds of 2.02, the calculation is (2.18 / 2.02 - 1) x 100, or about +7.9%.
Select your bet bookmakers in your account. Your plan sets the limit, separately from general odds-catalog access.
Yes. Load a snapshot with strategies=pos_ev, retain its resume token, then connect to the matching SSE or WebSocket stream. Apply upserts and deletions to keep your value-bet board current.
Yes. Paid plans include prepared positive EV and arbitrage feeds, within their bookmaker and usage limits.
Positive EV identifies a selection priced above its estimated fair odds. Arbitrage combines opposing outcomes across bookmakers. This feed returns the individual value-bet selection and its estimated edge.