The Trade Desk
The Trade Desk is a global programmatic advertising platform and demand-side platform (DSP) that enables advertisers, agencies, and media buyers to plan, manage, and optimize digital advertising campaigns across connected TV, display, video, audio, native, and mobile channels. The platform provides REST and GraphQL APIs for managing advertisers, campaigns, ad groups, creatives, targeting, bidding strategies, audience data segments, and campaign performance reporting at scale.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles The Trade Desk the way a machine reads it — 52 machine-readable artifacts across 7 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — The Trade Desk scores 40.8/100 (thin), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile The Trade Desk
Each block below is one kind of artifact we hold for The Trade Desk. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 7
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
The Trade Desk Platform API
The Trade Desk Platform API provides REST and GraphQL interfaces for programmatically managing all aspects of programmatic advertising campaigns. Key resources include advertise...
The Trade Desk Real-Time Conversions API
The Trade Desk Real-Time Conversions API (formerly the Real-Time Conversion Events API) allows advertisers to send conversion events server-side in real time, enabling more accu...
The Trade Desk Reporting API
The Trade Desk Reporting API provides programmatic access to campaign performance data including impressions, clicks, conversions, spend, win rates, viewability, effective CPM, ...
The Trade Desk Advertiser API
The Advertiser API from The Trade Desk — 1 operation(s) for advertiser.
The Trade Desk DeletionOptOut API
The DeletionOptOut API from The Trade Desk — 3 operation(s) for deletionoptout.
The Trade Desk OfflineConversion API
The OfflineConversion API from The Trade Desk — 1 operation(s) for offlineconversion.
The Trade Desk ThirdParty API
The ThirdParty API from The Trade Desk — 1 operation(s) for thirdparty.
Scroll within the panel for all 7 ·
GraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
The Trade Desk GraphQL API
The Trade Desk is a demand-side platform for programmatic advertising. Their API covers campaign management, ad groups, targeting segments, creatives, deal management, and repor...
GRAPHQLSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
context Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
The Trade Desk API Rules
SPECTRALJSON Schema 34
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
AdvertiserData
JSON SCHEMAAdvertiserDataItem
JSON SCHEMAAdvertiserDataRequest
JSON SCHEMAAdvertiserDataResponseErrorCode
JSON SCHEMAAdvertiserDataServerResponse
JSON SCHEMAAdvertiserDataServerResponseLine
JSON SCHEMAAdvertiserDsrFailedLine
JSON SCHEMAAdvertiserDsrRequest
JSON SCHEMAAdvertiserDsrResponse
JSON SCHEMADataOrigin
JSON SCHEMADataOriginType
JSON SCHEMADsrErrorCode
JSON SCHEMAMerchantDsrFailedLine
JSON SCHEMAMerchantDsrRequest
JSON SCHEMAMerchantDsrResponse
JSON SCHEMAOfflineConversionDataItem
JSON SCHEMAOfflineConversionDataRequest
JSON SCHEMAOfflineConversionDataResponseErrorCode
JSON SCHEMAOfflineConversionDataServerResponse
JSON SCHEMAOfflineConversionDataServerResponseLine
JSON SCHEMAPartnerDsrDataItem
JSON SCHEMAPartnerDsrRequestType
JSON SCHEMARealTimeConversionEventLineItem
JSON SCHEMARealTimeConversionEventsPrivacySetting
JSON SCHEMAStringStringValueTuple
JSON SCHEMAThirdPartyData
JSON SCHEMAThirdPartyDataItem
JSON SCHEMAThirdPartyDataRequest
JSON SCHEMAThirdPartyDataResponseErrorCode
JSON SCHEMAThirdPartyDataServerResponse
JSON SCHEMAThirdPartyDataServerResponseLine
JSON SCHEMAThirdPartyDsrFailedLine
JSON SCHEMAThirdPartyDsrRequest
JSON SCHEMAThirdPartyDsrResponse
JSON SCHEMAScroll within the panel for all 34 ·
Examples 6
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for The Trade Desk — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/the-trade-desk · machine-readable index on apis.io