Hello, You are absolutely right in not wanting to share your developer token with a third party. Developer tokens should be kept secure <https://developers.google.com/adwords/api/docs/guides/start#developer_token>. That's why we ask that people remove developer tokens out of output when posting to the forum. Please have that person apply for a developer token. When applying for a developer token, he'll have to explain why he needs the developer token. Our compliance team goes over that information when granting the developer token to make sure that the intended use is correct.
Cheers, Nadine, AdWords API Team On Friday, September 18, 2015 at 3:48:07 AM UTC-4, helpplease...@gmail.com wrote: > > Thanks Brett, > > No, he's not an employee and I only know him over email as I was testing > the tool and wanted some data for 4 other countries, which is where the API > resquest came from. I've questioned this a bit further with him and he just > needs me to autorise his app with the API key. I don't know how much access > that gives him to be honest. I did a whole lot more research today. I am > flagging the following from Google: > > *Scraping TargetingIdeaService or TrafficEstimatorService* > > *The TargetingIdeaService (TIS) and TrafficEstimatorService (TES) help > advertisers and agencies generate keywords programmatically and optimize > their AdWords keyword and bidding strategies. You may not collect data from > the TIS or TES for any purposes other than creating or managing AdWords > campaigns. If you're an advertising agency or an Independent AdWords > Developer and would like to give your clients access to TIS or TES data > through your external API tool, you need to meet all of the Required > Minimum Functionality requirements (campaign creation, management, and > reporting).* > > *Allowing automated use of your API token* > > You can't allow agencies, end-advertisers, or other third parties to use > your AdWords API token (or your own API) in a way that would allow those > third parties to avoid applying for their own AdWords API token. Any > automatic or programmatic use of AdWords by agencies or end-advertiser > clients requires them to use their own AdWords API token; you cannot > provide indirect access to your API token via APIs that you provide. > > I do not know how many queries are intended but it is to get access to the > TrafficEstimatorService. This is only used by tools requiring keyword > suggestions or traffic to help facilitate the creation and management of > AdWords campaigns, which this tool is not intending to do. > > > > On Thursday, September 17, 2015 at 11:57:16 PM UTC+10, Brett Baggott wrote: >> >> There are provisions for allowing others access to your API credentials >> but this is usually done for employees of your company. It doesn't sound >> like that's what's going on here. I think your instincts on this are right. >> >> Having said that, were he an employee or contractor, and I wanted to do >> what you are talking about, it can be done and still limit access. I >> wouldn't do it for anyone that wasn't in my direct employ, but here's an >> example of a good way to limit access: >> >> https://groups.google.com/forum/#!topic/adwords-api/vIhAHaZ7n7s >> >> >> On Thursday, September 17, 2015 at 7:25:08 AM UTC-5, helppl...@gmail.com >> wrote: >>> >>> Hi there, >>> >>> >>> >>> I have a question I'd just like to run by you which I need clarity on - >>> I know a guy who wants to use my access to the AdWords API to help populate >>> results in a tool he's building. To do so I need to apply for the token >>> through my MCC account, however, after researching a bit it doesn't sound >>> like a good idea. >>> >>> >>> >>> 1. The tool won't be built to aide in PPC/AdWords/Campaign management. >>> It is for keyword data/search volume. This in itself seems to fly in the >>> face of the T&C's. >>> >>> >>> >>> 2. I also do not think it common practice to let developers 'borrow' the >>> token to begin with. Should he not apply for his own? >>> >>> >>> >>> 3. There's a lot of guidelines that Google has in its' documentation >>> about checks on the use of the API and I wouldn't have any transparency in >>> how my token will be used to ensure the tool complies. I know the likes of >>> Moz and Raven had theirs revoked at one point. I also read that their could >>> be non-compliant fees. >>> >>> >>> >>> 4. There's no way I would want him to be able to access the many >>> accounts I manage through my MCC. >>> >>> >>> >>> Anyway, I think I'm on the right track here and will keep reading, but >>> would love to hear other opinions. >>> >>> >>> >>> Thanks >>> >> -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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. Visit this group at http://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/b1a33a85-f740-41c9-9037-6b749b96bb59%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
