API uptime target
Monthly operating target for production API endpoints. Check current health on the status page.
Pull Neds prices into your AFL, NRL or multi-book odds product with the neds filter, stable event IDs and normalized market fields.
{
"event_id": "afl-bris-carl",
"items": [
{
"bookmaker": "neds",
"bet_type": "moneyline",
"period_str": "full game",
"side": "home",
"selection_name": "Brisbane Lions",
"odds": 1.72
},
{
"bookmaker": "neds",
"bet_type": "total",
"period_str": "full game",
"side": "over",
"selection_name": "Over 171.5",
"odds": 1.91
}
],
"resume": "1784092451749-0"
}
neds bookmaker key.
Find an event that lists Neds, then request a focused snapshot with the canonical neds bookmaker key.
X-API-Keyneds/v1/events/{event_id}/odds/snapshot?bookmakers=neds
const apiKey = process.env.ODDS_API_KEY;
const baseUrl = "https://api.odds-api.net/v1";
const headers = { "X-API-Key": apiKey };
if (!apiKey) throw new Error("Set ODDS_API_KEY before running this file.");
async function getJson(path) {
const response = await fetch(`${baseUrl}${path}`, { headers });
if (!response.ok) throw new Error(await response.text());
return response.json();
}
const events = await getJson("/events?limit=200");
const event = events.items.find(({ bookmakers }) =>
Array.isArray(bookmakers)
? bookmakers.includes("neds")
: Object.hasOwn(bookmakers ?? {}, "neds")
);
if (!event) throw new Error("No current Neds event found.");
const snapshot = await getJson(
`/events/${encodeURIComponent(event.event_id)}/odds/snapshot?bookmakers=neds`
);
console.log(JSON.stringify(snapshot, null, 2));
import os
import requests
base_url = "https://api.odds-api.net/v1"
headers = {"X-API-Key": os.environ["ODDS_API_KEY"]}
events_response = requests.get(
f"{base_url}/events",
headers=headers,
params={"limit": 200},
timeout=20,
)
events_response.raise_for_status()
events = events_response.json()["items"]
event = next(
(item for item in events if "neds" in item.get("bookmakers", [])),
None,
)
if event is None:
raise RuntimeError("No current Neds event found.")
response = requests.get(
f"{base_url}/events/{event['event_id']}/odds/snapshot",
headers=headers,
params={"bookmakers": "neds"},
timeout=20,
)
response.raise_for_status()
print(response.json())
export ODDS_API_KEY="your_api_key"
export EVENT_ID="replace_with_event_id"
curl -sS \
-H "X-API-Key: $ODDS_API_KEY" \
"https://api.odds-api.net/v1/events/$EVENT_ID/odds/snapshot?bookmakers=neds"
Add Neds to the same request and response structure already used across your Australian bookmaker comparison.
Monthly operating target for production API endpoints. Check current health on the status page.
Use a REST snapshot for initial state and supported streams for subsequent pre-match changes.
Winner, line, totals, team totals and player markets share stable fields across bookmakers.
Use bookmakers=neds,ladbrokes,sportsbet,tabtouch to compare local prices without changing your event or market model.
Explore the Australian odds APIMap Neds winner, line, totals, team totals and player markets with the normalized bet_type field.
| Market | API bet_type | What it covers |
|---|---|---|
| Head-to-head |
moneylinemoneyline 3w
|
Two-way and three-way winner prices for full events and covered periods. |
| Line |
handicap
|
Selection prices with the positive or negative line retained as structured data. |
| Match total |
total
|
Over and under outcomes joined to the relevant full-game or period total. |
| Team totals |
team total
|
One-team scoring totals organized by event and covered period. |
| Player props |
player pointsplayer goalsplayer disposals
|
Player performance selections represented with consistent player and market fields. |
Check the event snapshot and coverage catalogue for the Neds markets currently attached to a fixture. Check current Neds coverage.
Tools for events, odds, line movement, streams, and paid-plan positive EV or arbitrage feeds.
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 the event, filter for Neds, add comparison sources, then process supported pre-match changes.
Request GET /v1/events and choose an event that includes neds in its bookmaker coverage.
Call the event snapshot with bookmakers=neds and retain the returned freshness and resume metadata.
Pass neds with ladbrokes, sportsbet or tabtouch and align rows by market, period, line and selection.
Process supported pre-match stream events and use the latest resume token after a disconnect.
Choose a monthly plan based on request volume, rate limits, and support.
Answers about the Neds bookmaker key, Australian comparisons, event coverage, streams, and independence.
No. odds-api is an independent data service. It is not affiliated with, endorsed by, or sponsored by Neds, and it does not place bets or access Neds customer accounts.
Use bookmakers=neds on a covered event snapshot. GET /v1/bookmakers returns the canonical key accepted by the API.
Yes. Pass neds,ladbrokes on endpoints that accept multiple bookmaker filters, then compare the normalized event, market, period, line and selection fields.
Use GET /v1/events to identify AFL and NRL fixtures that currently include Neds, then request the odds snapshot for the selected event.
Start with the REST snapshot, then open the matching SSE or WebSocket route for supported pre-match changes and resume handling.
Create an API key, find a covered event, and request Neds alongside the Australian bookmakers you already compare.