What is the difference between using the API and using MCP?

The same thing runs underneath. The API is what you build against in code, and MCP is a hosted layer that lets an AI client discover and call those endpoints for you, so the choice is about who writes the request rather than what the platform allows.

Do I need a developer to work with the offer endpoints?

Not for every task. Through an MCP-compatible AI client you can describe the change in plain language and have it resolve and run the call. Your team still reviews what it produced before it goes live.

Can an AI agent create offers, or only edit existing ones?

Both. The offer endpoints cover creating an offer, updating its data and pricing, setting affiliate access, managing creatives and ordering landing pages. Deleting an offer is not among them, so retiring one stays a dashboard action.

Affiliate Program API

Run The Program From The Systems You Already Use

Point your own code or an AI agent at Trackdesk and handle offers, conversions, billing and reporting without a click in the dashboard.

20 Offer Endpoints

Reachable Over MCP

Token-Scoped Access

Server-Side Tracking

Start 14-day FREE trial

No Credit Card Required

Read The API Docs

Case Study

What The Public API Covers

Trackdesk puts the whole platform behind one authenticated interface, and three things define how you use it: reach, access, and MCP.

Reach Across The Platform

Spans affiliate management, offer configuration, conversion handling, billing and reporting: 97 documented operations your code can call.

Access Scoped To The Token

Runs on personal access tokens sent as an API key header: a token does what the account that issued it can do, and nothing more.

Available In AI Clients

Answers over Trackdesk MCP through two tools, search and execute: an AI client resolves the right endpoint and runs it inside the same session.

Run The Offer Lifecycle Without Touching The Dashboard

Offer endpoints are public, so setups that used to run click by click now run from your own code. Pair them with webhooks and automation flows to close the loop.

Repricing Runs From Your Own Systems

Adjust commission schemas and tiers through the API, so payout terms track your unit economics instead of a manual edit.

Private Offer Access Opens On Its Own

Grant or revoke affiliate access to private offers remotely, or wire it into an automation flow keyed to partner tier or status.

Landing Page Targeting Follows Live Data

Manage landing pages and their targeting from outside Trackdesk, and set the priority order visitors get routed through.

Creatives Arrive Through A Pipeline

Set up flows that push new and updated creatives to the right offers, so your library and what affiliates see stay in sync.

Tracking Links Reach Partners Anywhere

Build affiliate tracking links programmatically and push them into your own portal or wherever your partners actually log in.

AI Agents Set It Up, Your Team Reviews

The same endpoints are reachable over Trackdesk MCP, so you describe what you need in your AI client and your team reviews the result.

Three Steps: From Token to First Request

Self-Serve From Inside Your Account

Read the API Docs

Generate A Personal Access Token

In Trackdesk, open Settings → Integrations → Personal access tokens and generate a key. Requests go to your own program subdomain and carry that key in an X-Api-Key header.

Call The Endpoints You Need

Point your integration at the developer portal, which documents the available endpoints along with request and response shapes for each. Build against it directly, or let an existing CRM, ERP or BI tool read and write on your behalf.

Review Changes In Activity Logs

Offer, pricing and landing page edits made through the API land in activity logs on Enterprise plans, alongside manual ones.

Frequently Asked Questions

Yes. In-browser tracking scripts can be disabled and conversion creation routed through server-side API calls instead.