Included as an omnichannel demand-side platform control surface whose first-party APIs support partner and advertiser setup, campaign and budget automation, ad-group and bid-list operations, first-party data activation, creative workflows, and several reporting products.
Concrete capability record
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
Partners or seats, advertisers, campaigns and flights, ad groups, creatives, budgets, bid lists and bid lines, seeds, first-party data segments and elements, tracking tags, report templates, predefined reports, dimension-specific reports, and report files.
Use REST for fixed platform-resource reads and GraphQL queries for selected fields across partner, advertiser, campaign, and ad-group relationships; inspect budgets, creatives, bid lists, data elements, and pacing; download scheduled, predefined, or dimension-specific reports where the seat and report product permit it.
Use REST or GraphQL mutations to create or update supported advertisers, campaigns, budgets, ad groups, creatives, bid lists, seeds, and activation settings. Kokai-only features and bulk operations are GraphQL-only. Data onboarding and some hidden domains require separate enablement. For replacement-style PUT list properties, retrieve and resubmit the complete list.
Platform API access is provisioned through The Trade Desk onboarding and may require contracts, service-specific paperwork, and account-team enablement. REST and GraphQL calls use a Platform API token generated in the Platform UI and sent in TTD-Auth; standard token lifetimes range from one week to one year and tokens can be revoked. Sandbox and production credentials are issued during onboarding.
Record the partner or seat, advertiser, campaign, ad group, environment, API style, token name and expiry, and operation result. Before mutating bid lists or list-valued ad-group fields, resolve ownership, association, inheritance, and replacement behavior so parent changes or incomplete PUT payloads cannot silently alter descendants.
Access depends on contracted services, onboarding, seat permissions, and possible Technical Account Manager enablement; API credentials alone do not grant Platform UI access. REST and GraphQL domains are not one-to-one, with Kokai-only and bulk capabilities in GraphQL and some legacy Solimar functions in REST. Endpoint rate limits can be dynamically reduced or group-throttled. Reporting latency ranges from near real time for REDS to two-to-three-hour hourly feeds and one-day-delayed report products.
First-party access
Agent access
Support: Third-party only
Read scope: No first-party MCP read surface verified.
Write scope: No first-party MCP write surface verified.
Authentication: The portal's TTD-Auth token contract applies to Platform API integrations; no first-party provider MCP auth is claimed here. A customer-built adapter would use provisioned credentials and a revocable Platform UI token with a chosen lifetime and separate sandbox or production context.
Approval boundary: Require confirmation for campaign activation, budgets, ad-group status, creatives, first-party data activation, and bid-list association or enablement. Show owner and descendant impact before inherited changes, and show the complete replacement payload before PUT operations on list-valued fields.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Proposed customer-shaped experiences
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that The Trade Desk ships them.
Evidence and dates
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
Partners, advertisers, campaigns, campaign sets and flights, ad groups, creatives, bid lists, first-party data elements, tracking tags, and reports. Create and update advertisers, campaigns, ad groups, bid lists,…
Targeted first-party core-access review
First-party API reference or API overview recorded for this platform.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party product homepage used to confirm product identity and current positioning.
Inventory source: structurally normalized; content was not individually reopened in this pass.
Tied to cited first-party evidence reviewed for this profile.
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
System role, maturity interpretation, and architectural boundary.
Interface patterns and compositions—not vendor product claims.
