Looks like I responded to your email, not to the thread. Here's the reply I tried to post a week back.
Hi Robert, I see you had a frustrating experience signing up for the API, so here's the explanation: 1. You need an AdWords account (looks like you already have one, email #1) 2. You need an MCC account, since AdWords API tokens are available only through an MCC account (email #2). You need to sign up for the developer token in the MCC account. Ideally, you should have just done this on your company's top MCC account. Token review process can take a while, so it doesn't benefit you to signup for a token in your personal account, then get it approved, then much later, repeat the exercise for your company's MCC. If you can, get the token approved, and transfer the ownership of this MCC to your company. If you want to wait until the token application gets reviewed and approved, then you don't need to create a test account. If that isn't the case, you would need a test MCC account and AdWords account to develop your application. 1. Create a test MCC account (looks like you did this step - email #3) 2. Create a test advertiser account (looks like you did this too - email #4) The difference between regular accounts and test accounts is that test accounts are closed, and hence nothing you create in those accounts would ever serve. So your personal AdWords account (email #1) is a production account, email #4 is a test account. You cannot link email #4 under email #1, since one is production account, and the other is test account. Once you have created the test account, you can make calls against it, even when the developer token is being reviewed. You need to use the developer token from email #2 + credentials of email #3 or email #4 to do this. Does this help? Cheers, Anash P. Oommen, AdWords API Advisor. On Friday, May 30, 2014 1:20:46 PM UTC-4, Anash P. Oommen (AdWords API Team) wrote: > > Hi Robert, > > I'm pretty sure I responded to this thread, let me check. > > Anash > > On Wednesday, May 28, 2014 5:21:16 PM UTC-4, [email protected] wrote: >> >> Still waiting on a response to this... >> >> Although I did take a break last week while waiting for this message to >> even post, and was able to sign-up for, develop, test, and implement >> automated cost reports using the Bing Ads API. >> While the Bing Ads API dev token issuing was not completely straight >> forward, I was able to get a working one in less than a day. I'm still >> trying after a week for the Google one. >> >> Back to this issue. The problem really appears as though I have to agree >> to some other T&C based on the error I receive, and the red warning under >> the accounts setup: >> https://developers.google.com/adwords/api/docs/test-accounts >> >> What is the DIRECT LINK for this T&C? >> I have entered my billing info (and agreed to some T&C just to do that!) >> ---------------------------- >> >> My next question has to do with developer console projects. >> Do I need to create ONE project for development (using the dev-mcc >> account), and a SECOND project for production (using the prod-mcc account)? >> >> -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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.
