Wednesday, 25 January 2012

AdWords, DFA and DFP Client Library Updates

We’re constantly making improvements to our AdWords, DoubleClick for Advertisers (DFA) and DoubleClick for Publishers (DFP) client libraries across all supported languages. Recently, we added the following features. Read the ChangeLogs and READMEs for details on these changes: 
  • GZIP compression used when sending and receiving API calls and reports. (Perl and Java do not have this for AdWords API Report Downloads).
  • SSL certificate verification.
  • AdWords only - Examples and support for the new CreateAccountService.
Please see below for a summary of other changes for each library. DotNet
  • No other updates.
  • A preview version of the rewritten Java client library is now available for AdWords, DFA and DFP APIs. Please consider this alpha-quality code; please file any bugs or feature requests on the issue tracker. The new library currently supports Maven2, SLF4J, OAuth and we have plans to support other environments and platforms.
  • Improved parameters validation and error reporting on missing / mistyped fields.
  • HTTP headers are now logged on DEBUG level.
  • Fixes to OAuth logic to better handle misconfigurations.
  • Several bug fixes.
  • AdWords only - Added example to get the clientCustomerId for a clientEmail.
  • AdWords only - Fixed issue with GetAccountHeirarchy example when used in the sandbox.
  • Fixed issue with lingering "id" attribute after reference replacement. Added tests for SoapXmlFixer.
  • Validation and error handling has been improved to make it easier to use OAuth and Google AppEngine.
You can download updated versions of our client libraries from their respective sites, or see a list of all client libraries: AdWords, DFA and DFP.

No comments:

Post a Comment

Share This Post