[Google Ads Developer Blog] New Required Header for Google Ads API Requests

[adwordsapia...@google.com]

Starting February 11, 2019 if you are making Google Ads API requests using OAuth credentials from a manager account and are accessing a related customer account, you will need an additional HTTP request header/grpc metadata field. You will need to set the login-customer-id header to the customer ID of the manager account, removing any hyphens in the ID.

Setting this new header is essentially equivalent to choosing an account in the Google Ads UI after signing in, and it’s configurable in the client libraries. Each library has instructions in its README that explain how to set a login-customer-id in your local configuration. Here are links to all relevant sets of instructions in each library:

• Python google-ads-python
• PHP google-ads-php
• Java google-ads-java
• Ruby google-ads-ruby
• .NET google-ads-dotnet

If this header is not set, you may begin seeing the error: USER_PERMISSION_DENIED.

For more details on request headers, including login-customer-id, see our documentation.

If you have questions, please reach out to us on the Google Ads API forum.
 Ben Karl, Google Ads API Team

-- Posted By Google Ads Developer Advisor to Google Ads Developer Blog on January 31, 2019.