What API customers asked for and what shipped, once a week. Read it here or have it emailed.
One email a week, only when an issue is published. Nothing else goes to this list, and every email carries a one-click unsubscribe.
Issue #1
This was a week driven almost entirely by customer requests. Every section below opens with who asked and what for. Where something is half-done, it says so.
Asked by three customers building modelling and backtesting tools, who needed timestamped price movement rather than a single closing line.
/v1/racing/price-history now serves races that have aged out of the live store from the archive, in the same response shape. You will not notice the switch./v1/racing/price-paths: a bulk export of the archive as CSV or JSON, one row per observed price point, up to a seven-day window per call. Paid plans. Betfair prices are withheld pending a data licence.Asked by a daily picks service that was polling on a schedule to find out when a race had been priced.
race.odds_open fires once per race, the moment the first bookmaker prices land. Subscribe to it and stop polling./v1/racing/next-to-go accepts num_races up to 200, so one call returns the whole priced card./v1/racing/results docs now explain when starting prices appear: every final result carries settled prices, and a null SP means the race is still in the interim window.Asked by two customers maintaining historical runner databases, who needed a finishing position for every starter and an ID that survives name spelling.
runner_ref: a stable registry ID (ra:<horsecode> for horses, grv:<dogId> for greyhounds). Join on it, never on the name.Asked by a customer building a greyhound analysis app, who sent a ten-item list.
/v1/racing/greyhounds/form and /v1/racing/greyhounds/stats (3 credits each). Form history per dog, and track, distance, box and grade statistics, from the official Topaz feed. Form runs include grade_in and grade_out, and a second split time where the track records one./v1/racing/changes: a changed-since feed with a since cursor. Poll it once instead of re-downloading the card. Deliveries are at-least-once, so treat a repeated row as harmless./v1/racing/events now serves scratchings and market status. Box-vacancy placeholders, which used to appear under several spellings and double-count the field, collapse to one canonical Vacant Box entry per box.Asked by a customer building a thoroughbred model app, who needed last-ten-start histories and career splits joined to the odds feed.
/v1/racing/horses/form: last starts, career record, and going splits per horse, from Racing Australia form pages, with stable horse IDs that join straight onto the live feed./v1/racing/jockeys/stats and /v1/racing/trainers/stats (2 credits). Premiership top-20 tables, national and per state, split by metro, provincial, country and picnic, for the current and previous season. The store is still filling. Both endpoints answer 503 until it does. Do not build on them this week.Asked by a customer whose model joins broke on Sandown Hillside versus Lakeside and on Pakenham Synthetic.
venue_id, venue_canonical and venue_site. The raw venue string is unchanged./v1/racing/venues (1 credit), the measured venue directory.track_name on next-to-go and events gives Racing Australia's course name verbatim (Hillside, Lakeside, Main).venue_id and venue_site as trailing columns, so positional CSV readers keep working.Asked by a tipping service that rejected every place quote for lacking a link, and a customer who noticed Sportsbet coverage fall away.
best_place quotes on /v1/racing/best-odds now carry source_url, matching best_win.age_seconds now reports the true age of a pushed price.Asked by a customer who had wrapped the API in an MCP server himself, and suggested a first-party one.
puntersedge-mcp 0.1.0 is on PyPI. Ten read-only tools, credit cost in every tool description, and credits_remaining on every response.pip install puntersedge-mcp
country=NZ./v1/racing/best-odds. books_quoting is one combined number today.Reply with anything you want on the list. Requests from the last week drove nearly everything above. Write to hamish@punters-edge.com or use the feature request form.