my request for the offline access code was thus:
'scope' => 'https://adwords.google.com/api/adwords/', // this
was already part of my code before your comment
'redirect_uri' =>
'http://inside.dealerinnovation.com/ppc/oauth2callback.php',
'response_type' => 'code',
'client_id' => $oauth2_client_id,
'access_type' => 'offline',
'approval_prompt' => 'force',
my request for the refresh token was thus:
'scope' => 'https://adwords.google.com/api/adwords/', // I added this
based on your comment
'client_id' => $oauth2_client_id,
'client_secret' => $oauth2_client_secret,
'redirect_uri' =>
'http://inside.dealerinnovation.com/ppc/oauth2callback.php',
'code' => $oauth2_offline_code, // the return from the previous
request
'grant_type' => 'authorization_code',
my request for the access token was thus:
'scope' => 'https://adwords.google.com/api/adwords/', // I
added this based on your comment
'client_id' => $oauth2_client_id,
'client_secret' => $oauth2_client_secret,
'refresh_token' => $oauth2_refresh_token, // the return
from the previous request
'grant_type' => 'refresh_token',
these three operations seemed to yield reasonable results with no errors
my request for the actual report (more details in the screenshot in my
previous post) was thus:
'Authorization' => "Bearer $oauth2_access_token", // the return
from the previous request
'developerToken' => $google_dev_token,
'clientCustomerId' => $client_id, // not the same as my MMC
client id, which I used in the previous requests
'returnMoneyInMicros' => 'true',
'Content-type' => 'application/x-www-form-urlencoded',
that returned the NOT_ADS_USER error seen my in screenshot (I added the
scope lines and re-ran the tests just now, with the same result).
On Monday, March 31, 2014 3:04:52 AM UTC-7, Danial Klimkin wrote:
>
> Hello,
>
>
> Please see this guide for more details:
>
>
> https://developers.google.com/adwords/api/docs/guides/authentication#scope
>
>
> -Danial, AdWords API Team.
>
>
> On Sunday, March 30, 2014 10:10:58 PM UTC+4, [email protected]:
>>
>>
>>
>> On Wednesday, August 7, 2013 3:04:44 AM UTC-7, Danial Klimkin wrote:
>>>
>>>
>>> Make sure you use the correct ClientID and secret and the scope is valid
>>> for AdWords. You may want to try to generate an access token with one of
>>> our libs and try if it works within your app first.
>>>
>>
>> How do I make sure the scope is valid for AdWords? I tried the same
>> developers console where I set up the client secret/callback/etc so that I
>> could get the token to get the refresh token to get the auth tokens, but
>> that console makes no mention of AdWords anywhere, even on the big list of
>> APIs I could enable/disable...
>>
>>
>>
>
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
You received this message because you are subscribed to the Google
Groups "AdWords 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 Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
