We are making the following changes to AdWords OAuth Scopes during the week of
January 8, 2018.
Invalid OAuth scopes will no longer be supported
One mistake that developers make when obtaining an OAuth2 access or refresh token for AdWords API is to use the service URL prefix (e.g.
https://adwords.google.com/api/adwords/cm/v201708,
https://adwords.google.com/api/adwords/reportdownload/v201708) as OAuth2 scope. When we switched to OAuth2, this was a common source of confusion for AdWords API users, so we allowed developers to use these scopes. Since most users are now using the new scope, we are sunsetting these old scopes. Any refresh tokens authorized with the old scopes will stop working with an
invalid_scope error. If this error occurs, you will have to
re-authorize your users with the proper AdWords scope (
https://www.googleapis.com/auth/adwords) to continue making API calls.
Change to permitted OAuth 2.0 scopes when creating Location Extension feeds
When
creating a Feed for Location Extensions, make sure you set the
OAuthInfo object’s
httpRequestUrl field to the AdWords API scope (
https://www.googleapis.com/auth/adwords). In the past, we also supported using the Google My Business scope (
https://www.googleapis.com/auth/plus.business.manage) for this field; we are sunsetting support for this scope. Similarly, the
httpAuthorizationHeader field must have an access token that is authorized for the AdWords API scope.
While we don’t expect most users to be affected by these changes, make sure you review your code and make necessary changes if needed. As always, if you have any questions, let us know on the
AdWords API forum.
Anash P. Oommen, AdWords API Team
