As part of ongoing efforts to modernize platforms, and to improve security and reliability, TLS 1.0 and 1.1 have been deprecated by the Internet Engineering Task Force (IETF) as of March 25, 2021. As a result, TLS 1.0 and 1.1 will be blocked on Buzz API going forward.

We previously provided several reference documents in publicly-available Google Docs. These have been migrated to Excel files available in Github and the links in the documentation have been updated.

The 0.5 APIs for the report_queue is now fully deprecated and should not be used. The new Reporting API should be used by all customers.

The 2.0 API now supports Bid Modifiers and Delivery Modifiers. The 2.0 APIs are recommended for all customers moving forward.

The Line Item resources in the 0.5 version of the API now support the target_skad field which limits delivery to inventory that supports Apple's SKAdNetwork reporting.

A new guide page describing how to Bulk Edit Targeting has been published.

Line Item and Campaign definitions have been updated to include the new frequency_cap_vendor field that allows for frequency caps using third-party device graphs from TapAd and LiveRamp. The Frequency Caps guide has also been updated with new frequency_cap_type values. These changes are only in the 0.5 API version.

New guide page describing using the Reporting API when in a Multi-Account context: Multi-Account Reporting .

The following 2.0 APIs are now available:

The 2.0 API now supports CSV and Excel formatting for responses.