Results

Result Freshness

Market Coverage

Results cover every meeting Race Form covers, across gallops, harness and greyhounds. How a result is sourced varies by market, and so does what it carries:

• Where the batch pipeline holds the race, positions arrive with margin and, where published, the official startingPrice.
• Elsewhere the result comes from bookmaker results feeds, which report placings but not margins, so those results carry no margin. Premium sees them as races settle; Pro receives the confirmed (correct_weight) result once a race is two hours past its start with no batch result.

Coverage deepens as sources are added. Treat margin and startingPrice as optional on every runner.

Parameters

Two Endpoints

Code Examples

// Single race
const response = await fetch(
  'https://api.formfav.com/v1/results?' +
  new URLSearchParams({
    date: '2026-07-25',
    track: 'caulfield',
    race: '1'
  }),
  {
    headers: { 'X-API-Key': 'your_api_key_here' }
  }
);

const race = await response.json();

if (race.resultStatus === 'final') {
  race.placings
    .filter(p => p.position != null)
    .forEach(p => console.log(`${p.position}. ${p.name} (${p.margin})`));
}

Result Status

The race-level resultStatus field tells you how complete a race's result is:

Result Stages

On Premium and Enterprise, a finishing position can reach you from the real-time feed before the batch pipeline has the race at all. When it does, that runner carries resultStage saying how settled the position is. It is a per-runner field — placings[].resultStage, not a race-level one.

Two consequences of it being a fill-in rather than an override:

• •A runner the batch pipeline has already resulted never carries a stage, and neither does a scratching. Where the two sources both have a position the batch one wins — it comes from the controlling body rather than a bookmaker feed.
• •A position filled in this way carries no margin. The feed reports the finishing order, not margins; the margin arrives later with the batch result.

Abridged, showing a race the feed has called but the batch pipeline has not yet ingested. The placed runners carry a stage and no margin; the scratching carries neither:

{
  "raceNumber": 4,
  "resultStatus": "final",
  "placings": [
    {
      "number": 6,
      "name": "Torrent Bay",
      "position": 1,
      "scratched": false,
      "resultStage": "correct_weight"
    },
    {
      "number": 2,
      "name": "Second Reading",
      "position": 2,
      "scratched": false,
      "resultStage": "correct_weight"
    },
    {
      "number": 9,
      "name": "Withdrawn Early",
      "scratched": true
    }
  ]
}

Although the field sits on each runner, the stage is decided once per race — a feed calls a whole race interim or correct-weight, not individual placings. So every live-filled runner in a race carries the same value, and it is safe to read one runner's stage as the race's. Do not build logic that expects the two to differ within a race.

Where several feeds report the same race, a stewards-confirmed result is preferred over a provisional one, then the most recent. A feed that disagrees with the others is excluded outright rather than ranked below them, on the grounds that a known-wrong result is worse than none.

Pro keys never see interim. Their positions come from the batch pipeline or, where it has no result two hours after the start, from the confirmed live result — which carries resultStage correct_weight until a batch position replaces it.

Corrected and withdrawn results

A result can change after it first appears: stewards amend the order, a margin arrives after the placings, or an abandonment clears results that were already recorded. Three race-level fields let you tell which copy of a race is the latest and whether its placings were ever altered.

A race whose result was withdrawn (for example by an abandonment) still reports the time of the withdrawal, with resultRevised: true and no positions. Corrections show on the next request; a settled result is cached for a few minutes only once it has been unchanged for ten.

Reading a placing

Two fields tell you everything about a runner: position and scratched. There is no outcome field — see the note below if you were using one.

Response Fields

The /results/meeting variant wraps a list of these race objects: date, track, slug, country, raceType, abandoned, and a races array.

Example Response

{
  "date": "2026-07-25",
  "track": "Caulfield",
  "raceNumber": 1,
  "raceName": "Le Pine Funerals Handicap",
  "distance": "1200m",
  "condition": "Good 4",
  "weather": "Fine",
  "raceClass": "BM70",
  "abandoned": false,
  "startTime": "2026-07-25T02:30:00Z",
  "timezone": "Australia/Melbourne",
  "prizeMoney": "130000",
  "numberOfRunners": 10,
  "resultStatus": "final",
  "placings": [
    {
      "number": 3,
      "name": "Custom",
      "jockey": "J. McDonald",
      "trainer": "C. Waller",
      "weight": 58.5,
      "barrier": 4,
      "position": 1,
      "margin": "0.0",
      "scratched": false,
      "startingPrice": 3.4
    },
    {
      "number": 7,
      "name": "Sun Setting",
      "jockey": "M. Dee",
      "trainer": "G. Waterhouse",
      "weight": 56.0,
      "barrier": 2,
      "position": 2,
      "margin": "3.0",
      "scratched": false
    },
    {
      "number": 9,
      "name": "Late Withdrawal",
      "trainer": "P. Moody",
      "barrier": 8,
      "scratched": true
    }
  ]
}

Related

• •Race Form endpoint — runners, form and ratings going into a race (same parameters)
• •Meetings endpoint — discover which tracks ran on a date
• •Errors — how 400 / 403 / 404 responses are shaped