Skip to main content

Public API: Overview of Available Actions

Every action available in the Trackdesk Public API, grouped by area, with a short summary and a link to each endpoint, plus how to authenticate with an API key or OAuth2.

Written by Trackdesk Team

This article lists every action available in the Trackdesk Public API, grouped by area, with a one-line summary of what each endpoint does. Use it to quickly check whether something can be done via the API. For request fields, examples and responses, click the endpoint to open it in the full API reference.

The list covers the full API, used by program owners and their team. Affiliates and advertisers can call a smaller set of these endpoints with their own token.


​

Before you start

  • Base URL: https://TENANT_ID.trackdesk.com. Replace TENANT_ID with your Tenant ID, which is your program's subdomain.

  • Authentication: send your personal access token in the X-Api-Key header (see Personal Tokens and API Access), or use an OAuth2 access token (see OAuth2 authorization below).

  • Full reference: developers.trackdesk.com, also available as an OpenAPI specification.

  • Affiliate and advertiser references: the endpoints an affiliate's or advertiser's own token can call are listed in the Affiliate API (OpenAPI) and the Advertiser API (OpenAPI).

  • Your program's reference: https://TENANT_ID.trackdesk.com/developers has your Tenant ID filled in, and its Test Request calls use your signed-in session, so you can try endpoints without a token.

  • Limits: see API Rate Limiting.

  • AI assistants: the same actions are available through the Trackdesk MCP Server.

Clicks and tracking links

  • Create click: Creates a new click on the server side, without a visitor loading the click tracking script. You send the link ID, affiliate source ID, IP address and user agent (plus optional geo data, referrer, AffS1 to AffS5 and ad click IDs). The response contains the click's CID, which you then use when creating conversions.

  • Build tracking link: Generates a tracking link for a given affiliate and offer (direct, system redirect or Google-certified redirect), optionally with AffS1 to AffS5 parameters appended.

  • List conversion types available for a CID: Returns the conversion types that are available for a given Click ID (CID).

Conversions

Clients and client metrics

A client is your customer (in iGaming programs, a player). See Registering players and recording movements via the API for a worked example.

Affiliates

Affiliate tiers

Affiliate bonuses

Bonuses are one-off amounts added to, or deducted from, an affiliate's open balance and paid out with their next settlement. See Affiliate Bonuses.

Offers

Offer settings and pricing

  • Create offer: Creates an offer with its configuration, pricing and landing pages and publishes it, either immediately or at a scheduled time.

  • List offers: Lists offers matching your filters, each with its pricing and landing pages.

  • Get offer: Returns an offer with its pricing and landing pages.

  • Update offer: Updates the offer's general settings (name, visibility, targeting, tags, description and so on) and its status. Pricing and landing pages have their own endpoints.

  • Update offer pricing: Updates the offer's conversion type settings and targeting groups. This is also where you set a payout for a single affiliate: add it under sourceCosts in a currency group, using the affiliate's source ID, and it overrides their tier payout for that offer. Send the complete pricing, not only the part you changed.

Affiliate access to offers

Landing pages

Creatives

Offer caps

Coupons

Affiliate billing and payouts

For the full payout flow, see Handling Affiliate Billing via API.

Billing details and payment methods

Balances and settlements

Tipalti payouts

Advertisers

Available for networks. In the API, advertisers are called revenue origins.

Reports

Tags

Webhooks

Program settings

OAuth2 authorization

Instead of a personal access token, you can authenticate with an OAuth2 access token. Create a client in Settings → Integrations → OAuth2. Use the client_credentials grant for machine-to-machine access, or authorization_code with PKCE when a user approves the access at https://TENANT_ID.trackdesk.com/oauth/authorize. Access tokens expire after 1 hour, and refresh tokens are replaced with a new one on every use.

  • Create or refresh access token: Issues an access token for the client_credentials, authorization_code or refresh_token grant. Authorization codes need the original redirect URI and the PKCE code verifier.

  • Revoke OAuth grant: Revokes an access or refresh token, together with the whole user authorization behind it. Tokens issued through client_credentials can't be revoked one by one; delete the client instead.

  • Check credential: Checks whether an access token or API key is valid.

  • Register OAuth client: Registers a public client automatically (dynamic client registration), so an app can get a client ID without anyone entering one by hand. The client can't do anything until a user approves it on the consent screen, and registrations nobody approves are deleted within two hours.

Did this answer your question?