[null,null,["最后更新时间 (UTC)：2025-07-25。"],[[["\u003cp\u003eOAuth 2.0 allows third-party apps to access protected data with user or app's own authorization.\u003c/p\u003e\n"],["\u003cp\u003eYou need an OAuth 2.0 client ID for your app to request access to your organization's location data on behalf of users.\u003c/p\u003e\n"],["\u003cp\u003eIt's recommended to combine Merchant Center and Ads OAuth requirements during setup.\u003c/p\u003e\n"],["\u003cp\u003eOffline access is crucial for refreshing access tokens without repeated user prompts.\u003c/p\u003e\n"],["\u003cp\u003eUsing a client library for OAuth implementation is highly recommended.\u003c/p\u003e\n"]]],["OAuth 2.0 enables third-party applications to access HTTP services, either on behalf of a user or itself, requiring an OAuth 2.0 client ID. Google APIs use OAuth 2.0 for authentication and authorization. When integrating, combine Merchant Center and Ads OAuth requirements. Set `access_type` to `offline` to enable refreshing access tokens, and use Google's Client Libraries for OAuth implementation. Merchants should grant read/write access with the scope: `https://www.googleapis.com/auth/adwords`.\n"],null,["4.1.1 OAuth\n-----------\n\nThe OAuth 2.0 authorization framework enables a third-party application to\nobtain limited access to an HTTP service, either on behalf of a resource owner\nby orchestrating an approval interaction between the resource owner and the HTTP\nservice, or by allowing the third-party application to obtain access on its\nbehalf.\n\nBecause your app accesses protected (non-public) data, you need an OAuth 2.0\nclient ID. This lets your app request authorization to access your\norganization's location data on behalf of your app's users. Google APIs use the\nOAuth 2.0 protocol for authentication and authorization. Google supports common\nOAuth 2.0 scenarios such as those for web server, installed, and client-side\napplications.\n\nLearn More\n\nWe recommend bundling your ads OAuth requirements when you perform the OAuth\nprocess for connecting your Merchant Center. Learn more about the following:\n\n- [Setting up your Google Cloud Project for your integration](https://developers.google.com/merchant/storebuilder/online/prerequisites#oauth_and_google_cloud_platform_gcp_project_creation)\n- [Review our detailed OAuth section to combine Merchant Center and Ads OAuth requirements](https://developers.google.com/merchant/storebuilder/online/sections/1_1_oauth_account_linking)\n- [OAuth for the Ads API](https://developers.google.com/google-ads/api/docs/oauth/internals)\n\n| **Important:** Ensure you have set the access_type to offline: access tokens periodically expire and become invalid credentials for a related API request. If you requested offline access to the scopes associated with the token, you can refresh an access token without prompting the user for permission (including when the user is not present).\n| **Tip:** We highly recommend that you use the OAuth implementation from one of our [Client Libraries](https://developers.google.com/google-ads/api/docs/client-libs).\n| **Note:** Request your merchant to grant you read and write access to its Google Account the following OAuth scope: `https://www.googleapis.com/auth/adwords`."]]
