The reason that the adWords SOAP interface, and the usefulness of the various client libraries in trying to abstract out some of the intricacies of the interface, is because AdWords itself is in fact a complex beast. Some parts are very simple, especially those operations that are GETs, and so I can see your point about SOAP seeming to be overkill. But many operations are not so simple, and I cannot imagine easily implementing them as REST services. What if I want to create 1000 ads - that's one heck of a REST call!
The stated need to be able to more easily build a JavaScript interface using REST rather than SOAP helps put this request in focus, because it distinguishes the desired use of the api from that of the backend production systems that many of us have been building to service large numbers of accounts with large numbers of keywords, ads, etc. If you are building something in JavaScript, then you are probably building more of a query tool. It could end up being an expensive query tool, btw, if it is going to be using the api to get its data all the time (rather than loading data into a database and then querying against it for free as often as you want). The recent announcement of a JavaScript client library might meet your needs in a better fashion - even if there were a REST api that you could call from JS, you'd still have to spend a lot of time programming to it, instead of using the JS client library and leaving the actual interfacing up to the AdWords team. my 2 cents -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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
