Page History

December 9, 2025

Lists and Custom List Items 2.0 APIs Now Available

What is it? The 2.0 versions of the lists and custom list items endpoints are now available for use. This release simplifies the API JSON structure and adds new PATCH methods for partial updates.

How am I affected? Customers may now start using the 2.0 APIs for lists and custom list items. The deprecation date for the 0.5 custom lists and list items APIs will be announced at a future date.

The new endpoints are listed below:

• /lists
• /lists/{id}
• /lists/{id}/duplicate
• /custom-list-items
• /custom-list-items/bulk
• /custom-list-items/{id}
• /custom-list-items/delete-all-for-list/{list_id}

Resource(s): Lists

November 12, 2025

Alerts and Account Alerts 2.0 APIs Now Available

What is it? The 2.0 versions of the alerts and account alerts endpoints are now available for use. This release simplifies the API JSON structure and adds new PATCH methods for partial updates.

How am I affected? Customers may now start using the 2.0 APIs for alerts and account alerts. The deprecation date for the 0.5 alerts and account alerts APIs will be announced at a future date.

The new endpoints are listed below:

• /alerts
• /alerts/dismiss-all
• /alerts/{id}
• /alerts/{id}/dismiss
• /account-alerts
• /account-alerts/{id}

Resource(s): Alerts

August 11, 2025

Deprecation of Legacy Ads.txt Values

What is it? As announced on May 13th, the legacy ads.txt values will be deprecated on August 12th. All customers must use the new ads.txt values outlined below:

How am I affected? Starting on August 12th, any calls using the deprecated targeting values will receive an error until the call is updated with the new values. The impacted endpoints are listed below:

• /targeting-expressions
• /targeting-expressions/{id}

Resource(s): List of Targeting Modules and Keys

June 16, 2025

Change to Expected Values for 2.0 Creative Attributes

What is it? For the attributes object in the creatives GET response, users previously would see NULL when there was no value. With this change, users will begin seeing {} instead.

How am I affected? On June 17th, 2025, the 2.0 creatives endpoint will begin returning {} for the attributes object when there is no value. Please ensure your systems will be able to handle this change in value type. The affected endpoint is listed below:

• /creatives

Resource(s): Creatives

June 10, 2025

New Validation for 2.0 Flight Budgets

What is it? For the active_flights array of objects within the 2.0 line item endpoints, a new validation is being added that will require a minimum budget of 1 for impressions_budget and a minimum budget of 0.01 for spend_budget.

...

Resource(s): Line items

May 19, 2025

New Validation for 2.0 Campaign Endpoints

What is it? A new validation will now require inputting an advertiser ID when creating new campaigns. This was already labeled as required in documentation, but was not enforced through a validation.

...

What is it? The release of the API targeting key changes to support app-ads.txt, originally announced on February 10th, 2025, will go live on May 13th, 2025. This change will result in the deprecation of some of the targeting values for this key, which will occur on August 12th, 2025. The updates to the targeting values are listed below:

How am I affected? On May 13th, 2025, the migration to the new targeting values can begin. Any existing calls using the deprecated targeting values after this date will be translated to the new targeting values to ease the transition while adjustments are made to the API calls. This translation will continue until the deprecation date of August 12th, 2025. The impacted endpoints are listed below:

...

Resource(s): List of Targeting Modules and Keys

May 5, 2025

New Field on 2.0 Creative Vendor Fees

What is it? A new field called vendor_fees/read_only will start being returned in API responses for some creatives endpoints. This new field will help API users know if a vendor fee is read only or editable.

...