The Trade Desk

The Trade Desk is a programmatic advertising platform that enables advertisers to buy digital ads across multiple channels including display, video, mobile, and social media through real-time bidding technology.

Power end-to-end data operations for your The Trade Desk API with Nexla. Our bi-directional The Trade Desk connector is purpose-built for The Trade Desk, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to The Trade Desk or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your The Trade Desk workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating a The Trade Desk credential, you need to obtain your Long-Lived API Token from your The Trade Desk account. The Trade Desk uses token authentication for all API requests, with the token sent in the TTD-Auth header.

To obtain your The Trade Desk API token, follow these steps:

1. Sign in to your The Trade Desk account using your administrator credentials.

2. Navigate to the API or Developer section in your The Trade Desk account, typically accessible from the account menu or settings.

3. In the API section, navigate to Token Management or API Tokens to access token configuration options.

4. Look for the Long-Lived API Token section in your The Trade Desk API settings.

5. If you don't have a long-lived API token yet, click Create Token or Generate Long-Lived Token to create a new API token.

6. Configure your API token settings:

   • Enter a name for the token (e.g., "Nexla Integration")
   • Review and select the permissions or scopes for the token (if applicable)
   • Set an expiration date if required (optional)

7. Click Create or Generate to create the long-lived API token.

8. Copy the API token immediately after it's generated, as it may not be accessible again after you navigate away from the page.

9. Store the API token securely, as you will need it to configure your Nexla credential. The API token is sensitive information and should be kept confidential.

The API token is sent in the TTD-Auth header for all API requests to The Trade Desk API. The token authenticates your requests and grants access to The Trade Desk resources based on your account permissions. If your API token is compromised, you should immediately revoke it in your The Trade Desk account settings and generate a new one. For detailed information about obtaining and managing API tokens, API authentication, and available endpoints, refer to the The Trade Desk API documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
API URL	Yes	No	Select whether you want to connect to TradeDesk API production or sandbox APIs. Allowed values: Production: https://api.thetradedesk.com/v3; Sandbox: https://apisb.thetradedesk.com/v3
Long-Lived API Token	Yes	Yes	Your TradeDesk long-lived API token. Check for https://api.thetradedesk.com/v3/portal/api/doc/Authentication#ui-method-create for Token Management.

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – The Trade Desk

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

The Trade Desk uses token authentication for all API requests. The API token is sent in the TTD-Auth header, and you can select whether to connect to the production or sandbox API environment.

3. Select your API URL from the API URL dropdown menu. Choose whether you want to connect to The Trade Desk API production or sandbox APIs:

   • Production: https://api.thetradedesk.com/v3 - For production use
   • Sandbox: https://apisb.thetradedesk.com/v3 - For testing and development

4. Enter your Long-Lived API Token in the Long-Lived API Token field. This is the long-lived API token you obtained from your The Trade Desk account (API > Token Management). The API token is sent in the TTD-Auth header for all API requests to The Trade Desk API. The API token is sensitive information and must be kept confidential.

   Your The Trade Desk API token can be found in your The Trade Desk account under API > Token Management. The API token is sent in the TTD-Auth header for all API requests to The Trade Desk API.

   If your API token is compromised, you should immediately revoke it in your The Trade Desk account settings and generate a new one. The API token provides access to your The Trade Desk account data and should be treated as sensitive information. Keep your API token secure and do not share it publicly.

   For detailed information about obtaining and managing API tokens, API authentication, and available endpoints, see the The Trade Desk API documentation and The Trade Desk API overview.

5. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the The Trade Desk connector tile, then select the credential that will be used to connect to the The Trade Desk instance, and click Next; or, create a new The Trade Desk credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common The Trade Desk endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

Fetch a Resource

This endpoint template fetches a specific resource from your The Trade Desk account. Use this template when you need to retrieve detailed information about a specific resource such as an advertiser, audience, campaign, bidlist, or contract for analysis, reporting, or integration purposes.

• Enter the Resource Type in the Resource Type field. This should be the type of resource you want to retrieve (e.g., advertiser, audience, campaign, bidlist, contract). The Resource Type determines which type of resource will be retrieved. You can select from the available options or type a custom resource type if needed.
• Enter the Resource ID in the Resource ID field. This should be the unique identifier of the specific resource you want to retrieve. The Resource ID determines which specific resource will be retrieved.

This endpoint returns detailed information for the specified resource from your The Trade Desk account. The Resource Type determines the API endpoint path, and the Resource ID identifies the specific resource to retrieve.

For detailed information about resources, API response structures, and available resource data, see the The Trade Desk API documentation.

Get Analytics Report for AdGroup

This endpoint template retrieves analytics reports for an existing Ad Group from your The Trade Desk account. Use this template when you need to access performance metrics, campaign analytics, or reporting data for a specific ad group for analysis, reporting, or integration purposes.

• Enter the Ad Group ID in the Ad Group ID field. This should be the unique identifier of the ad group whose analytics report you want to retrieve. The Ad Group ID determines which ad group's analytics will be retrieved.

This endpoint returns analytics reports for the specified ad group from your The Trade Desk account, including performance metrics, campaign data, and reporting information. The Ad Group ID identifies the specific ad group whose analytics will be retrieved.

For detailed information about analytics reports, API response structures, and available analytics data, see the The Trade Desk API documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

The Trade Desk data sources can also be manually configured to ingest data from any valid The Trade Desk API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new The Trade Desk data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination

Click the + icon on the Nexset that will be sent to the The Trade Desk destination, and select the Send to Destination option from the menu. Select the The Trade Desk connector from the list of available destination connectors, then select the credential that will be used to connect to the The Trade Desk instance, and click Next; or, create a new The Trade Desk credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common The Trade Desk endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

Create Resources from Nexset Records

This endpoint template creates resources of a selected type from records in a Nexset in your The Trade Desk account. Use this template when you need to automatically create resources such as advertisers, ad groups, audiences, campaigns, bidlists, or contracts based on data from your Nexla flows.

• Enter the Resource Type in the Resource Type field. This should be the type of resource you want to create (e.g., advertiser, adgroup, audience, campaign, bidlist, contract). The Resource Type determines which type of resource will be created. You can select from the available options or type a custom resource type if needed.
• This endpoint sends data as JSON in the request body to create new resources. Each record from your Nexset will be sent as a separate API request to create a resource. The request body should contain the resource data in the format required by The Trade Desk API, including all required properties for the selected resource type.

This endpoint sends data as JSON in the request body to create new resources in your The Trade Desk account. Each record from your Nexset will be sent as a separate API request to create a resource. The request body should contain the resource data in the format required by The Trade Desk API, including all required properties for the selected resource type.

The resource structure must match The Trade Desk API's expected format. Ensure your resource data includes all required fields for the selected resource type. For detailed information about resource creation, request body formats, and available resource properties, see the The Trade Desk API documentation.

Update Resources from Nexset Records

This endpoint template updates resources of a selected type from records in a Nexset in your The Trade Desk account. Use this template when you need to automatically update existing resources such as advertisers, ad groups, audiences, campaigns, bidlists, or contracts based on data from your Nexla flows.

• Enter the Resource Type in the Resource Type field. This should be the type of resource you want to update (e.g., advertiser, adgroup, audience, campaign, bidlist, contract). The Resource Type determines which type of resource will be updated. You can select from the available options or type a custom resource type if needed.
• This endpoint sends data as JSON in the request body to update existing resources. Each record from your Nexset will be sent as a separate API request to update a resource. The request body should contain the resource data in the format required by The Trade Desk API, including all required properties for the selected resource type.

This endpoint sends data as JSON in the request body to update existing resources in your The Trade Desk account. Each record from your Nexset will be sent as a separate API request to update a resource. The request body should contain the resource data in the format required by The Trade Desk API, including all required properties for the selected resource type.

The resource structure must match The Trade Desk API's expected format. Ensure your resource data includes all required fields for the selected resource type. For detailed information about resource updates, request body formats, and available resource properties, see the The Trade Desk API documentation.

Manual configuration

The Trade Desk destinations can also be manually configured to send data to any valid The Trade Desk API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

The Trade Desk APIs typically expect JSON format for most operations. For update/upsert operations, include the ID of the object to be updated at the end of the URL.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured The Trade Desk endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to The Trade Desk endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.