<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Asana Developers</title>
	<atom:link href="http://developer.asana.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://developer.asana.com</link>
	<description>Resources for Developers using the Asana API</description>
	<lastBuildDate>Thu, 09 May 2013 00:31:54 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
		<item>
		<title>Organizations, JSON-P, and more!</title>
		<link>http://developer.asana.com/organizations-json-p-and-more/</link>
		<comments>http://developer.asana.com/organizations-json-p-and-more/#comments</comments>
		<pubDate>Thu, 09 May 2013 00:31:54 +0000</pubDate>
		<dc:creator>Greg Slovacek</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://developer.asana.com/?p=44</guid>
		<description><![CDATA[We just wanted to call your attention to a few changes to the API that you may or may not have noticed if you&#8217;ve been developing with us for some time. Some changes we rolled out just recently, others a little while ago: Organizations. With the introduction of Organizations, we&#8217;ve updated the API to handle [...]]]></description>
				<content:encoded><![CDATA[<p>We just wanted to call your attention to a few changes to the API that you may or may not have noticed if you&#8217;ve been developing with us for some time. Some changes we rolled out just recently, others a little while ago:</p>
<ul>
<li><strong>Organizations.</strong> With the introduction of <a href="http://blog.asana.com/2013/05/organizations-in-asana/">Organizations</a>, we&#8217;ve updated the API to handle the changes to how your data is organized. These changes are very minor, but could impact you if you&#8217;ve upgraded. The main change is that in Workspaces that have been upgraded to Organizations, when you create a new Project via the API you must specify a <code>team</code> to put the Project in.</li>
<li><strong>JSON-P support.</strong> If you authenticate using <a href="http://blog.asana.com/2013/04/introducing-asana-connect/">Asana Connect</a>, you can now make requests to the API and receive a response in JSON-P format. Simply add the URL parameter <code>opt_jsonp=CALLBACK</code>, filling in the name of the function you want in place of CALLBACK, and that function will be called with the result.</li>
<li><strong>Task ordering.</strong> You can use the <code>insert_before</code> and <code>insert_after</code> parameters on the <code>addProject</code> Task endpoint in order to insert or move a Task to a specific place within the Project.</li>
<li><strong>Subtask re-homing.</strong> You can set the <code>parent</code> field on a Task to change which Task it is a subtask of.</li>
<li><strong>Followers.</strong> The <code>addFollowers</code> and <code>removeFollowers</code> Task endpoints allow you to add or remove followers on a Task.
</ul>
<p>We hope these changes are helpful, and as usual give us feedback at <a href="mailto:api-support@asana.com!">api-support@asana.com</a>!</p>
]]></content:encoded>
			<wfw:commentRss>http://developer.asana.com/organizations-json-p-and-more/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Asana Connect</title>
		<link>http://developer.asana.com/asana-connect/</link>
		<comments>http://developer.asana.com/asana-connect/#comments</comments>
		<pubDate>Thu, 11 Apr 2013 17:22:20 +0000</pubDate>
		<dc:creator>Isaac Wolkerstorfer</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://developer.asana.com/?p=42</guid>
		<description><![CDATA[We&#8217;re announcing a new feature for the API today: Asana Connect! Asana Connect uses OAuth 2.0 to authenticate users, so you no longer have to ask them to supply an API key. There&#8217;s plenty of documentation, some example code, and even a ruby gem for omniauth. This was an extremely popular request, so we&#8217;re looking [...]]]></description>
				<content:encoded><![CDATA[<p>We&#8217;re announcing a new feature for the API today: <a href="http://blog.asana.com/2013/04/introducing-asana-connect/">Asana Connect</a>!</p>
<p>Asana Connect uses OAuth 2.0 to authenticate users, so you no longer have to ask them to supply an API key. There&#8217;s plenty of <a href="http://developer.asana.com/documentation/#AsanaConnect">documentation</a>, some <a href="https://github.com/Asana/oauth-examples">example code</a>, and even a <a href="https://rubygems.org/gems/omniauth-asana">ruby gem for omniauth</a>.</p>
<p>This was an extremely popular request, so we&#8217;re looking forward to seeing lot of &#8220;Sign in with Asana&#8221; buttons. If you hit any problems, be sure to let us know by reporting issues (or feedback) to <a href="mailto:api-support@asana.com">api-support@asana.com</a>!</p>
]]></content:encoded>
			<wfw:commentRss>http://developer.asana.com/asana-connect/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Add to project during task creation</title>
		<link>http://developer.asana.com/add-to-project-during-task-creation/</link>
		<comments>http://developer.asana.com/add-to-project-during-task-creation/#comments</comments>
		<pubDate>Sat, 15 Dec 2012 01:40:29 +0000</pubDate>
		<dc:creator>Greg Slovacek</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://developer.asana.com/?p=34</guid>
		<description><![CDATA[In addition to fixing a few bugs lately, we&#8217;ve also allowed you to specify a projects field during task creation, and provide a list of ids of the projects the task should be added to. This has been updated in the Task reference documentation.]]></description>
				<content:encoded><![CDATA[<p>In addition to fixing a few bugs lately, we&#8217;ve also allowed you to specify a <code>projects</code> field during task creation, and provide a list of ids of the projects the task should be added to. This has been updated in the <a href="http://developer.asana.com/documentation/#tasks">Task reference</a> documentation.</p>
]]></content:encoded>
			<wfw:commentRss>http://developer.asana.com/add-to-project-during-task-creation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Tags are here!</title>
		<link>http://developer.asana.com/tags-are-here/</link>
		<comments>http://developer.asana.com/tags-are-here/#comments</comments>
		<pubDate>Tue, 19 Jun 2012 20:51:44 +0000</pubDate>
		<dc:creator>Greg Slovacek</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://asanadev.wpengine.com/?p=22</guid>
		<description><![CDATA[Thanks to all those that requested it, the API now supports tags! Here are the changes we recently rolled out: Projects now have a stories endpoint similar to tasks, for querying comments/updates on the project object itself. There is a new /tags endpoint for manipulating tags. Full records for tasks now include a tags field. [...]]]></description>
				<content:encoded><![CDATA[<p>Thanks to all those that requested it, the API now supports <a href="http://developer.asana.com/documentation/#tags">tags</a>! Here are the changes we recently rolled out:</p>
<ul>
<li>Projects now have a <code>stories</code> endpoint similar to tasks, for querying comments/updates on the project object itself.</li>
<li>There is a new <code>/tags</code> endpoint for manipulating tags.</li>
<li>Full records for tasks now include a <code>tags</code> field.</li>
<li>The task endpoint now has <code>addTag</code> and <code>removeTag</code> methods.</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://developer.asana.com/tags-are-here/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Minor bugfixes</title>
		<link>http://developer.asana.com/minor-bugfixes/</link>
		<comments>http://developer.asana.com/minor-bugfixes/#comments</comments>
		<pubDate>Sat, 26 May 2012 00:40:40 +0000</pubDate>
		<dc:creator>Greg Slovacek</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://developer.asana.com/?p=21</guid>
		<description><![CDATA[We&#8217;ve fixed a few bugs in the last week, including: The &#8220;method&#8221; option was ineffective when using it in the POST body. 500 error when setting a task assignee to null. Just a reminder to our developers that if you receive a 500 response, you&#8217;ve probably hit a bug in the API. Please don&#8217;t be [...]]]></description>
				<content:encoded><![CDATA[<p>We&#8217;ve fixed a few bugs in the last week, including:</p>
<ul>
<li>The &#8220;method&#8221; option was ineffective when using it in the POST body.</li>
<li>500 error when setting a task assignee to null.</li>
</ul>
<p>Just a reminder to our developers that if you receive a 500 response, you&#8217;ve probably hit a bug in the API. Please don&#8217;t be shy about reporting it to api-support@asana.com!</p>
]]></content:encoded>
			<wfw:commentRss>http://developer.asana.com/minor-bugfixes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Version 1.0 of the API has launched!</title>
		<link>http://developer.asana.com/version-1-0-of-the-api-has-launched/</link>
		<comments>http://developer.asana.com/version-1-0-of-the-api-has-launched/#comments</comments>
		<pubDate>Thu, 19 Apr 2012 00:30:30 +0000</pubDate>
		<dc:creator>Greg Slovacek</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://developer.asana.com/?p=18</guid>
		<description><![CDATA[We&#8217;re pleased to announce that the first public version of the Asana API is live! Existing developers should take note of an important change. The base URL for all API requests has changed to: https://app.asana.com/api/1.0 Notice we have changed the version number and removed the leading dash (-) from the path. We will keep the [...]]]></description>
				<content:encoded><![CDATA[<p>We&#8217;re pleased to announce that the first public version of the Asana API is live!</p>
<p>Existing developers should take note of an important change. The base URL for all API requests has changed to:</p>
<ul>https://app.asana.com/api/1.0</ul>
<p>Notice we have changed the version number <em>and</em> removed the leading dash (-) from the path. We will keep the old 0.1 access point around for a while and give you time to switch over, but will end-of-life it soon. Please update your clients!</p>
<p>Thanks for being a part of our early access program. Happy developing!</p>
]]></content:encoded>
			<wfw:commentRss>http://developer.asana.com/version-1-0-of-the-api-has-launched/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Minor fixes, changes and additions</title>
		<link>http://developer.asana.com/minor-fixes-changes-and-additions/</link>
		<comments>http://developer.asana.com/minor-fixes-changes-and-additions/#comments</comments>
		<pubDate>Wed, 04 Apr 2012 00:06:52 +0000</pubDate>
		<dc:creator>Greg Slovacek</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://developer.asana.com/?p=16</guid>
		<description><![CDATA[Fixed a bug where requests that should return 400 were returning 500s or unparsable content. Renamed Task.schedule_status to assignee_status and changed its value of ok to later Added Task.due_on so you can get and set due dates for Tasks with the API.]]></description>
				<content:encoded><![CDATA[<ul>
<li>Fixed a bug where requests that should return 400 were returning 500s or unparsable content.</li>
<li>Renamed <code>Task.schedule_status</code> to <code>assignee_status</code> and changed its value of <code>ok</code> to <code>later</code></li>
<li>Added <code>Task.due_on</code> so you can get and set due dates for Tasks with the API.</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://developer.asana.com/minor-fixes-changes-and-additions/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>API early access available!</title>
		<link>http://developer.asana.com/api-early-access/</link>
		<comments>http://developer.asana.com/api-early-access/#comments</comments>
		<pubDate>Tue, 28 Feb 2012 05:26:17 +0000</pubDate>
		<dc:creator>Kenny</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://developer.wpengine.com/?p=13</guid>
		<description><![CDATA[We are now making the Asana API more widely available! Those desiring early access can answer a few questions and we&#8217;ll let you know when we&#8217;ve given you access.]]></description>
				<content:encoded><![CDATA[<p>We are now making the Asana API more widely available! Those desiring early access can <a href="https://docs.google.com/a/asana.com/spreadsheet/viewform?formkey=dGF2TUlmWFA0czRhSjlfS2NpZVFYZ0E6MQ">answer a few questions</a> and we&#8217;ll let you know when we&#8217;ve given you access.</p>
]]></content:encoded>
			<wfw:commentRss>http://developer.asana.com/api-early-access/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>First API Update</title>
		<link>http://developer.asana.com/first-api-update/</link>
		<comments>http://developer.asana.com/first-api-update/#comments</comments>
		<pubDate>Tue, 28 Feb 2012 00:17:26 +0000</pubDate>
		<dc:creator>Kenny</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://developer.wpengine.com/?p=12</guid>
		<description><![CDATA[Discarded opt_include/opt_exclude in favor of just opt_fields which explicitly names all fields desired. Any unnamed fields will not be included in the output (we think this is the right way to expose this functionality, so you don&#8217;t have to guess what will be included by default.) The ID of objects are always included. Added a [...]]]></description>
				<content:encoded><![CDATA[<ul>
<li>Discarded <code>opt_include/opt_exclude</code> in favor of just <code>opt_fields</code> which explicitly names all fields desired. Any unnamed fields will not be included in the output (we think this is the right way to expose this functionality, so you don&#8217;t have to guess what will be included by default.) The ID of objects are <em>always</em> included.</li>
<li>Added a (read-only) &#8220;workspace&#8221; property to Tasks.</li>
<li><code>target</code> and <code>source</code> of a Story are no longer part of their compact representation.</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://developer.asana.com/first-api-update/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
