March 10, 2025
Update to Advertiser 2.0 PATCH Required Fields
What is it? A fix has been made to an identified bug that was allowing for the use of the advertiser PATCH method to update active advertisers without specifying the advertiser category or advertiser domain. Due to exchange requirements, those fields are required to be declared on the advertiser level to ensure that information is always being passed.
How am I affected? On March 11, 2025, a fix will be implemented that will prevent using the PATCH method to update active advertisers if they don't have a declared advertiser category or advertiser domain. The affected endpoints are listed below:
- /advertisers/{id}
- /advertisers/bulk
- /advertisers/bulk/validate
Resource(s): Advertisers Endpoints
March 7, 2025
Creative Asset Upload 2.0 Endpoint Now Available
What is it? The creative asset upload endpoint has been released to allow uploading assets using the 2.0 API. Users who have already migrated other creatives APIs to 2.0 should begin using this endpoint.
How am I affected? The below endpoint is now available and ready to use:
- /creative_asset/upload/{id}
Resource(s): Creative Asset Upload
Timing Update to Ads.txt Targeting Key
What is it? The release of the API targeting key changes originally announced on February 10, 2025 is being temporarily delayed. The new release date and deprecation date are provided below. For more details, users can refer to the "Ads.txt Targeting Key Update" from February 10.
How am I affected?
- New release date: April 8, 2025
- New deprecation date: July 8, 2025
Resource(s): List of Targeting Modules and Keys
February 10, 2025
Ads.txt Targeting Key Update
What is it? On March 11th, 2025, Beeswax will add support for app-ads.txt into the existing ads.txt targeting key. This change will result in the deprecation of some of the targeting values for this key, which will occur on June 10th, 2025, 90 days after the release of the new values. This update aims to make ads.txt and app-ads.txt targeting more efficient and streamlined. The updates to the targeting values are listed below:
| Old Targeting Label | Old Targeting Value | New Targeting Label | New Targeting Value |
|---|---|---|---|
| No Domain | 0 | Unknown | 9 |
| No Ads.txt File | 1 | Unauthorized | 8 |
| Ads.txt File Not Scanned | 2 | Unauthorized | 8 |
| No Advertising Allowed | 3 | Unauthorized | 8 |
| Missing Publisher ID | 4 | Unknown | 9 |
| Not Authorized | 5 | Unauthorized | 8 |
| Authorized - Reseller | 6 | No Change | No Change |
| Authorized - Direct | 7 | No Change | No Change |
How am I affected? As of March 11th, 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 June 10th, 2025. The impacted endpoints are listed below:
- /ref/ads-txt
- /targeting-expressions
- /targeting-expressions/{id}
Resource(s): List of Targeting Modules and Keys