Re: Adhoc report with Oauth2 : looking for Documentation

2014-04-01 Thread Danial Klimkin
Hello,


Normally, NOT_ADS_USER error is produced when you were logged in under a 
wrong user when granted the access. Please log off from any google account 
in the browser and re-try OAuth2 flow.

Make sure to log in as your AdWords user before granting the access.


-Danial, AdWords API Team.


On Monday, March 31, 2014 8:37:20 PM UTC+4, goo...@rndinteractive.com wrote:

 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, goo...@rndinteractive.comwrote:



 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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
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 adwords-api+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Adhoc report with Oauth2 : looking for Documentation

2014-04-01 Thread goo...@rndinteractive.com
so instead of asking if I was an authorized representative of 
$google_username, it was asking if $google_username could access MY stuff, 
and since I was logged in (in a completely different browser session from 
the day before) to my personal gmail account, it was asking about my 
personal adwords account (which doesn't exist).

when I logged out of gmail, and ran through the 'get offline token' part 
again... it asked me to log in. I logged in as the account owning the 
adwords account... and, presto changeo, no more 'NOT ADS USER' - the 
reports retrieve just fine.

wow. all that time hunting for a bug, and what I needed to do was look in 
the upper right of the permissions screen (I have a wide monitor, so it was 
way out of the field of focus) to see it showed MY username, and not the 
adwords user for work. Thanks!

On Tuesday, April 1, 2014 4:21:31 AM UTC-7, Danial Klimkin wrote:

 Hello,


 Normally, NOT_ADS_USER error is produced when you were logged in under a 
 wrong user when granted the access. Please log off from any google account 
 in the browser and re-try OAuth2 flow.

 Make sure to log in as your AdWords user before granting the access.


 -Danial, AdWords API Team.


 On Monday, March 31, 2014 8:37:20 PM UTC+4, goo...@rndinteractive.comwrote:

 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, goo...@rndinteractive.comwrote:



 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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
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 

Re: Adhoc report with Oauth2 : looking for Documentation

2014-03-31 Thread Danial Klimkin
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, goo...@rndinteractive.com 
wrote:



 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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
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 adwords-api+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Adhoc report with Oauth2 : looking for Documentation

2014-03-31 Thread goo...@rndinteractive.com
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, goo...@rndinteractive.comwrote:



 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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
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 adwords-api+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Adhoc report with Oauth2 : looking for Documentation

2014-03-30 Thread goo...@rndinteractive.com


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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
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 adwords-api+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Adhoc report with Oauth2 : looking for Documentation

2013-08-07 Thread Jani Link
I don't use any of the libraries on the library page.  I am using NodeJs. 
 I am trying to make a direct http post to get Adhoc reports with the 
accessToken I receive from Oauth using passport-google-oauth npm and the 
adwords api scope.  I set the Authorization header to Bearer 
[accessToken], but I am still receiving an invalid oauth token error. 
 What is the correct method for making this post, there are no explicit 
instructions for oauth 2.


On Wednesday, July 17, 2013 4:58:11 AM UTC-4, Danial Klimkin wrote:

 Hello,


 Did you see this guide? Please let us know if you need more details.

   https://code.google.com/p/google-api-adwords-php/wiki/OAuth2


 -Danial, AdWords API Team.


 On Tuesday, July 16, 2013 6:47:02 PM UTC+4, SylvainFR wrote:

 Thanks for your answer.

 We use PHP library : https://code.google.com/p/google-api-adwords-php/

 Best regards

 Le vendredi 12 juillet 2013 13:10:25 UTC+2, SylvainFR a écrit :

 Hello,

 We work on Adhoc report.

 With Clientlogin, no problem, all works fine.

 We tried with Oauth2 but we did not find the way to get report with this 
 (recommanded!) method.

 Is that possible to get documentation or step-by-step guide about 
 getting report with Oauth2 identification ?

 Best regards



-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups AdWords API Forum group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
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 adwords-api+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




Re: Adhoc report with Oauth2 : looking for Documentation

2013-08-07 Thread Danial Klimkin
Hello Jani,


The method seems correct but it looks like the access token is not valid. 
As you generate it with your code we are not able to help here.

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.


-Danial, AdWords API Team.


On Sunday, August 4, 2013 6:06:59 AM UTC+4, Jani Link wrote:

 I don't use any of the libraries on the library page.  I am using NodeJs. 
  I am trying to make a direct http post to get Adhoc reports with the 
 accessToken I receive from Oauth using passport-google-oauth npm and the 
 adwords api scope.  I set the Authorization header to Bearer 
 [accessToken], but I am still receiving an invalid oauth token error. 
  What is the correct method for making this post, there are no explicit 
 instructions for oauth 2.


 On Wednesday, July 17, 2013 4:58:11 AM UTC-4, Danial Klimkin wrote:

 Hello,


 Did you see this guide? Please let us know if you need more details.

   https://code.google.com/p/google-api-adwords-php/wiki/OAuth2


 -Danial, AdWords API Team.


 On Tuesday, July 16, 2013 6:47:02 PM UTC+4, SylvainFR wrote:

 Thanks for your answer.

 We use PHP library : https://code.google.com/p/google-api-adwords-php/

 Best regards

 Le vendredi 12 juillet 2013 13:10:25 UTC+2, SylvainFR a écrit :

 Hello,

 We work on Adhoc report.

 With Clientlogin, no problem, all works fine.

 We tried with Oauth2 but we did not find the way to get report with 
 this (recommanded!) method.

 Is that possible to get documentation or step-by-step guide about 
 getting report with Oauth2 identification ?

 Best regards



-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups AdWords API Forum group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
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 adwords-api+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




Re: Adhoc report with Oauth2 : looking for Documentation

2013-07-17 Thread Danial Klimkin
Hello,


Did you see this guide? Please let us know if you need more details.

  https://code.google.com/p/google-api-adwords-php/wiki/OAuth2


-Danial, AdWords API Team.


On Tuesday, July 16, 2013 6:47:02 PM UTC+4, SylvainFR wrote:

 Thanks for your answer.

 We use PHP library : https://code.google.com/p/google-api-adwords-php/

 Best regards

 Le vendredi 12 juillet 2013 13:10:25 UTC+2, SylvainFR a écrit :

 Hello,

 We work on Adhoc report.

 With Clientlogin, no problem, all works fine.

 We tried with Oauth2 but we did not find the way to get report with this 
 (recommanded!) method.

 Is that possible to get documentation or step-by-step guide about getting 
 report with Oauth2 identification ?

 Best regards



-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups AdWords API Forum group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
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 adwords-api+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




Re: Adhoc report with Oauth2 : looking for Documentation

2013-07-16 Thread Danial Klimkin
Hello,


What language are you using? Do you use any of our client libraries?

  https://developers.google.com/adwords/api/docs/clientlibraries


-Danial, AdWords API Team.


On Friday, July 12, 2013 3:10:25 PM UTC+4, SylvainFR wrote:

 Hello,

 We work on Adhoc report.

 With Clientlogin, no problem, all works fine.

 We tried with Oauth2 but we did not find the way to get report with this 
 (recommanded!) method.

 Is that possible to get documentation or step-by-step guide about getting 
 report with Oauth2 identification ?

 Best regards


-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups AdWords API Forum group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
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 adwords-api+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




Re: Adhoc report with Oauth2 : looking for Documentation

2013-07-16 Thread SylvainFR
Thanks for your answer.

We use PHP library : https://code.google.com/p/google-api-adwords-php/

Best regards

Le vendredi 12 juillet 2013 13:10:25 UTC+2, SylvainFR a écrit :

 Hello,

 We work on Adhoc report.

 With Clientlogin, no problem, all works fine.

 We tried with Oauth2 but we did not find the way to get report with this 
 (recommanded!) method.

 Is that possible to get documentation or step-by-step guide about getting 
 report with Oauth2 identification ?

 Best regards


-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups AdWords API Forum group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
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 adwords-api+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




Adhoc report with Oauth2 : looking for Documentation

2013-07-12 Thread SylvainFR
Hello,

We work on Adhoc report.

With Clientlogin, no problem, all works fine.

We tried with Oauth2 but we did not find the way to get report with this 
(recommanded!) method.

Is that possible to get documentation or step-by-step guide about getting 
report with Oauth2 identification ?

Best regards

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups AdWords API Forum group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
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 adwords-api+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.