Search Ads 360 Reporting API เวอร์ชันใหม่พร้อมให้ใช้งานแล้ว เข้าร่วมกลุ่ม Google searchads-api-announcements เพื่อติดตามการปรับปรุงและรุ่นที่กำลังจะเปิดตัว
นำ https://developers.google.com/oauthplayground ออกจาก URI การเปลี่ยนเส้นทางที่ได้รับอนุญาต โปรดทราบว่าคุณต้องปล่อยให้ URI เปลี่ยนเส้นทางอย่างน้อย 1 รายการอยู่ในตำแหน่งเดิม
[null,null,["อัปเดตล่าสุด 2025-08-29 UTC"],[[["\u003cp\u003eThe OAuth2 Playground enables manual creation of OAuth2 tokens for single manager account or Google Ads user access.\u003c/p\u003e\n"],["\u003cp\u003eTo use the OAuth2 Playground, you need a client ID and client secret generated for a web application in the Google API Console.\u003c/p\u003e\n"],["\u003cp\u003eGenerate refresh and access tokens using the OAuth2 Playground by authorizing the Search Ads 360 Reporting API.\u003c/p\u003e\n"],["\u003cp\u003eConfigure your client library using the generated refresh token, client ID, and client secret for Search Ads 360 API access.\u003c/p\u003e\n"],["\u003cp\u003eAfter obtaining the refresh token, remove the OAuth2 Playground from the authorized redirect URIs in your Google API Console project.\u003c/p\u003e\n"]]],["To generate OAuth2 credentials via the OAuth2 Playground, first create a web application client ID and secret in the Google API Console, adding `https://developers.google.com/oauthplayground` as an authorized redirect URI. Next, navigate to the OAuth2 Playground, input your credentials, and select the Search Ads 360 Reporting API scope. Authorize the API, exchange the authorization code for tokens, and copy the refresh token, client ID, and client secret to your client library configuration. Finally, remove the OAuth2 Playground URI from your authorized redirect URIs.\n"],null,["# OAuth Playground\n\nOne option for generating OAuth2 credentials is to use the **OAuth2\nPlayground**. The OAuth2 Playground, in conjunction with the Google Ads API console,\nlets you manually create OAuth2 tokens.\n\nThe OAuth2 Playground is for users who only need to access the accounts for a\n*single* manager account or Google Ads user. If you need to prompt multiple\nusers for credentials, it is likely better to configure a [client library](/search-ads/reporting/client-libraries/client-libraries) for\nOAuth in Search Ads 360.\n\nGet a client ID and client secret\n---------------------------------\n\n| **Warning:** To use the **OAuth2 Playground** , you need to generate a **client\n| ID** for a [web application](/identity/protocols/OAuth2WebServer). This is the *only* type of application that works with the OAuth2 Playground. Refer to [Choose an application\n| type](/google-ads/api/docs/oauth/cloud-project#choose_an_application_type) for more information.\n\nIf you do not have an existing cloud project:\n\n1. Open the [Google API Console\n Credentials page](https://console.cloud.google.com/apis/credentials).\n\n2. From the project drop-down, select an existing project or create a new one.\n\n3. On the Credentials page, select **Create credentials** , then select\n **OAuth client ID**.\n\n4. Under **Application type** , choose **Web application**.\n\n5. Under **Authorized redirect URIs** , add a line with:\n `https://developers.google.com/oauthplayground`\n\n6. Click **Create**.\n\n7. On the Client ID page, take note of the **client ID** and **client secret**.\n You'll need these in the next step.\n\nIf you have an existing cloud project, you can reuse it by setting the\nAuthorized redirect URIs as above.\n\nGenerate tokens\n---------------\n\n| **Warning:** The Search Ads 360 user you're signed in as in your browser determines which accounts you'll be able to access with the OAuth2 credentials you generate. Therefore, you may want to do these steps in an incognito window or when you're not signed in to your Search Ads 360 account, since it's likely that the user whose credentials you want to use isn't the same user you were signed in as when you got the client ID and secret.\n\n1. Go to the [OAuth2\n Playground](https://developers.google.com/oauthplayground/#step1&scopes=https%3A//www.googleapis.com/auth/doubleclicksearch&url=https%3A//&content_type=application/json&http_method=GET&useDefaultOauthCred=checked&oauthEndpointSelect=Google&oauthAuthEndpointValue=https%3A//accounts.google.com/o/oauth2/v2/auth&oauthTokenEndpointValue=https%3A//oauth2.googleapis.com/token&includeCredentials=unchecked&accessTokenType=bearer&autoRefreshToken=unchecked&accessType=offline&forceAprovalPrompt=checked&response_type=code),\n (using this link should pre-populate some key values for you).\n\n2. Click the gear icon\n in the upper right corner and check the box labeled **Use your own OAuth\n credentials** (if it isn't already checked).\n\n3. Make sure that:\n\n - **OAuth flow** is set to **Server-side**.\n - **Access type** is set to **Offline** (this ensures you get a refresh token *and* an access token, instead of just an access token).\n4. Enter the **OAuth2 client ID** and **OAuth2 client secret** you obtained above.\n\n5. In the section labeled **Step 1 - Select \\& authorize APIs** , click **Search Ads 360 Reporting API** from the list and select its scope,\n `https://www.googleapis.com/auth/doubleclicksearch`. Then click **Authorize APIs**:\n\n6. If prompted, sign in to the account to which you want to grant access and\n authorization. Otherwise, confirm that the current user in the top\n right corner is the client or manager account for whom you want to obtain\n credentials.\n\n | If you got your client ID and secret only a few minutes ago, and you get an error such as **Error: redirect_uri_mismatch** , the changes you made may not have propagated. Click the back button in your browser, wait a few minutes, then try clicking **Authorize APIs** again.\n\n \u003cbr /\u003e\n\n | If you get an error that you have not been granted access by the developer and the app is currently being tested, you will need to visit the OAuth consent screen page within your GCP project and do one of the following:\n |\n | \u003cbr /\u003e\n |\n | - Publish the app.\n |\n | - Keep the app in the Testing status, and add yourself as a test user.\n |\n \u003cbr /\u003e\n\n7. A prompt appears indicating your app would like to\n **Manage your Search Ads 360 campaigns** . Click **Accept** to continue.\n\n8. In the tab labeled **Step 2 - Exchange authorization code for tokens** ,\n an **Authorization code** should appear. Click\n **Exchange authorization code for tokens**.\n\n9. If all goes well, the **Refresh token** and **Access token** should be\n filled in for you (you may have to re-expand\n **Step 2 - Exchange authorization code for tokens**):\n\n10. Copy the **Refresh token** into the configuration file for your client\n library of choice, along with the **client ID** and **client secret**.\n\n11. [Configure a client library for OAuth in the Search Ads 360 Reporting API](/search-ads/reporting/client-libraries/client-libraries).\n\nRemove the OAuth2 Playground from your client ID\n------------------------------------------------\n\nNow that you have a **refresh token**, you no longer need the OAuth2 Playground\nto be an authorized redirect URI. To remove it from the list of authorized\nredirect URIs:\n\n1. Go to the [Google API Console Credentials page](https://console.cloud.google.com/apis/credentials).\n\n2. From the project drop-down, select your project.\n\n3. On the Credentials page, click the **client ID name** to edit.\n\n4. Remove `https://developers.google.com/oauthplayground` from the **Authorized\n redirect URIs** . Note that you must leave at least *one* redirect URI in\n place.\n\n5. Click **Save**."]]
ที่มุมขวาบน แล้วเลือกช่องที่ระบุว่าใช้ข้อมูลเข้าสู่ระบบ OAuth ของคุณเอง (หากยังไม่ได้เลือก)
