You'd have to confirm with the ToS team to verify compliance, but 
technically speaking, it is possible to generate multiple sets of access 
tokens, refresh tokens, etc., using the same developer token, so you'd only 
be using one developer token if you took that approach.

On Wednesday, October 23, 2013 5:02:13 AM UTC-4, Subrata Sarkar wrote:
>
> Hello,
>
> I have just gone through updated Terms published by Google  
> https://developers.google.com/adwords/api/docs/terms and have some 
> confusions amongst which the major one is using multiple Adwrods client 
> login credentials and OAuth2 credentials (for Analytic) in my application's 
> database. Please read below.
>
> I am developing an application which will use Google Adwords API and 
> Google Analytic API. The objective of the application is to allow users 
> signe up and add thier own Adwords credential (client login) which would be 
> stored in the database. At any point they can login to the site and fetch 
> data using API library (in my case I am using .NET client library) and 
> prepae custom reports for Campaigns, Adgroups, Ads, Keywords etc. using the 
> raw data. All raw data would be sotored in system's database as well. Once 
> the data is stored a report can be generated at any time by supplying a 
> Start and an End date.
>
> There could be many such Adwords credentials stored in the database. For 
> Google Analytic API, I have planned to use OAuth2, whcih will access an app 
> and after authentication process is complete an Aceess_Token, Refresh_Token 
> and an Expiry time are bing recorded in the database. Again like Adwords 
> credential, there could be many OAuth2 credential stored in database as 
> well.
>
> I am concerened of the following mainly (may be more!):
>
> Permission to Use. You may use the AdWords API only in accordance with the 
> terms and conditions of this AdWords API Agreement. You must use the same 
> Developer Token, and only one Developer Token, at all times. You may only 
> apply for a Developer Token for the sole purpose of using it in AdWords API 
> Clients you have developed, as approved by Google. You may not use any 
> Third Party Developer Token in an AdWords API Client unless permitted in 
> writing by Google.
>
> Please let me know if this violates anything as far as terms of usage are 
> concerned.
>
> Subrata
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.

Reply via email to