<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Aweber Needs an API</title>
	<atom:link href="http://www.nicktemple.com/2008/239/aweber-needs-an-api.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.nicktemple.com/2008/239/aweber-needs-an-api.html</link>
	<description>Personal Development for Entrepreneurs</description>
	<lastBuildDate>Thu, 15 Jul 2010 13:03:55 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Nick</title>
		<link>http://www.nicktemple.com/2008/239/aweber-needs-an-api.html/comment-page-1#comment-85879</link>
		<dc:creator>Nick</dc:creator>
		<pubDate>Sat, 26 Jun 2010 02:10:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.nicktemple.com/?p=239#comment-85879</guid>
		<description>Yes, it is very disappointing to see a &quot;premiere&quot; autoreponder contininue suffer in such an obvious area?

Simply having the system be able to POST contact information (even if that did require a a seperate confirmation) would allow many apps to use AWeber that currently either can&#039;t or get hung up in the complexity of the &quot;email parser&quot;.

iContact&#039;s email system is very robust, and their API is sweet ... though setting up apps is very complicated, and the inability to change the confirmation link URL is a serious problem - but the API is sound enough that you can write your own app, if necessary.</description>
		<content:encoded><![CDATA[<p>Yes, it is very disappointing to see a &#8220;premiere&#8221; autoreponder contininue suffer in such an obvious area?</p>
<p>Simply having the system be able to POST contact information (even if that did require a a seperate confirmation) would allow many apps to use AWeber that currently either can&#8217;t or get hung up in the complexity of the &#8220;email parser&#8221;.</p>
<p>iContact&#8217;s email system is very robust, and their API is sweet &#8230; though setting up apps is very complicated, and the inability to change the confirmation link URL is a serious problem &#8211; but the API is sound enough that you can write your own app, if necessary.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Phipps</title>
		<link>http://www.nicktemple.com/2008/239/aweber-needs-an-api.html/comment-page-1#comment-85668</link>
		<dc:creator>Michael Phipps</dc:creator>
		<pubDate>Wed, 05 May 2010 00:23:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.nicktemple.com/?p=239#comment-85668</guid>
		<description>I&#039;m thinking about putting together an API document that would outline each function I want the API to have, what it does, and how it responds.

I think the nicest thing about Aweber is it&#039;s simplicity.  Clients can catch on to how it works pretty quickly, compared to iContact or MailChimp.

I think instead of asking &quot;where&#039;s the API&quot;, documenting the features that you specifically want. (saying &#039;everything&#039; is generally not helpful to programming folk) and sending it into Aweber might get results.</description>
		<content:encoded><![CDATA[<p>I&#8217;m thinking about putting together an API document that would outline each function I want the API to have, what it does, and how it responds.</p>
<p>I think the nicest thing about Aweber is it&#8217;s simplicity.  Clients can catch on to how it works pretty quickly, compared to iContact or MailChimp.</p>
<p>I think instead of asking &#8220;where&#8217;s the API&#8221;, documenting the features that you specifically want. (saying &#8216;everything&#8217; is generally not helpful to programming folk) and sending it into Aweber might get results.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Liz</title>
		<link>http://www.nicktemple.com/2008/239/aweber-needs-an-api.html/comment-page-1#comment-85556</link>
		<dc:creator>Liz</dc:creator>
		<pubDate>Mon, 19 Apr 2010 20:14:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.nicktemple.com/?p=239#comment-85556</guid>
		<description>This thread is quite old now, and Justin from aweber said over 18 months ago they were considering an api.  How long does this take? I spoke to aweber support and they said there still was no api, but that we might see one by the end of this year (2010). Any progress? As for what we want to see. That is easy. Basically everything you can do via the aweber UI.
Liz</description>
		<content:encoded><![CDATA[<p>This thread is quite old now, and Justin from aweber said over 18 months ago they were considering an api.  How long does this take? I spoke to aweber support and they said there still was no api, but that we might see one by the end of this year (2010). Any progress? As for what we want to see. That is easy. Basically everything you can do via the aweber UI.<br />
Liz</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Denise</title>
		<link>http://www.nicktemple.com/2008/239/aweber-needs-an-api.html/comment-page-1#comment-83341</link>
		<dc:creator>Denise</dc:creator>
		<pubDate>Wed, 06 May 2009 04:21:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.nicktemple.com/?p=239#comment-83341</guid>
		<description>Can anyone help me with info on how to design a nice looking aweber opt in form for a squeeze page? In other words, I don&#039;t want the kind I&#039;ve seen that had no graphic design to them. 
Thanks.</description>
		<content:encoded><![CDATA[<p>Can anyone help me with info on how to design a nice looking aweber opt in form for a squeeze page? In other words, I don&#8217;t want the kind I&#8217;ve seen that had no graphic design to them.<br />
Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick</title>
		<link>http://www.nicktemple.com/2008/239/aweber-needs-an-api.html/comment-page-1#comment-82424</link>
		<dc:creator>Nick</dc:creator>
		<pubDate>Sun, 05 Apr 2009 21:14:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.nicktemple.com/?p=239#comment-82424</guid>
		<description>Andy,

Aweber does have a way to &quot;post&quot; variables to the thank you page, which is probably what you are referring to.

And that can work if your designing a system from scratch, and if you are willing to make the auto-responder signup the most important (first piece) of the process.

For most systems ... I develop for Joomla, Wordpress and a few other CMS&#039;s, that&#039;s just impractical to do.

Not to mention making your customers leave your sight during the signup process, even if it&#039;s only for a moment.

Aweber does not, to the best of my knowledge, have a callback function similar to Paypal [IPN]. The downside of a systems is that the customer / potential customer must go all the way through the process before you are notified: in many cases, what you actually want, is their contact information _before_ they start checkout, so that you can contact them and &quot;save the sale&quot; if they drop out partway through.

Both &lt;a href=&quot;http://www.intellispire.com/try/getresponse&quot; rel=&quot;nofollow&quot;&gt;GetResponse&lt;/a&gt; and &lt;a href=&quot;http://www.intellispire.com/try/icontact&quot; rel=&quot;nofollow&quot;&gt;iContact&lt;/a&gt; have elegent, API-based solutions to this problem. Aweber just seems to be falling behind.</description>
		<content:encoded><![CDATA[<p>Andy,</p>
<p>Aweber does have a way to &#8220;post&#8221; variables to the thank you page, which is probably what you are referring to.</p>
<p>And that can work if your designing a system from scratch, and if you are willing to make the auto-responder signup the most important (first piece) of the process.</p>
<p>For most systems &#8230; I develop for Joomla, WordPress and a few other CMS&#8217;s, that&#8217;s just impractical to do.</p>
<p>Not to mention making your customers leave your sight during the signup process, even if it&#8217;s only for a moment.</p>
<p>Aweber does not, to the best of my knowledge, have a callback function similar to Paypal [IPN]. The downside of a systems is that the customer / potential customer must go all the way through the process before you are notified: in many cases, what you actually want, is their contact information _before_ they start checkout, so that you can contact them and &#8220;save the sale&#8221; if they drop out partway through.</p>
<p>Both <a href="http://www.intellispire.com/try/getresponse" rel="nofollow">GetResponse</a> and <a href="http://www.intellispire.com/try/icontact" rel="nofollow">iContact</a> have elegent, API-based solutions to this problem. Aweber just seems to be falling behind.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Beard</title>
		<link>http://www.nicktemple.com/2008/239/aweber-needs-an-api.html/comment-page-1#comment-82397</link>
		<dc:creator>Andy Beard</dc:creator>
		<pubDate>Sat, 04 Apr 2009 21:48:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.nicktemple.com/?p=239#comment-82397</guid>
		<description>Although not quite the same, and more complicated to implement if you already have something done for other platforms, a &quot;push&quot; system such as implemented by Clickbank, where they send data back to a form on your own site is a workable alternative.</description>
		<content:encoded><![CDATA[<p>Although not quite the same, and more complicated to implement if you already have something done for other platforms, a &#8220;push&#8221; system such as implemented by Clickbank, where they send data back to a form on your own site is a workable alternative.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick</title>
		<link>http://www.nicktemple.com/2008/239/aweber-needs-an-api.html/comment-page-1#comment-82032</link>
		<dc:creator>Nick</dc:creator>
		<pubDate>Sat, 21 Feb 2009 21:15:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.nicktemple.com/?p=239#comment-82032</guid>
		<description>George: thanks for the comment. As soon as I get systems for the rest of the AR&#039;s in place (1SC / CommerceStore.com, etc) I do plan on supporting other CMS&#039;s.

Nico: Yes, a lot of integrations would be possible of Aweber would just allow a form POST to their signup forms, or have a alternate (lighter weight) API for signing people up. As it is now, your only option is the email parser, which seems to be stable over the last few weeks, anyway, but is always at the mercy of filters and email deliverability issues from your ISP (which is why most people use aweber in the first place!)</description>
		<content:encoded><![CDATA[<p>George: thanks for the comment. As soon as I get systems for the rest of the AR&#8217;s in place (1SC / CommerceStore.com, etc) I do plan on supporting other CMS&#8217;s.</p>
<p>Nico: Yes, a lot of integrations would be possible of Aweber would just allow a form POST to their signup forms, or have a alternate (lighter weight) API for signing people up. As it is now, your only option is the email parser, which seems to be stable over the last few weeks, anyway, but is always at the mercy of filters and email deliverability issues from your ISP (which is why most people use aweber in the first place!)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nico Granelli</title>
		<link>http://www.nicktemple.com/2008/239/aweber-needs-an-api.html/comment-page-1#comment-82030</link>
		<dc:creator>Nico Granelli</dc:creator>
		<pubDate>Sat, 21 Feb 2009 11:26:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.nicktemple.com/?p=239#comment-82030</guid>
		<description>Integrating aweber with highrise would be great, and very easy with an API</description>
		<content:encoded><![CDATA[<p>Integrating aweber with highrise would be great, and very easy with an API</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: George Snyder</title>
		<link>http://www.nicktemple.com/2008/239/aweber-needs-an-api.html/comment-page-1#comment-82020</link>
		<dc:creator>George Snyder</dc:creator>
		<pubDate>Sun, 15 Feb 2009 17:58:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.nicktemple.com/?p=239#comment-82020</guid>
		<description>Would be nice if you ported your nice apps over to wordpress, I would certainly be interested in them. Keep up the good work, atb George</description>
		<content:encoded><![CDATA[<p>Would be nice if you ported your nice apps over to wordpress, I would certainly be interested in them. Keep up the good work, atb George</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: GetResponse Review - Autoresponder User Reviews</title>
		<link>http://www.nicktemple.com/2008/239/aweber-needs-an-api.html/comment-page-1#comment-82000</link>
		<dc:creator>GetResponse Review - Autoresponder User Reviews</dc:creator>
		<pubDate>Thu, 29 Jan 2009 19:24:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.nicktemple.com/?p=239#comment-82000</guid>
		<description>API availability is not the only shortcoming of aweber.  getresponse is implementing a pricing structer that TRUMPS aweber.  500 subscribers for 20$ a month with AWeber versus 10,000 subscribers for 20$ a month with GetResponse.

i smell the death of aweber.</description>
		<content:encoded><![CDATA[<p>API availability is not the only shortcoming of aweber.  getresponse is implementing a pricing structer that TRUMPS aweber.  500 subscribers for 20$ a month with AWeber versus 10,000 subscribers for 20$ a month with GetResponse.</p>
<p>i smell the death of aweber.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
