Hi, My apologies as your developer console concern is already out of scope for us. However, I would recommend that you access the said page while in a session and logged in as the user (email address) in which you originally created your own OAuth2 crendentials with. You may carefully follow the steps mentioned in this guide <https://developers.google.com/adwords/api/docs/guides/authentication#oauth2_playground> .
Best regards, Peter AdWords API Team On Friday, October 26, 2018 at 7:11:10 PM UTC+8, [email protected] wrote: > > Hi Peter, > > thanks for the quick response. looks like when we are generating the > access key from the playground it is referring to a different client id > than what is defined in the developer console also the response gives a > different refresh token. is there anything we need to do to authorize the > client in the developer console. do we need to publish the OAuth Consent > on the OAuth Consent screen > > On Friday, October 26, 2018 at 12:04:10 PM UTC+5:30, Peter Oliquino > (AdWords API Team) wrote: >> >> Hi, >> >> As long as the refreshToken you specify in your properties file is >> associated to your clientId and clientSecret (in the same file), then, >> generating the access tokens via the client library should not be an issue. >> >> Thanks and regards, >> Peter >> AdWords API Team >> >> On Friday, October 26, 2018 at 12:21:46 PM UTC+8, [email protected] >> wrote: >>> >>> we are trying to generate access token using >>> >>> >>> >>> >>> https://www.googleapis.com/oauth2/v4/token?client_id=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.apps.googleusercontent.com&client_secret=********************&refresh_token=1/0z1VUN_LmxR-wnr67812blTb6F7jHUosQmNe6HsUxtw&grant_type=refresh_token >>> >>> >>> >>> the client id and refresh token is defined in the developer console and >>> using the OAUTH Playground, we are able to generate the access token >>> manually for the required scope. >>> >>> >>> >>> is there anything we need to do with the API call to generate the token >>> using the same refresh token as in the OAUTH Playground >>> >> -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog: https://googleadsdeveloper.blogspot.com/ =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API and Google Ads API Forum" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups "AdWords API and Google Ads API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/7d9f03ce-ea14-43a0-9e17-7fd2d11ab9d1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
