Today, we launch v201408 of the DFP API. This release features the addition of a new table to the Publisher Query Language service, some changes to the LineItem.Goal object, a multitude of enhancements to our Sales Manager services, as well as changes to our server endpoint and scope URLs. A detailed list of these features and what’s changed can be found on our
release notes page.
New Endpoint URL
Version v201408 of the DFP API changes the endpoint URL for requests from
https://www.google.com to
https://ads.google.com. For example:
https://ads.google.com/apis/ads/publisher/v201408/CompanyService?wsdl
All of our
DFP API client libraries have been updated to reference this URL starting with the v201408 release. If you are using a supported version of the client libraries, then no changes will be required. Otherwise, please update your code to make requests against this new URL.
Line Item goals, Sales Manager refactorings, and more PQL support
In v201408, we have added the field of
Goal.goalType to the
LineItem.Goal; this replaces what was formerly
lineItem.duration and adds back support to create / update the line item types impacted in v201405 (listed
here).
We've also done some significant refactoring of our Sales Manager API services adding premiums to rateCard objects. Prior to this version, there was a
RateCardCustomizationService as well as a
RateCardCustomizationGroupService; both were required to add a feature premium to an existing
rateCard. This has now been replaced with a singular service named
PremiumRateService.
In addition, we've also heard you loud and clear that PQL tables make development easier - in v201408, we provide support for the
Audience_Segment_Category table.
New OAuth 2.0 Scope
With the release of v201408 of the DFP API, we will be introducing a new
OAuth 2.0 scope. This scope identifies the service that your application will access during the authorization process.
https://www.googleapis.com/auth/dfp
This new scope better aligns with the naming conventions of many of the other Google APIs.
Starting from today, you should use the new scope when authorizing access for the DFP API regardless of the DFP API version. All our current DFP API client libraries use this new scope.
But I have refresh tokens from the deprecated scope...
Don't worry if your client code is using refresh tokens authorized with the deprecated scope - they will still work. However, new authorizations should specify the new scope.
- Nicholas Chen, DFP API Team
