Skip to main content

Connect to Trackdesk: API, MCP and AI Assistants

How external tools, integrations and AI assistants access Trackdesk, what they can see, and which way of connecting fits your use case.

Trackdesk connects to external tools in three ways: AI assistants such as Claude and ChatGPT through the Trackdesk MCP server, personal tokens (static API keys), and OAuth2 credentials. Every connection acts as one Trackdesk account and can do only what that account can do in the app.

💡 Tip: To use AI without connecting anything, use the AI assistant built into your dashboard: open the Search or ask AI… bar and switch to AI Chat.


​

Connect an AI assistant in a minute

The fastest way in is an AI assistant. It takes three steps and no API key:

  1. Open the connector screen of your assistant: Claude or ChatGPT.

  2. Paste your Trackdesk server URL:

    https://TENANT_ID.trackdesk.com/mcp

    Replace TENANT_ID with your Tenant ID.

  3. Sign in to Trackdesk and click Allow access.

Your assistant can now answer questions like "Which affiliates brought the most approved conversions last month?" or "Approve all pending conversions older than 30 days", and asks before it changes anything.

Using Claude? If you're an admin or a team member who can manage OAuth2 credentials, navigate to Settings → Integrations → OAuth2 (or Integrations) and click Add to Claude in the Connect Trackdesk to Claude banner. Claude opens its custom connector dialog with the name Trackdesk and your server URL already filled in, so you only confirm, sign in and click Allow access.

For details, see Connect Trackdesk to Claude and Connect Trackdesk to ChatGPT. Other assistants that support MCP, such as Cursor or Windsurf, are covered in Trackdesk MCP Server.


​

Every connection acts as one account

Whatever you connect, it never gets a special "system" access. It always acts as one specific Trackdesk account and can do exactly what that account can do in the app, nothing more:

  • Admins: The full API, covering offers, affiliates, conversions, reports, payouts and settings.

  • Team members: Limited by their role, the same way they are in the dashboard, for example an affiliate manager.

  • Affiliates and advertisers: A smaller part of the API that covers only their own data: their offers, coupons, balances, payouts and reports.

To give an integration less access, connect it with an account whose role matches what it should be allowed to do.


​

AI assistants for your affiliates and advertisers

Because every connection is tied to one account, your affiliates can connect their own AI assistant too, and it only ever sees their own part of your program. An affiliate goes through the same three steps above, signs in with their affiliate account, and can then ask things like:

  • "How many conversions did my coupon bring this week?"

  • "What is my open balance and when was my last payout?"

  • "Which of my landing pages converts best?"

To let affiliates and advertisers connect their own applications, navigate to Settings → Integrations → OAuth2 and switch on Allow affiliates and advertisers to create their own OAuth2 credentials. They then manage their connections under Tools → Integrations → OAuth2, where they can delete an assistant's credentials at any time to disconnect it.

You can disconnect any application yourself by deleting its credentials on the same settings page, as described in OAuth2 Credentials.


​

Choose how to connect

  • AI assistant (Claude, ChatGPT and other MCP clients): Paste the server URL and approve the access. The assistant signs in with OAuth2 automatically. See Trackdesk MCP Server.

  • Personal token: A single static key you send with each API request. The simplest choice for scripts, Zapier or WooCommerce. See Personal Tokens and API Access.

  • OAuth2, server to server (client_credentials): Your backend exchanges a client ID and secret for short-lived access tokens. Choose it when you want a secret you can rotate.

  • OAuth2, user-approved (authorization_code with PKCE): For your own app used by many people. Each user signs in to Trackdesk and approves the access, and the app acts as that user.

Both OAuth2 options are described in OAuth2 Credentials.


​

Who can create access

  • Admins: Can create personal tokens and OAuth2 credentials for themselves, and on behalf of any enabled affiliate or advertiser. Only the account a token or credentials belong to can see the token value or the client_secret: the affiliate or advertiser copies the token under Tools → Integrations → Personal token, or gets a client_secret by rotating the secret under Tools → Integrations → OAuth2.

  • Affiliates and advertisers: Can create their own only when you allow it. Personal tokens and OAuth2 credentials each have their own switch, and both are off by default. Switching one off stops new tokens or credentials from being created; the existing ones keep working until you or the owner delete them.

While you're impersonating an affiliate or advertiser, their Personal token and OAuth2 pages under Tools → Integrations open. You can generate and delete their personal tokens and create and delete their OAuth2 credentials, but token values and the client_secret stay hidden, and Rotate secret and Connected applications aren't available.


​

Before you build an integration

Related Articles
Did this answer your question?