Thanks - that did it. I kept interpreting header as HTTP header.
Putting it in the SOAP header worked.
Still would be nice to eliminate the need for it when getting field
metadata.
On Friday, October 31, 2014 10:26:55 AM UTC-4, Anash P. Oommen (AdWords API
Team) wrote:
Hi Chris,
From the
Hi Chris,
From the logs, it looks like you are sending clientCustomerId in the HTTP
header.
content-type=[text/xml; charset=utf-8]
connection=[Keep-Alive]
Host=[adwords.google.com]
Content-Length=[704]
developerToken=[**],
Authorization=[Bearer **]
clientCustomerId=[]
?xml
Hi Chris,
Could you post a request id for a failed request, so I can investigate this
further? It is part of the SOAP response header.
Cheers,
Anash P. Oommen,
AdWords API Advisor.
On Monday, October 27, 2014 8:22:09 PM UTC-4, chris h wrote:
Hi Anash,
Yes, I did add it to the request
Hi Anash,
Here is the full response:
soap:Envelope
xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/;soap:HeaderResponseHeader
Look here how get all fields by report
name
https://github.com/googleads/googleads-python-lib/blob/master/examples/adwords/v201409/reporting/get_report_fields.py
and here how correctly authorizing
Thanks, but I'm not using Python. I need to know what has changed with the
protocol handshake that is causing my existing application to stop working.
On Monday, October 27, 2014 6:52:11 AM UTC-4, Сергей Козловский wrote:
Look here how get all fields by report name
Hi Chris,
in v201409, we made client customer id a required field in all the
services. We have asked the team to relax this requirement for
ReportDefinitionService. Meanwhile, you can work around the issue by
setting the clientCustomerId header in the API calls to
ReportDefinitionService.
Hi Anash,
I did add the clientCustomerId to the header (was mentioned in my original
post) but I still get this error. Does it matter which clientCustomerId is
used?
On Monday, October 27, 2014 1:26:46 PM UTC-4, Anash P. Oommen (AdWords API
Team) wrote:
Hi Chris,
in v201409, we made
Hi Chris,
ReportDefinitionService is a SOAP service, so clientCustomerId goes in the
SOAP RequestHeader header.
Cheers,
Anash
On Monday, October 27, 2014 1:33:57 PM UTC-4, chris h wrote:
Hi Anash,
I did add the clientCustomerId to the header (was mentioned in my original
post) but I still
Hi Anash,
Yes, I did add it to the request header. Can you think of anything else
which could be causing it not to work?
On Monday, October 27, 2014 2:55:40 PM UTC-4, Anash P. Oommen (AdWords API
Team) wrote:
Hi Chris,
ReportDefinitionService is a SOAP service, so clientCustomerId goes in
Am migrating to v201409
Getting error:
AuthenticationError.CLIENT_CUSTOMER_ID_IS_REQUIRED
when calling getReportFields
Reading this:
https://developers.google.com/adwords/api/docs/reference/v201409/ReportDefinitionService
I find in errors section:
CLIENT_CUSTOMER_ID_IS_REQUIRED Client
11 matches
Mail list logo
