Neds APIneds.com.au ↗
Access Neds.com.au racing data via API: next-to-jump races, daily meetings, race details, and official results for thoroughbred, harness, and greyhound racing.
What is the Neds API?
This API exposes 4 endpoints covering Neds.com.au racing data across three codes — thoroughbred, harness, and greyhound. Use get_next_to_jump_races to retrieve upcoming race summaries ordered by start time, or get_racing_events to pull all meetings and event schedules for the current day. Response fields include race IDs, advertised start times, venue details, distance, market IDs, and official results for completed races.
curl -X GET 'https://api.parse.bot/scraper/6a5dfa2c-4d36-46b5-bfcf-3eb558434309/get_next_to_jump_races?limit=5' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace neds-com-au-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Neds Racing API — browse upcoming races and today's meetings."""
from parse_apis.neds_racing_api import Neds, RacingCode, InvalidInput
client = Neds()
# Fetch the next races about to jump across all codes (horse, harness, greyhound).
for race in client.races.next_to_jump(limit=5):
print(race.race_name, race.venue_name, race.track_condition, race.distance)
# List today's thoroughbred meetings and inspect their scheduled events.
meeting = client.meetings.list(sport_ids=RacingCode.THOROUGHBRED, limit=1).first()
if meeting:
print(meeting.name, meeting.advertised_date, len(meeting.race_ids), "races")
for event in meeting.events.list(limit=3):
print(event.name, event.number, event.advertised_start)
# Typed error handling around a call that could fail on bad input.
try:
for race in client.races.next_to_jump(limit=3):
print(race.race_id, race.meeting_name, race.advertised_start)
except InvalidInput as exc:
print(f"Invalid input: {exc}")
print("exercised: races.next_to_jump / meetings.list / meeting.events.list")
Fetches the next races about to start across all racing codes (horse racing, harness, greyhounds). Returns race summaries ordered by start time, including form data, track conditions, and race comments.
| Param | Type | Description |
|---|---|---|
| limit | integer | Number of upcoming races to fetch. |
{
"type": "object",
"fields": {
"races": "array of race summary objects containing race_id, race_name, race_number, meeting_name, advertised_start, venue details, distance, track_condition, weather, and race_comment",
"total": "integer count of races returned"
},
"sample": {
"data": {
"races": [
{
"class": "Maiden Heat",
"race_id": "17c9fe8f-e626-4b0f-b7cc-d39a993b06da",
"weather": "OCAST",
"distance": 350,
"race_name": "Sportsbet Ht2",
"meeting_id": "17056ba0-3d4e-5c9d-b10e-bbee9ea35e48",
"start_type": "",
"venue_name": "Traralgon",
"category_id": "9daef0d7-bf3c-4f50-921d-8e818c60fe61",
"race_number": 2,
"venue_state": "VIC",
"meeting_name": "Traralgon",
"race_comment": "DAINTREE GAV (6) ran a sound debut...",
"distance_unit": "m",
"venue_country": "AUS",
"track_condition": "Good",
"advertised_start": "2026-06-12T09:24:00Z"
}
],
"total": 5
},
"status": "success"
}
}About the Neds API
Race Discovery and Scheduling
The get_next_to_jump_races endpoint returns an ordered list of races about to start across all codes. Each race object in the races array includes race_id, race_name, race_number, meeting_name, advertised_start, venue details, distance, form data, track conditions, and race comments. The limit parameter controls how many upcoming races are returned. The total field indicates the count of races in the response.
The get_racing_events endpoint retrieves all meetings and individual race events scheduled for the current day. Filter by code using the sport_ids parameter: 1 for thoroughbred, 2 for harness, 3 for greyhound. The meetings array includes id, name, advertised_date, category_id, venue_id, and race_ids. The events array includes id, meeting_id, name, number, advertised_start, actual_start, and market_ids.
Race Detail and Results
get_race_detail accepts a required event_id and returns an event object alongside a markets array for that specific race. This is the endpoint to use when building a race card view or displaying runner and market information for a single event.
get_race_results also takes an event_id and returns a results array for completed races. Use this to display finishing positions and official outcomes once a race has been run. Both detail endpoints are designed to be called after obtaining an event_id from get_next_to_jump_races or get_racing_events.
The Neds API is a managed, monitored endpoint for neds.com.au — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when neds.com.au changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official neds.com.au API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Display a live next-to-jump widget showing upcoming races with track conditions and race comments
- Build a daily race calendar filtered by code (thoroughbred, harness, or greyhound) using get_racing_events
- Retrieve market IDs from event objects to map races to betting markets in a custom interface
- Show official finishing results for completed races using get_race_results and a stored event_id
- Aggregate advertised start times across meetings to power race schedule notifications
- Pull venue and distance data from get_next_to_jump_races to enrich a form guide application
| 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 | 100 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 Neds have an official public developer API?+
What does get_racing_events return and how do I filter by racing code?+
meetings (with venue, date, category, and associated race IDs) and events (with scheduling fields including advertised_start, actual_start, and market_ids). Pass a value to the sport_ids parameter to filter: 1 for thoroughbred horse racing, 2 for harness, and 3 for greyhound.Does the API cover historical race data beyond the current day?+
get_racing_events endpoint covers the current day's meetings and events. get_race_results returns results for a completed race when you supply an event_id, but there is no dedicated historical results or past-meeting listing endpoint. You can fork this API on Parse and revise it to add a historical endpoint if your use case requires multi-day lookups.Does the API expose individual runner or jockey/trainer data?+
get_race_detail returns a markets array and an event object that may carry deeper race card data. You can fork this API on Parse and revise it to expose individual runner fields if that level of detail is required.How do I get the event_id needed for get_race_detail and get_race_results?+
get_race_detail and get_race_results require an event_id. You can obtain event IDs from the races array returned by get_next_to_jump_races (via race_id) or from the events array returned by get_racing_events (via the id field).