A read-only REST API. It gives your own systems direct access to the data in your Traackr account: campaigns, creators, posts, performance metrics and spend. You send a request with your API key and receive JSON.

Typical uses are campaign dashboards in a BI tool, spend reconciliation with finance systems, and compliance checks across markets.

Yes. The API launched on 23 September 2026 and supports production integrations. Releases are normally deployed without downtime.

The API is available to customers on mid-tier and enterprise-tier subscriptions. Your Client Partner can confirm what your subscription includes.

What do we need to get started?

The API's machine-readable specification (OpenAPI) needs no key. You can import it into API tools such as Postman, or give it to an AI coding assistant to write the first version of your integration.

See Getting started with the Traackr API for your first calls.

Yes. The API reference gives the name, type and description of every field, and the specification carries the same information in a machine-readable form.

Ask your Traackr Client Partner.Tell us:

There is no self-service key generation.

Through a secure link that works once. The link shows the key one time, then stops working. The link also expires, so open it as soon as you receive it.

Only the person who will store the key should open the link. If someone else opened it first, or the link expired, ask for a new one.

No. A key does not expire and needs no periodic renewal. Traackr replaces a key only if it may have been exposed: contact support@traackr.com.

No. Traackr issues one key per project, and that key serves both testing and production. The API is read-only, so a test call cannot change anything in your account.

Exactly one Traackr account, and all of it: every campaign, brand and market, spend included. A key belongs to the account, not to a person.

Your campaigns, spend and account data (tags, review status) are never visible to another account, and a key never sees another account's campaigns. Creator profiles are the exception: they are public profiles, so a key can read any creator's profile from its Traackr ID.

No. Anyone who holds the key can read the whole account. To work on part of the account, use the filters on the campaign list, for example by country, brand or category.

No, each account needs its own key. The endpoints and data formats are the same for every account, so one integration can serve all your keys. You combine the accounts in your own systems.

We recommend one key per project, even when several projects read the same account. Separate keys let Traackr see which project consumes what, and help you if one project uses too much. A shared key also has a cost: if Traackr must replace it, every team that uses it loses access at the same time.

Agree inside your company who holds which key.

Yes, with its own key. Your company requests the key for that purpose, and names the partner and the account. Traackr may confirm the request with the owner of your Traackr account before it issues the key. The partner MUST NOT use a key that was issued to someone else.

A partner that works with several Traackr customers uses a separate key for each customer. If you are a technology partner and want to build an integration for many Traackr customers, contact us to discuss it.

If the key may have been exposed, contact support@traackr.com immediately. Traackr replaces it.

Not today. Each request sends the API key in the X-Api-Key header. OAuth 2.0 support is on the roadmap.

No. The API is a public HTTPS endpoint, and access is controlled by the key. If your network restricts outbound traffic, allow the host name api.traackr.ai on port 443. Do not allow fixed IP addresses: they change over time.

Your agreement with Traackr sets the terms for storing the data and for using it with AI tools. Your Client Partner can answer contract questions and security questionnaires.

Some of the data is personal data about creators: names, handles, the fees you paid them, notes and tags. Handle it under your own data protection policies, as you do in the Traackr app.

The API is not covered by an uptime commitment or service credits. Releases are normally deployed without downtime, and scheduled maintenance is announced in advance.

The campaign area of Traackr, plus creator profiles:

The API reference lists every endpoint and field.

Not yet. The main areas not covered today are:

See What the API does not cover yet for the full list, and how to tell us that a gap blocks you.

Yes. The Traackr app is the source of truth, and the API returns the same data, at most a few hours later. Campaign and creator totals use the app's own calculations. One exception: the totals shown on the campaign list can be up to a day behind. When you need the app's current figure, use the campaign metrics endpoint.

The API does not add any segmentation of its own. If you need a breakdown that does not exist in your account (a sub-brand, for example), it has to be set up in Traackr first.

When a figure differs from a screen in the app, the usual reasons are timing, currency (each campaign keeps its own currency) or a missing value treated as zero. See Getting started and Spend Data.

The API returns the same history as the Traackr app.

No. The API returns the current state only. A post's metrics are the latest values Traackr measured, not the values on a past date.

If you need history (how a campaign's figures evolved, or what was reported in March), store what you fetch, with the date you fetched it. Post metrics over time are on the roadmap.

Partly. You can read any creator's profile when you have their Traackr creator ID, and you can export creator IDs from the Traackr app. The API does not search for creators, and it returns posts only through campaigns.

Yes. Early access to the Benchmark API opens in mid-November 2026. Ask your Traackr contact if you want to take part.

No. The API is read-only: you cannot create a campaign, add a creator or change a tag through it. Write access is on the roadmap, with no date yet.

Importing historical campaigns from another platform is an onboarding project, not an API feature. Talk to your Traackr contact about it.

Yes. AI assistants work well with the API's specification: they can write your integration code and query the data you load. Traackr is also preparing an MCP server, so that an AI assistant can query your Traackr data directly. Ask your Traackr contact for its status.

No. The API reflects the Traackr app with a delay of up to 4 hours, usually much less. See Getting started → How current is the data?.

You choose the schedule: there is no publication time to wait for, and no preferred time of day. A daily load is common.

To load only what changed, read the campaign list and compare 3 signals with your previous load:

Records change after you first load them, so update the rows you already hold (upsert) rather than appending new ones. A periodic full reload, for example monthly, is a good safety net. Creator profiles change slowly: a monthly refresh of the profiles you store is enough.

No. Your system asks the API for changes (polling), using the signals above.

There is currently no deletion flag. A record deleted in Traackr is no longer returned: a deleted campaign disappears from the campaign list, and a creator removed from a campaign disappears from that campaign's creator list. Compare the full list of IDs with your previous load to find them.

A post deleted on the social platform stays in Traackr, with its last measured metrics.

Both work. For standard dashboards, and for any history, store the data in your own systems and refresh it on a schedule. For interactive needs, such as a dashboard with many filters, querying the API live works well.

Send no more than 5 requests per second, and no more than 5 requests in parallel. Short bursts above that rate are absorbed. Above the limit, the API answers HTTP 429 and does not process the request. Retry with exponential backoff (for example after 1, 2, 4, then 8 seconds). The response does not show how many requests you have left.

Before a large initial load, contact support@traackr.com.

No. The API is the only way Traackr delivers this data: there is no file export. Every request is answered directly, and lists return up to 100 items per page. Batching (several IDs in one request) is on the roadmap.

To keep the number of requests low:

It depends on the size of your account. Most per-campaign data needs a few requests per campaign, and each creator profile is one request. Posts come 100 per request, so a campaign with 20,000 posts takes 200 requests. A large account can need tens of thousands of requests for its first load. Plan the first load in advance, and run the daily loads on what changed only.

Use of the API is free through 31 December 2026. From January 2027, API access is charged. Your Client Partner will share the terms that apply to your account.

Yes. The API will eventually replace the Data Lake. Your Traackr contact shares your timeline and a migration plan, and supports your team until the move is complete. See The API and the Data Lake, side by side.

Largely, and the API also returns ready-made totals. Some fields have no equivalent: check the ones you use in the field mapping before you switch. Benchmark data will be available through the Benchmark API.

API key holders receive email updates about changes. Ask support@traackr.com to add you if you do not receive them.

Email support@traackr.com. To help us answer quickly, include:

Never include your API key.

Yes. Talk to your Traackr contact about your project. During the first months of an implementation, Traackr can hold regular check-ins and review your data model with your team.

No. The features Traackr has announced are listed in What the API does not cover yet → Coming soon. API key holders also receive email updates when new features ship.

Email support@traackr.com, or tell your account manager. Explain what you need, what you do with it, and whether its absence blocks you. See What the API does not cover yet → How to raise a gap.