All guides, by feature
Create a Trade Desk API key for Claude Code
Create a key under MCP API Keys on The Trade Desk page, copy it straight away, and add it to Claude Code’s .mcp.json. Orbit shows each key only once.
Before you start
- You need
- Your agency’s Trade Desk credentials, saved on the same page.
- Where in Orbit
- Sidebar › Data › Integrations
Steps
Tick a step’s number when it’s done. We’ll remember where you were.
Open Integrations and choose The Trade Desk.
Under , press + New API Key.
Give the key a Name you’ll recognise, such as the laptop it’s for, and press Create.
In API key created, press Copy, store the key somewhere safe, then press I've saved it.
To use it, press Connect with Claude and follow Claude Code / stdio (advanced): put the key in the snippet, save it as .mcp.json in your Claude Code project, and restart Claude Code.
When it worked
Orbit confirms “Copied to clipboard” when you copy the key. The key is listed with its [[Prefix]], [[Created]] date and [[Last used]] time.
If something goes wrong
Orbit showsCopy this key now — it will not be shown again. If you lose it, revoke and create a new one.
Orbit can’t show it again. Press Revoke beside it and create a new one.
Orbit showsName is required
Type a name of up to 100 characters, then press Create.
A key may have leaked.
Press Revoke beside it. Requests using it start failing within about 60 seconds. Then create a new key.
How it works
Explainer: Two ways to connect Claude to The Trade Desk
Claude.ai connects through a custom connector that you approve with your Orbit login. Claude Code and other tools use an API key you create in Orbit.
| Claude.ai connector | API key | |
|---|---|---|
| Best for | Claude.ai. Orbit recommends it. | Claude Code and other tools that read an .mcp.json file. |
| How you connect | Add a custom connector in Claude.ai and approve it. | Create a key in Orbit and paste it into .mcp.json. |
| Listed under | Connected Clients (Claude.ai) | MCP API Keys (Claude Code / advanced) |
| When revoked | Stops at once. The person re-authorizes from Claude.ai’s connector settings. | Requests start failing within about 60 seconds. |
| What Claude can do | Set by Read-only mode. | Set by Read-only mode. |
- Each API key is shown once, when you create it. If you lose it, revoke it and create another.
- Keys last until they’re revoked. The table lists each one’s Prefix, Created date and when it was Last used.
- The approval screen in Claude.ai says what Claude may do: “Read and modify TTD data”, or “Read TTD data (agency is in read-only mode)”.
- Owners and Admins see and can revoke every Claude.ai connection at your agency. Everyone else sees only their own.
Explainer: The Trade Desk credentials and modes
Your agency saves one set of Trade Desk credentials in Orbit. Claude uses them through Orbit’s Trade Desk server, and Command Center checks them before a push to The Trade Desk.
| Field | What it does |
|---|---|
| TTD API Token | Your Trade Desk API token. Stored encrypted and never shown again. When updating, leave it blank to keep the current one. |
| Partner ID | Required. Your Trade Desk partner ID. |
| Default Advertiser ID (optional) | An advertiser to use by default. |
| Environment | Production or Sandbox. |
| Read-only mode on | “Writes blocked. Agents can read TTD data only.” This is the default. |
| Read-only mode off | “Writes allowed. Agents may create campaigns, ad groups, etc.” |
| Optional · DMP workflows credential | A separate credential that only the DMP toolset needs. |
- Connected means a token is saved. Orbit doesn’t check it with The Trade Desk.
- There’s one set per agency. Saving again replaces it for everyone.
- Once saved, the page shows the Partner, Environment, Mode and when they were Last updated.
- Command Center’s push checks include TTD credentials configured and TTD-MCP key issued.