Sunset of DFP API v201605

On Wednesday, May 31, 2017, in accordance with the deprecation schedule, v201605 of the DFP API will be sunset. At that time, any requests made to this version will return errors.

If you're still using this version, now's the time to upgrade to the latest release and take advantage of new features like native ad styling, additional DAI fields, and the change history table. To do so, check the release notes to identify any breaking changes, grab the latest version of your client library, and update your code.

Significant changes include:

• The integer AdRule.id was replaced with the long AdRule.adRuleId. The values of existing IDs are the same.
• Removed paging support from ProposalService.getMarketplaceCommentsByStatement.
• getCustomTargetingValuesByStatement() now properly enforces the requirement of a custom targeting key ID in the filter statement.
• Added PROPOSAL_OUT_OF_SYNC_WITH_MARKETPLACE that will be thrown in rare cases where a programmatic proposal is out of sync with its Marketplace version.
• ProposalAction.DiscardProposalDrafts has been renamed to ProposalAction.DiscardLocalVersionEdits to more accurately reflect its purpose.
• Order.programmaticSettings has been removed in favor of Proposal.ProposalMarketplaceInfo.
• AD_SERVER_DELIVERY_INDICATOR has been renamed to LINE_ITEM_DELIVERY_INDICATOR and is now a dimension attribute.
• Team.companyIds, Team.adUnitIds, and Team.orderIds have been removed. Use Company.appliedTeamIds, AdUnit.appliedTeamIds, and Order.appliedTeamIds instead.
• GrpProvider.COMSCORE has been renamed to GrpProvider.GOOGLE.

This is not an exhaustive list, so as always, don't hesitate to reach out to us with any questions. To be notified of future deprecations and sunsets, join the DFP API Sunset Announcements group and adjust your notification settings.

 - Gabe Rives-Corbett, DFP API Team