canonical: https://jentic.com/apis/thetradedesk.com/thetradedesk

# The Trade Desk API

The Trade Desk programmatic advertising platform API. Manage advertisers, campaigns, ad groups, creatives, audiences, bid lists, contracts, CRM data, and more. The API exposes 47 endpoints secured with bearer authentication.

## For AI agents

Programmatically authenticate and obtain API token, create advertiser. Covers 47 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for marketing only.

## Capabilities

- Authenticate and obtain API token
- Create advertiser
- Update advertiser
- Get advertiser by ID
- Query advertisers by partner

## Use cases

### Marketing Operations

Use the The Trade Desk API to perform marketing operations programmatically. The API provides 47 endpoints covering core functionality including authenticate and obtain API token, create advertiser, update advertiser.

Example prompt: Call POST /authentication to authenticate and obtain API token

### Automated Authentication Management

Automate authentication operations by combining multiple The Trade Desk API endpoints. Agents can create advertiser and then update advertiser in a single workflow.

Example prompt: Call POST /advertiser to create advertiser, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call The Trade Desk API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Example prompt: Search Jentic for 'authenticate and obtain API token', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /authentication | Authenticate and obtain API token |
| POST | /advertiser | Create advertiser |
| PUT | /advertiser | Update advertiser |
| GET | /advertiser/{advertiserId} | Get advertiser by ID |
| POST | /advertiser/query/partner | Query advertisers by partner |
| POST | /campaign | Create campaign |
| PUT | /campaign | Update campaign |
| GET | /campaign/{campaignId} | Get campaign by ID |

## Key resources

- **Authentication** — Authenticate and obtain API tokens
- **Advertisers** — Manage advertiser accounts
- **Campaigns** — Manage advertising campaigns
- **CampaignFlights** — Manage campaign flights (budget scheduling)
- **AdGroups** — Manage ad groups within campaigns

## Why Jentic

- **Setup:** Wiring The Trade Desk API by hand means calling POST /authentication for a token, passing that bearer token on each request, and handling your own retries. Through Jentic you install once, import The Trade Desk API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** The Trade Desk API puts the advertiser id in the URL path (/advertiser/{advertiserId}), so a rule can pin your agent to one advertiser: it can read that advertiser and nothing else. You choose the operations it may call, so writes like creating or updating advertisers and campaigns are not included unless you add them.
- **Credential handling:** Your The Trade Desk token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get an advertiser by id' or 'create a campaign', and Jentic returns the matching The Trade Desk operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mailchimp** — Alternative marketing API
- **Hubspot** — Alternative marketing API

## FAQ

### What authentication does the The Trade Desk API use?

The The Trade Desk API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I authenticate and obtain API token with the The Trade Desk API?

Yes. Use the POST /authentication endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the The Trade Desk API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I authenticate and obtain API token through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'authenticate and obtain API token'. Jentic returns the matching The Trade Desk API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the The Trade Desk API have?

The The Trade Desk API exposes 47 endpoints covering authentication, advertisers, campaigns operations.

### Can I limit what my agent is allowed to do with the The Trade Desk API?

Yes. Because you run Jentic One yourself, your own rules decide which The Trade Desk operations and credentials the agent may use. Since the advertiser id sits in the URL path (/advertiser/{advertiserId}), you can pin the agent to a single advertiser so it reads that advertiser and nothing else. You also pick the exact operations it may call, so write actions like creating or updating advertisers and campaigns stay out of reach unless you explicitly grant them.