Closed ylluminate closed 12 years ago
Good morning, and thank you for the feedback. We're constantly improving our API feature set as well as the functionality of our client libraries, and that's all a result of the feedback we get from our developer community. If you have any specific observations you'd like to offer, we'd be happy to hear what you have to say.
I also highly recommend contacting API support directly via api@aweber.com, so your questions can be answered in the most efficient and timely manner.
Thanks, other's are having similarly abysmal experiences with the AWeber API. For example, a person at SO says: "The AWeber docs are mindbogglingly poor. I don't even understand why they have an API: your app and your keys have nothing to do with accessing any user's data. They just prove to AWeber that yes, you are a developer.... but so what?..."
We'll try to write to the API team there, but be warned, others are having these experiences and it is generally and publicly considered a very bad thing presently.
Thanks again for your feedback and for working with us directly to resolve your technical issue. We're taking note of what you are reporting here and will factor what we learn into our next round of improvements on the API and its documentation.
I would highly suggest that you look at https://github.com/amro/gibbon for a good example of how an API should be modeled and wrapped. MailChimp has done a very good job and while contemplating a switch over to AWeber the API has been an enormous deterrent for us.