Authorization is an important concern when writing software that interacts with Google’s Ads APIs. We’ve recently improved our documentation and published resources documenting how to use OAuth2 with many of our Ads APIs.
OAuth2 is an authorization flow that allows you to direct a user to a specially crafted Google URL where they grant permissions to your software to make changes to their account. With an authorized access token, you can make requests to Ads APIs on the user’s behalf. Benefits include:
- Users don’t need to provide a username and password - they just log into Google.
- No CAPTCHA challenges.
- Limited scope - the user will only be prompted to grant access to a specific part of their account. For example, they could grant access to AdWords without the application being able to see their email or calendar.
OAuth2 is supported by:
- AdWords API
- DoubleClick for Advertisers Reporting API
- DoubleClick for Advertisers Trafficking API
- AdSense Host API (v4)
- AdSense Management API
- DoubleClick for Publishers API
- DoubleClick Ad Exchange Buyer REST API
The Ads API client libraries supported by Google have built-in support for OAuth2. We’ve included examples demonstrating how to use this feature in all client libraries. See your respective product and language product sites for more information on OAuth2.
We’re also hosting a Google Developers Live event covering how to use OAuth2 on August 23rd. This will be recorded if you can’t make it. If you have any questions about OAuth2, please post on the respective product API forums.
- Kevin Winter, AdWords API Team
No comments:
Post a Comment