Refer to the table below to verify if the methods you are currently using will be available in v1.1 after February 26, 2021:
| Service | Methods | Available in v1.1 after February 26, 2021? |
|---|---|---|
| Reporting | queries.createquery queries.deletequery queries.getquery queries.listqueries queries.runquery reports.listreports | Yes |
| Line Item | lineitems.downloadlineitems lineitems.uploadlineitems | No. Use the new Display & Video 360 API instead. |
| SDF Download | sdf.download | No. Use the new Display & Video 360 API instead. |
If you are still using the DBM API v1 Reporting service, you must migrate to v1.1 by the sunset date to avoid an interruption of service. Consult the API release notes for the finer details of the changes between v1 and v1.1. Differences to note during this migration include:
- Queries created and accessed through the Reporting service require more specific filters in the
params.groupByfield in v1.1. You might have to add more values to theparams.groupByfield in order to create the same report structure generated in v1. - Responses from queries.listqueries and reports.listreports calls are paginated in v1.1. Users have to update their implementation to traverse multiple pages if they wish to consume more than the first 100 items returned.
If you are using any version of any other DBM API service, you must migrate to the Display & Video 360 (DV360) API.
- The DBM API SDF Download service is being replaced by the DV360 API asynchronous SDF Download service. It features new filter options and a new download format.
- The DBM API Line Item service is being replaced by the DV360 API Line Item service. This service provides create, update, and delete methods for line items using a more easily managed REST Line Item resource separate from Entity Write File format currently used in the DBM API.
Guides are available to help you set up the Display & Video 360 API and get started using it to download SDFs and manage your line items.
If you encounter issues with your migration or want to report a separate issue, please contact us using our support contact form.
- Trevor Mulchay, Display & Video 360 API Team