Hello Vladyslav,
I see the production MCC account is missing T&T (terms and conditions not signed). Normally, it's available as the last step of the billing setup process. Please check with the tokens review team to sign T&C manually. -Danial, AdWords API Team. On Tuesday, September 9, 2014 2:27:42 PM UTC+4, Vladyslav wrote: > > I've read all the threads about this error without success. I think I've > done all I could do myself. > > I went through the Common Errors guide > <https://developers.google.com/adwords/api/docs/common-errors#QuotaCheckError> > : > *Did you enter your billing information?* > *Yes. *I can see billing information in my *Production MCC* account. I've > seen AdWords API T&C and accepted it. > *Are you having trouble entering your billing information?* > *No. *I've added credit card successfully. It was charged for a few cents > (like when you link a card to Google Play) from Google Inc. So I'm sure the > card was added successfully. > *Are you using an unapproved developer token against a production AdWords > account?* > *No.* I'm using developer token from *Production MCC *against the *test > client account* under *Test MCC*. > *Still receiving INCOMPLETE_SIGNUP error after completing the above steps?* > *Yes! *I've submitted a form to AdWords API Compliance > <https://services.google.com/fb/forms/apicontact/> and received an answer > with same steps. So the tals way was to use the developer forum. > > > My *Production MCC*: 182-716-2353 > My *Test MCC*: 662-907-7712 > My *Client *under *Test MCC*: 861-475-5602 > > In the Developers Console I've created a "web application" logged in with > the email of my Test MCC. > > When a logged in as *Test MCC *owner account I go to my own web > application and go through OAuth2 flow, grant access to my application. > > Then I setup the client library in my web-server application with: > Developer Token: Developer token from my *Production MCC*. > Client Customer ID: *Client *under *Test MCC* (861-475-5602). > OAuth2 Client ID — From the app in Developers Console as described above. > OAuth2 Client Secret — Secret of the app. > OAuth2 Token: The one from auth flow with Test MCC owner. > > In debug mode I see Authorization header with the right token and SOAP > body contains clientCustomerId. So configs are fine. > > After all I receive INCOMPLETE_SIGNUP with any api request. > > -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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/c889713b-c90e-49c4-8667-95ae14c177cd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
