The Tracksuit API endpoint reference

The complete, always-current reference for every Tracksuit Public API endpoint lives in our interactive API documentation. It's generated directly from the API's OpenAPI spec, so the parameters, response fields and error codes you see there never drift out of date — and you can run real requests against your own data straight from the page.

This guide explains how to get the most out of it.

👉 New to the API? Start with the Quick-start guide first, then come back here.

👉 Open the interactive API documentation. Try any endpoint live, generate code snippets, and download the OpenAPI spec.

What the interactive docs give you

A live "try it" console. Add your API key once and run real GET requests against your own data, without writing any code or leaving the browser.
Ready-to-use code snippets. Every request generates copy-paste code (curl, Python, JavaScript and others) with your parameters already filled in.
Complete, current schemas. Every parameter (required and optional), response field and error code, straight from the OpenAPI spec. If anything on this page and the interactive docs ever disagree, the docs are the source of truth.
The downloadable OpenAPI spec. Import it into Postman, Insomnia or a client generator to scaffold your integration.

Always check the server first. The docs include a server selector so make sure it's set to https://api.gotracksuit.com/v2.

How to get the most out of them

Add your key once. Open the authentication panel and enter your token as Bearer YOUR_API_KEY. The key stays in your browser. See How to authenticate the Tracksuit API for where to find it.
Check the server. Make sure the selector is set to https://api.gotracksuit.com, as flagged in the note above.
Run List category views first. It returns the id for each brand/category/geography your key can access. Every other endpoint needs that id, so this is always your first call.
Fill in the parameters, then send. The panel marks required vs optional fields with inline hints. Remember start_period / end_period must be first-of-month ISO dates. Send the request to see the real response.
Read the live JSON. Inspecting a real response is the fastest way to learn the exact field names, the percentage values and the reliability indicators before you write any code.
Copy the generated snippet. Switch to your language in the code pane and paste the request straight into your project.

How to filter by demographics and How to handle pagination each have their own guide — try the parameters live in the docs while you read them.

What you'll find in there

Every endpoint sits under the Category Views tag and is a GET request:

List category views: The category views your key can access (start here).
Get metadata: The dimensions, metrics, brands and channels available for a category view.
Get funnel: Awareness, consideration, preference and usage over time.
Get conversion: Conversion rates between funnel stages.
Get statements: Brand imagery and attribute associations.
Get media consumption: The channels your category's audience consumes content on.
Get profile: The demographic make-up behind a chosen metric.

A few conventions to keep in mind

Base URL: https://api.gotracksuit.com/v2 and every endpoint sits under /category-views.
Dates (start_period, end_period) are ISO 8601 and must be the first day of a month. They map to survey wave dates, which are always the 1st.
Percentages are returned as a value between 0 and 1 (0.42 = 42%).
Statistical significance is available across the API, using the same testing as the dashboard.
Pagination is cursor-based via next_token . See How to handle pagination.
Don't sum demographic slices. Weighting is applied dynamically per slice, so individual age groups won't add up to the total. Pull the total with no filter, or pull a single slice on its own. See Why your API numbers may differ from the dashboard.
Reliability indicators (Insufficient / Directional / Reliable) accompany each data point; the raw sample size (n=) is not exposed. See the data dictionary.