Postman collection

The whole API as a Postman collection, at /postman-collection.json. Import it, set one variable, and every request is ready to send.

Generated from the same registry as the documentation and the OpenAPI spec, so all three describe the same surface and cannot drift apart.

Getting started

1. In Postman: Import, then paste https://apihorseracing.com/postman-collection.json.
2. Open the collection's Variables tab and set apiKey to your key.
3. Send anything.

The key is wired as collection-level authentication, so it applies to every request without being pasted into each one. baseUrl is already set to production.

How it is organised

One folder per section, matching the documentation. Every request carries its own description, its parameters with explanations, and a saved example response taken from the live API, so you can see the shape before you send anything.

Required parameters ship enabled with the example URL filled in. Optional ones are present but unticked, so you can see what exists without sending a blank value, which is a different request from leaving the parameter off.

What the labels mean

Requests that need the Complete + Analyst plan are prefixed [Analyst] in the name. Everything else works on any paid plan, and most of it works on a free key inside its delayed window.

They are labelled in text rather than with an icon on purpose: a label nobody can search for in a diff or quote in a support thread is a poor label.

It also works elsewhere

The file is standard collection format v2.1, so Insomnia and Bruno both import it. If your tool prefers a spec, use the OpenAPI file instead.