Search or download

This page opens any card from its code: a horse, a race, a clan or a member. It also gives you access to the exports and to the API, in order to get the game's data into a spreadsheet, a script or an AI.

Opening a card by its code

Each card displays its code. Enter it in the matching card, then click Search: the name appears, and Show the card opens it.

To show a card to another player, use the card's Share button: it copies a link that brings you back here, with the card already open.

The search is done in the world you are playing on. Clans and members, for their part, are common to all three worlds.

Exporting a card

The exports and the API are reserved for subscribers and competition managers. If you are not a subscriber, the page offers you the chance to become one in place of these buttons.

Once the card is found, the Export button opens its raw data. Just underneath, its address can be copied to be reused outside the game. It is only displayed once your API key has been created: without a key, it would only work in your browser.

A horse not yet born or gone into retirement is not exported.

The two keys

To use an address somewhere other than in the game (a spreadsheet, a script, an AI), you need a key. You have two, and they do not have the same role:

The API key opens the public data: the cards of horses, races, members, clans. It also counts your calls for the month. It stays visible on this page.
The private key opens your whole stable, genetics and folders included: what you alone see. It is displayed only once, when it is created: copy it straight away and keep it somewhere safe.

Only give your private key to a tool you trust: whoever holds it sees your whole stable. A key that is lost or disclosed can be regenerated: the old one stops working at once, including in the tools where you had already used it.

In co-management, the keys cannot be managed, so that a co-manager cannot take them away. Exception: on a competition manager's account, the co-manager can create and regenerate the API key. The private key, never.

The number of calls

Each address opened with your key counts as one call. Your subscription gives you a certain number per month, displayed under your key with what you have already used. The counter goes back to zero on the 1st of the month.

The Export buttons on this page do not count: they go through your game session.

A list in CSV format arrives whole in a single call, whereas in JSON it is read in pages of a hundred: for a long list, CSV is far more economical.

Exporting my stable, exporting my races

The My API access card offers two ready-made exports, each in two formats:

JSON, for a script or an AI;
CSV, for a spreadsheet: it opens as it is in Excel or LibreOffice.

Export fetches the file straight away. Copy copies the address, to do the export again later without going through the game.

My stable: all your horses, foals still to be born included, with their genetics and your folders. Its address asks for the private key. As that key is no longer displayed after its creation, the address carries YOUR_PRIVATE_KEY in its place: replace it with your key.
My races: the races you have organised. It is, for example, the export used by competition managers, to draw up their rankings.

In a CSV file, the last column gives the address of each row: the detail of a race with its runners and its finish, or a horse's card.

With an AI

An AI (ChatGPT, Claude, Gemini…) can read this data and answer your questions: taking stock of your stable, retracing a horse's career, following a line, calculating the ranking of a competition…

Click on Copy the text for my AI. It contains everything the AI needs: where to read the API's help, your world, your member code, your key and your addresses.
Paste it into a conversation with your AI.
Write your question after “My question:”.

If your AI cannot open a web address (some free versions), also paste the full help: the button of the same name copies it. It is in English, the language AIs read best. The AI will answer you in your own language.

If you want it to read your stable, replace YOUR_PRIVATE_KEY with your private key in the text before sending it. Remember that it gives access to your whole stable.

A few examples of questions:

“Give me a summary of my stable: how many horses by age, by sex and by speciality.”
“Which are my five horses that have won the most, and how old are they?”
“For each of my stallions, compare his birth genetics with those of his foals.”
“Retrace the career of horse 1182267 and give me its best results.”

An AI can be wrong: check what matters before taking a decision.

For competition managers

Even without a subscription, a competition manager has access to the exports and to the API, with their own number of calls.

To draw up a ranking, give your AI the copied text, your competition's rules (the points per place, the categories, the limits per owner) and the period you want. It finds your races, reads the finishes and does the totals.

It cannot know what you alone have decided: a multiple account, a cancelled race, a penalty. Tell it.

A few useful points to know:

the owner taken into account is the one at the moment of entry: a horse sold since then is still counted for its former owner;
players rename their horses: the AI must follow them by their code, not by their name;
deleted races appear in the list, with their state: they do not count;
a race remains readable for 60 days. Draw up your rankings as the month goes by, without waiting too long.

What the API does not give

the genetics of other players' horses;
other players' folders, notepads, contracts and accounts;
horses gone into retirement, whose card can no longer be read. They are still named, however, in race finishes and as parents.

For developers, the API's technical documentation (in English) is at the address /api/v1/help. The See the help button opens it.