Re: INVALID_OAUTH_TOKEN_FOR_EMAIL

2015-04-07 Thread Josh Radcliff (AdWords API Team)
Hi Sergey, You are setting the *OAuthInfo* object correctly, but your refresh token was created using the old, deprecated scope of *https://adwords.google.com/api/adwords/*. You could try setting *oAuthInfo.setHttpReq

Re: INVALID_OAUTH_TOKEN_FOR_EMAIL

2015-04-07 Thread Sergey Petrov
Hi Josh ! Great thanks for the answer, I think you find the problem point, because when I verify accessToken I get a many scopes but not that what I need: { "issued_to": "*.apps.googleusercontent.com", "audience": "*.apps.googleusercontent.com", "user_id": "1076**", "sco

Re: INVALID_OAUTH_TOKEN_FOR_EMAIL

2015-04-06 Thread Josh Radcliff (AdWords API Team)
Hi Sergey, As a first step, please generate a new access token from your refresh token and then check its information by appending it to the end of the following URL: https://www.googleapis.com/oauth2/v1/tokeninfo?access_token= That should return something like this: { "issued_to": "12345...

Re: INVALID_OAUTH_TOKEN_FOR_EMAIL

2015-04-06 Thread Sergey Petrov
Hi Josh ! I have same problem like Sandeep had before, but I can swear access token is actual, could you please take a look ? Request: http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>

Re: INVALID_OAUTH_TOKEN_FOR_EMAIL

2015-04-01 Thread Josh Radcliff (AdWords API Team)
Hi Sandeep, That error means that the access token you included in PlacesLocationFeedData.oAuthInfo is revoked or expired or is not for the user you specified in the emailAddress at

INVALID_OAUTH_TOKEN_FOR_EMAIL

2015-04-01 Thread cvit sandeep
Hi Adwords Team, When trying to implement AddGoogleMyBusinessLocationExtensions we get the following error. [FeedError.INVALID_OAUTH_TOKEN_FOR_EMAIL @ operations[0].operand.systemFeedGenerationData.oAuthInfo; trigger:'Invalid token'] We already checked the email is matching with Adword UI. C