Finding a set of colours
Search the name as it appears in a racecard.
Documentation / Jockeys & owners
/v1/owners/search
By name. Owners are identified by name; the source publishes no id.
Send your key in the X-API-Key header, or as
?key= if your tool cannot set one. A date outside your plan's window returns
403 outside_window naming the window, never an empty array.
| Name | In | Type | Required | Description |
|---|---|---|---|---|
| q | query | string | yes | At least two characters, matched against the name as published. |
| limit | query | integer | no | 1 to 100. Defaults to 25. |
| cursor | query | string | no | Opaque. Pass next_cursor from the previous response. |
curl https://api.apihorseracing.com/v1/owners/search \ -H "X-API-Key: $AHR_KEY"
$ch = curl_init('https://api.apihorseracing.com/v1/owners/search'); curl_setopt_array($ch, [ CURLOPT_RETURNTRANSFER => true, CURLOPT_HTTPHEADER => ['X-API-Key: ' . getenv('AHR_KEY')], ]); $data = json_decode(curl_exec($ch), true)['data'];
const res = await fetch( 'https://api.apihorseracing.com/v1/owners/search', { headers: { 'X-API-Key': process.env.AHR_KEY } } ); const { meta, data } = await res.json();
import os, requests r = requests.get( "https://api.apihorseracing.com/v1/owners/search", headers={"X-API-Key": os.environ["AHR_KEY"]}, ).json()
curl https://api.apihorseracing.com/v1/owners/search?key=$AHR_KEY
$url = 'https://api.apihorseracing.com/v1/owners/search' . '?key=$AHR_KEY'; $data = json_decode(file_get_contents($url), true)['data'];
const res = await fetch( 'https://api.apihorseracing.com/v1/owners/search?key=$AHR_KEY' ); const { meta, data } = await res.json();
import os, requests r = requests.get( "https://api.apihorseracing.com/v1/owners/search?key=$AHR_KEY", ).json()
{ "meta": { "request_id": "bc7add9caa52ba54", "data_as_of": "2026-09-12T05:10:27+00:00", "plan": "analyst", "window": "2017 → upcoming", "query": "Racing", "count": 25 }, "data": [ { "owner_id": "ow_2BANWEB", "name": "Al Shaqab Racing", "runs": 3366, "wins": 514 }, { "owner_id": "ow_3NF3KQC", "name": "King Power Racing Co Ltd", "runs": 2963, "wins": 376 }, "… 23 more" ] }
A real response from /v1/owners/search?name=Racing,
captured by calling the live API rather than written by hand.
Each field is described once and rendered on every endpoint that returns it, so the wording cannot drift between pages.
| Field | Type | What it is |
|---|---|---|
| owner_id | string | Opaque owner identifier, derived from the name because the source publishes none. Two owners sharing a name are one owner here. |
| name | string | Race title as published, sponsor and all. |
| runs | integer | Rides in the slice, priced or not. |
| Code | Status | When |
|---|---|---|
| unauthorized | 401 | No key, or one we do not recognise. Check the header name and that the key has not been rotated from your account page. |
| invalid_param | 422 | A date that is not YYYY-MM-DD, a by= dimension we do not have, or a cursor that did not come from us. The message names the parameter. |
| rate_limited | 429 | Past your per-minute rate. Retry-After is set, and X-RateLimit-Remaining tells you where you stand on every successful response too. |
| server_error | 500 | Ours, not yours. Every response carries a request_id; quote it and we can find the exact request. |
A real request from your browser straight to
api.apihorseracing.com with
your own key. Nothing is proxied and nothing is logged by this page.
Remembered in this browser so you do not paste it on every page. Forget it
Owners by name, with runners, wins and the span of the record.
Owners are the one entity in this API with no source identifier at all. The source publishes a name and nothing else, so the identifier you get back is derived from that name. It is stable, it round-trips, and it is exactly as reliable as the name itself.
That has consequences worth stating plainly. A syndicate written two ways is two owners. "Mrs J Smith" and "Mrs Jane Smith" are two owners. A partnership that adds a member becomes a new owner. We do not merge any of those, because merging on a name similarity produces confident, wrong answers and there is no identifier to check them against.
Search the name as it appears in a racecard.
If the same owner appears twice under variant spellings, your analysis needs to combine them and only you can decide that they are the same.
Not every runner carries an owner. Where the source published none, the runner is absent from owner endpoints entirely rather than bucketed as unknown.