http://learn.agilezen.com/ 2009-08-08T09:08:26+00:00 http://learn.agilezen.com/ http://learn.agilezen.com/lib/images/favicon.ico text/html 2009-08-07T03:22:56+00:00 Nate Kohari http://learn.agilezen.com/api/resources/stories?rev=1249615376&do=diff Get one story Request: Verb GET URI http://agilezen.com/api/v1/project/PROJECTID/story/STORYID Supports Enrichments Response: <?xml version="1.0" encoding="utf-8"?> <story> <id>1</id> <text>End world hunger</text> <size>large</size> <color>grey</color> <ready>false</ready> <blocked>true</blocked> <reasonBlocked>Need new ideas</reasonBlocked> <phase> <id>1</id> <n… text/html 2009-08-07T03:22:13+00:00 Nate Kohari http://learn.agilezen.com/api/resources/projects?rev=1249615333&do=diff Get one project Request: Verb GET URI http://agilezen.com/api/v1/project/PROJECTID Supports Enrichments Response: <?xml version="1.0" encoding="utf-8"?> <project> <id>123</id> <name>World Peace</name> <description>Working towards world peace</description> <owner> <id>1</id> <name>John Doe</name> </owner> </project> text/html 2009-08-03T13:41:15+00:00 Nate Kohari http://learn.agilezen.com/api/concepts/security?rev=1249306875&do=diff API Keys Zen uses API keys to associate requests with the users that are making them. API keys are identified by a token, which is just a unique series of letters and numbers. Anyone can create an API key via the Developer tab on the Settings screen, and you can have as many keys as you like. Keys can be enabled and disabled as necessary, and all requests using a given key will be denied while the key is disabled. text/html 2009-08-02T22:49:57+00:00 Nate Kohari http://learn.agilezen.com/start?rev=1249253397&do=diff Welcome to the Zen documentation wiki! We're still working to improve the content, so please forgive the clutter for the moment. * API Documentation: An overview of Zen's API (application programming interface). If you're a developer who is interested in creating custom solutions using your Zen project data, look here. text/html 2009-08-02T18:09:14+00:00 Nate Kohari http://learn.agilezen.com/api/concepts/formatting?rev=1249236554&do=diff The Zen API can communicate in two wire formats, XML and JSON. The format for input and output is controlled via the use of HTTP headers, specifically Content-Type and Accept. To refer to the formats, you use their MIME types: Format MIME type XML application/xml JSON application/json If you don't specify a wire format, Zen will speak XML by default. text/html 2009-08-02T18:06:52+00:00 Nate Kohari http://learn.agilezen.com/api/start?rev=1249236412&do=diff The Zen API documentation is a technical reference for developers that would like to integrate their own custom solutions with Zen. Concepts * Overview * Security * Formatting * Filters * Enrichments * Pagination Resources * Projects * Stories text/html 2009-07-31T21:37:28+00:00 Nate Kohari http://learn.agilezen.com/api/concepts/filters?rev=1249076248&do=diff Responses describing container resources can be customized by specifying one or more filters in the URI. Filters are defined by supplying where arguments, which are key/value pairs as follows: where=blocked:true To negate the value of a property (the equivalent of a NOT): text/html 2009-07-31T03:42:49+00:00 Nate Kohari http://learn.agilezen.com/api/concepts/overview?rev=1249011769&do=diff The Zen API is designed around a concept called REST. In a RESTful system, information is organized into resources, each of which is uniquely identified via a URI. Different resources support different actions, which are specified by using HTTP verbs.