<?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: Now We&#8217;re a Platform</title>
	<atom:link href="http://www.freshbooks.com/blog/2006/08/22/now-were-a-platform/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.freshbooks.com/blog/2006/08/22/now-were-a-platform/</link>
	<description>A blog about our thoughts on entrepreneurship, teamwork, our services, the Web and anything we find interesting.</description>
	<lastBuildDate>Wed, 17 Mar 2010 22:26:59 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: FreshBooks Reaches One Hundred Thousand Users</title>
		<link>http://www.freshbooks.com/blog/2006/08/22/now-were-a-platform/comment-page-1/#comment-21440</link>
		<dc:creator>FreshBooks Reaches One Hundred Thousand Users</dc:creator>
		<pubDate>Tue, 07 Nov 2006 19:16:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.freshbooks.com/blog/2006/08/22/now-were-a-platform/#comment-21440</guid>
		<description>[...] Next we released a service that allows our users to send their invoices, not just by email, but via first class mail through the US Post. Our partner sends over one billion pieces of mail a year. We receive our invoices in two or three days in our Toronto office. They seem to take about four days to get the United Kingdom. We also updated our API and added the capability to send ground mail invoices through the US Post via our API so businesses could leverage our billing platform and integrate with their existing systems and processes. [...]</description>
		<content:encoded><![CDATA[<p>[...] Next we released a service that allows our users to send their invoices, not just by email, but via first class mail through the US Post. Our partner sends over one billion pieces of mail a year. We receive our invoices in two or three days in our Toronto office. They seem to take about four days to get the United Kingdom. We also updated our API and added the capability to send ground mail invoices through the US Post via our API so businesses could leverage our billing platform and integrate with their existing systems and processes. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: API version 1.13</title>
		<link>http://www.freshbooks.com/blog/2006/08/22/now-were-a-platform/comment-page-1/#comment-17474</link>
		<dc:creator>API version 1.13</dc:creator>
		<pubDate>Tue, 19 Sep 2006 22:16:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.freshbooks.com/blog/2006/08/22/now-were-a-platform/#comment-17474</guid>
		<description>[...] With the introduction of our new ground mail feature, we have made a small update to our API.  If you are not familiar with our API, you can read more about the FreshBooks platform here.  You can now send invoices via ground mail using the API as well as normal email invoices.  Documentation of the new feature is available on page 15.  Currently our API allows you to create clients as well as create and send invoices outside of FreshBooks.  We have received a lot of requests to add recurring billing to our API, and that is a feature we plan to add for our next big API release, so stay tuned. [...]</description>
		<content:encoded><![CDATA[<p>[...] With the introduction of our new ground mail feature, we have made a small update to our API.  If you are not familiar with our API, you can read more about the FreshBooks platform here.  You can now send invoices via ground mail using the API as well as normal email invoices.  Documentation of the new feature is available on page 15.  Currently our API allows you to create clients as well as create and send invoices outside of FreshBooks.  We have received a lot of requests to add recurring billing to our API, and that is a feature we plan to add for our next big API release, so stay tuned. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
