Archived API changes for advertisers

Effective July 1, 2026, The Trade Desk will deprecate Adbug page quality bid list fields. Adbug is a China-specific fraud verification vendor that's no longer operational and is not supported in Kokai.
The following GraphQL fields will be removed:

• /BidLine/adBugPageQualityCategory
• /BidLine/adBugVideoPageQualityCategory
• /BidListDimension/HAS_AD_BUG_PAGE_QUALITY_CATEGORY_ID

• AdBugPageQualityCategoryId
• AdBugVideoPageQualityCategoryId

Update your bid list workflows to remove the deprecated fields from BidLines objects by July 1, 2026. For details, contact your Technical Account Manager.

Effective July 13, 2026, ImpressionPlacementId values in bid lists will be updated to exactly match values provided by the publishers. The Trade Desk will no longer apply custom updates to these IDs.
For example, most placement prefixes will be restored, and some generic values will change to publisher-specific paths with unique site IDs.

Review the ImpressionPlacementId entries in your target or optimized lists and update any affected values. If you need help identifying affected values or confirming updates, contact your Technical Account Manager. For example, you can request a list of affected values and their updated equivalents.
Your Technical Account Manager will also proactively reach out if your account is affected.

Effective August 3, 2026, as part of The Trade Desk's broad shift to ID-based fields, the EnabledValueAddedProviders field for campaigns and ad groups will be fully deprecated and replaced with the EnabledValueAddedProviderIds field. Instead of an array of provider name strings, the new field accepts an array of provider ID integers. Using the EnabledValueAddedProviders field will return errors.

Update your integration to use the EnabledValueAddedProviderIds field.

The GraphQL AdGroupFlight.minimumSpendInAdvertiserCurrency property, used to set the minimum spend for an ad group flight, has been fully deprecated and replaced with AdGroupFlight.allocationInAdvertiserCurrency in ad group workflows.

Remove the deprecated AdGroupFlight.minimumSpendInAdvertiserCurrency property from all ad group mutations and queries and replace it with the new AdGroupFlight.allocationInAdvertiserCurrency property.

Starting October 3, 2025, if your integrations currently use deprecated REST endpoints and properties that have a scheduled expiration date, you will receive an email notification that includes the following:

• A list of up to five endpoints and properties that are scheduled to expire within 180 days. These items are ordered by their potential risk to your integrations.
• A link to the API dashboard where you can view the full list of deprecated endpoints and properties along with additional details and guidance.

Use the API dashboard to review the deprecated endpoints and properties listed in the email. If you have questions about the level of impact on your integration or require additional guidance, contact your Technical Account Manager.

Starting December 12, 2025, The Trade Desk is introducing Trading Modes, a new campaign feature that defines how bidding, pacing, and optimization are managed. You can choose between two modes:

• Performance Mode (recommended): An end-to-end AI powered buying solution that makes it easier to maximize outcomes with minimal campaign management. Automatically applies AI to optimize every decision by selecting the highest-value impressions based on your inputs and goals.
• Control Mode: This mode enables you to manually select and configure each feature and adjust the campaign settings yourself.

To get started, we recommend creating new campaigns with Performance Mode.

As of July 7, 2025, we will deprecate our legacy External Sandbox environment (https://desksb.thetradedesk.com/). All API traffic directed to the legacy sandbox base URL https://apisb.thetradedesk.com/v3/ will no longer be supported. This change marks the official sunset of the External Sandbox in favor of our new Partner Sandbox, which is already available for use.
NOTE: No production data is affected by this change.
The new Partner Sandbox environment offers major improvements, including the following:

• Access to Kokai features
• Improved performance
• Weekly database refresh from production
• Ongoing long-term support

To ensure uninterrupted support for your testing and development workflows, migrate to the new Partner Sandbox as soon as possible.

• Advertisers in the Shopping category must now include a valid subcategory when created or edited.
• Attempts to create or edit advertisers in this category without specifying a subcategory will result in an error.
• Existing advertisers that are not modified will not be affected.

Update your integration to specify a valid subcategory when creating or editing advertisers in the Shopping industry. Be sure to complete this update as soon as possible—and no later than August 9, 2025. If you have any questions, contact your Technical Account Manager.

Starting November 13, 2024, the AdvertiserAudienceSettings.AudienceBoosterEnabled property, which allows you to configure ad group data settings at the advertiser level, will be disregarded in advertiser workflows. This property will be fully deprecated on April 28, 2025.

To enable the platform to add highly relevant segments to your audience when there is confidence they will improve your targeting and boost performance, continue using the RTBAttributes.AudienceTargeting.AudienceBoosterEnabled property in the ad group workflows. Remove the deprecated AdvertiserAudienceSettings.AudienceBoosterEnabled property from your advertiser workflows by April 28, 2025.

As of March 26, 2025, the GraphQL CampaignPacingSettings.isValuePacing property returns null in all campaign mutations and queries, regardless of its original value. This property is scheduled for full deprecation in the GraphQL schema on June 15, 2025.

Remove the deprecated GraphQL CampaignPacingSettings.isValuePacing property from all campaign mutations and queries by June 15, 2025.

As of June 30, 2025, direct publisher integrations (OpenPath) will no longer be managed using the SupplyVendorId field. As a result, attempts to use the bid list APIs (REST and GraphQL) to manage direct publisher connections through supply vendor bid lists will return an error. The following actions are no longer supported:

• Adding direct publisher connections
• Excluding direct publisher connections
• Adding or modifying bid factors for direct publisher connections
• Retrieving direct publisher connections

Review your current bid list workflows to ensure that they do not rely on the SupplyVendorId field to manage your direct publisher connections (OpenPath). To manage direct publisher inventory, use publisher lists or site lists instead. If you need help transitioning or have advanced supply chain requirements, contact your Technical Account Manager.

Starting January 7, 2025, the currently optional (IsUpfront) field will be required when creating or updating private contracts to indicate whether that the contract is part of an upfront agreement.

Update your contract workflows to include the IsUpfront property by January 7, 2025.

Starting March 31, 2025, new features and updates will be available and function correctly only for specific campaign versions defined by the Version property. For example, to set the budget properly, you must know which version of the campaign you are manipulating, as Solimar and Kokai workflows differ.

Your code must check the campaign version and conditionally use features supported by that version when updating your campaign and related workflows. All REST endpoints are marked with compatibility labels, and the appropriate campaign version is provided in all user guides, giving you everything you need to do this work.
To verify if the campaign Version property is set to Kokai, use the GET /v3/campaign/{campaignId} endpoint. See also Campaign upgrade process.

Starting October 1, 2024, the ChannelId property will be required for all ad group workflows in Kokai, with the following supported values: Display, Video, Audio, NativeDisplay, NativeVideo, TV, OutOfHome. In Kokai, the ad group channel will be used to inform bidding behavior and provide recommendations and insights. For example, if you choose Display, we'll buy only display content for that ad group. If you choose TV for an ad group targeting display inventory, we won't bid. Here's what it means for your integration:

• The ad group creative type must match the channel.
• You cannot update the ad group channel after the flight starts.
• Any deprecated values (Other, Mixed, Native, TVPersonal) included in create and update requests will result in a 400 (Bad Request) error.
• If a Solimar ad group with its channel set to Mixed is upgraded to Kokai, channel filtering will be ignored.
• Mixed will no longer be accepted as a ChannelId property value when cloning campaigns.

• Update all your ad group workflows to include the required ChannelId property and its updated values by October 1, 2024.
• When cloning campaigns, update any ad groups with the ChannelId property set to Mixed to the appropriate value supported in Kokai.

Starting October 29, 2024, all third-party data IDs in segments will be validated to check if they are biddable. Data group workflows will fail when non-biddable third-party data IDs are included in the ThirdPartyDataIds array.

Start using the POST /v3/dmp/thirdparty/advertiser endpoint to check if segments are buyable beforehand, then remove all third-party data IDs that are not listed from your POST and PUT data group workflows.

Starting September 30, 2024, we'll no longer accept the InBanner, InArticle, InFeed, and Outstream values in the VideoPlaybackType property in the ad group endpoints and will return a 400 (Bad Request) error.

Update all your ad group workflows to use the new AccompanyingContent and Standalone values in the VideoPlaybackType property by September 30, 2024.

Starting September 30, 2024, the RetentionEnabled field will be removed from the POST /v3/crmdata/{segmentType}/segment/{advertiserId}/{crmDataId} and POST /v3/crmdata/segment/{advertiserId}/{crmDataId} endpoints. By default, all targeting segments will retain hashed email addresses and phone numbers for 90 days to refresh UIDs daily.
NOTE: Update (March 2025): The retention period is now 180 days. This upgrade note reflects the policy at the time of release.

Update your workflows to remove the deprecated field by September 30, 2024.

As Oracle Advertising is sunsetting their pre- and post-bid products, Grapeshot and Moat, any targeting strategies that depend on these Oracle products will not function after September 30, 2024. All workflows using Moat Reporting will be automatically migrated to our new white-labeled product unless you choose to opt out.

Choose an alternative product as soon as possible.

• For Grapeshot standard and custom contextual categories, we recommend considering The Trade Desk Contextual categories.
• For other Oracle features—such as Grapeshot Content Affinity, Grapeshot Predicts, Moat Viewability, Grapeshot Language, Grapeshot Brand Safety, and Moat Invalid Traffic—contact your Account Manager for guidance on alternative solutions.
• If you prefer to use an alternate provider for Moat Reporting, request the necessary form from your Account Manager and opt out of the default migration by September 23, 2024. Be sure to update your advertiser or partner settings with the new provider by September 30, 2024.

We are removing Adbrain Household as a selection for our API users. Starting September 30, 2024, we'll automatically redirect all API calls with Adbrain Household (Cross-Device Vendor ID 8) to Identity Alliance Household (Cross-Device Vendor ID 11).

Update all your campaigns and ad group workflows currently leveraging Adbrain Household (Cross-Device Vendor ID 8) to use the Identity Alliance Household Graph (Cross-Device Vendor ID 11).