since february 2007, i've used two php scripts to query the adwords api TrafficEstimatorService via the @pility (apility) library. apart from upgrading the library to keep pace with each adwords api release, everything works unattended in a weekly cron job.
sometime between march 9 and 15, the TrafficEstimatorService soap requests generated by apility started to fail with an error "HTTP method POST is not supported by this URL", for a request that looks like: POST /api/adwords/v13/TrafficEstimatorService?wsdl HTTP/1.0 Host: adwords.google.com User-Agent: NuSOAP/0.7.2 (1.1) Content-Type: text/xml; charset=UTF-8 SOAPAction: "" Content-Length: 13623 did something change with respect to the way v13 api requests must be made going forward? get vs. post, new hostname, changed authentication method, etc. - or is this perhaps something unique to my environment? is anyone else still using apility to make their requests to v13 of the adwords api? i'm aware that many of the adwords api features are moving to v2009 only next month, but expected v13 to remain available for features that are not yet ported to v2009 like the traffic estimator service. thanks very much if anyone can shed some light on the issue! -sean -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Have you migrated to v200909 yet? The v13 sunset is on April 22, 2010. Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 To unsubscribe from this group, send email to adwords-api+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
