Re: OAUTH_TOKEN_HEADER_INVALID from CustomerSyncService

2011-09-12 Thread Kevin Winter
Hi Michael, Sorry for such a long delay, but I may have a clue. Could you please check when you make the request, what is the exact URL that you are posting the XML to? Does it have any query parameters? If so, please try the request again with none - even if ?wsdl exists at the end, please

Re: OAUTH_TOKEN_HEADER_INVALID from CustomerSyncService

2011-07-20 Thread Michael
Thank you very much for all of your help. Let me know if you hear anything. On Jul 20, 4:26 pm, Kevin Winter wrote: > Hi Michael, >   This one certainly has me stumped.  I've asked the core engineers to > investigate further on this one. > > -Kevin -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=

Re: OAUTH_TOKEN_HEADER_INVALID from CustomerSyncService

2011-07-20 Thread Kevin Winter
Hi Michael, This one certainly has me stumped. I've asked the core engineers to investigate further on this one. -Kevin -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api

Re: OAUTH_TOKEN_HEADER_INVALID from CustomerSyncService

2011-07-20 Thread Michael
Hi Kevin, I'm sorry for the confusion-- when you had asked before, not thinking I had glanced at a function that I'd written to download reports, which also includes an "Authorization" header. The only header I am specifying for the HTTP post is the "SOAPAction" header, which currently has the emp

Re: OAUTH_TOKEN_HEADER_INVALID from CustomerSyncService

2011-07-20 Thread Kevin Winter
Hi, Back to the HTTP header - I'm referring to this header: http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.8 Not to the authToken header: http://code.google.com/apis/adwords/docs/headers.html#authToken The AdWords API uses the Authorization header for OAuth. If you are specify

Re: OAUTH_TOKEN_HEADER_INVALID from CustomerSyncService

2011-07-20 Thread Michael
Hi Kevin, Thank you for your help with the delinquent account issue-- I do appreciate it. Any thoughts on the invalid header? The ClientLogin method is still appropriate for use with CustomerSyncService, correct? I'm not sure what to do with this error, since so far as I can tell the only thing t

Re: OAUTH_TOKEN_HEADER_INVALID from CustomerSyncService

2011-07-20 Thread Kevin Winter
Hi, The ACCOUNT_DELINQUENT usually indicates that the MCC account tied to the Developer Token was not able to be charged for API usage. Could you please go to Billing Summary -> Change account type to 'AdWords API' and check if there are any issues with billing? It's possible the credit card

Re: OAUTH_TOKEN_HEADER_INVALID from CustomerSyncService

2011-07-18 Thread Michael
Hi Kevin, This request went to the production environment (I have tried the same requests in the sandbox environment, with different but still error- laden results). And yes, I am specifying the authorization header in the same fashion I have for the successful requests. I ran the same code again

Re: OAUTH_TOKEN_HEADER_INVALID from CustomerSyncService

2011-07-18 Thread Kevin Winter
Hi, Is this request going to sandbox or production? I'm not able to locate it in the production logs. Are you specifying the HTTP header 'Authorization' ? - Kevin Winter AdWords API Team -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http

OAUTH_TOKEN_HEADER_INVALID from CustomerSyncService

2011-07-15 Thread Michael
Hi, I'm receiving a OAUTH_TOKEN_HEADER_INVALID when I send a request to the CustomerSyncService. The request ID is 0004a8219b8a5cf00ada428f2f477a8c. Here is the request: http://schemas.xmlsoap.org/soap/ envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema";