Rest api » History » Version 43

Jean-Philippe Lang, 2011-07-05 18:26

1 26 Jean-Philippe Lang
{{>toc}}
2 26 Jean-Philippe Lang
3 1 Jean-Philippe Lang
h1. Redmine API
4 1 Jean-Philippe Lang
5 1 Jean-Philippe Lang
Redmine exposes some of its data through a REST API. This API provides access and basic CRUD operations (create, update, delete) for the resources described below.
6 1 Jean-Philippe Lang
7 1 Jean-Philippe Lang
h2. API Description
8 1 Jean-Philippe Lang
9 24 Jean-Philippe Lang
|_.Resource                     |_.Status     |_.Notes  |_.Availability|
10 24 Jean-Philippe Lang
|[[Rest_Issues|Issues]]         | Beta        | Usable with some bugs and rough edges.  | 1.0 |
11 24 Jean-Philippe Lang
|[[Rest_Projects|Projects]]     | Beta        | Usable with some bugs and rough edges.  | 1.0 |
12 28 Jean-Philippe Lang
|[[Rest_Users|Users]]           | Beta | | 1.1 |
13 39 Jean-Philippe Lang
|[[Rest_TimeEntries|Time Entries]]           | Beta | | 1.1 |
14 28 Jean-Philippe Lang
|[[Rest_News|News]]             | Prototype | Prototype implementation for @index@ only | 1.1 |
15 43 Jean-Philippe Lang
|[[Rest_IssueRelations|Issue Relations]]  | Alpha | | 1.3 |
16 43 Jean-Philippe Lang
|[[Rest_Versions|Versions]]  | Alpha | | 1.3 |
17 24 Jean-Philippe Lang
18 15 Eric Davis
Status legend:
19 1 Jean-Philippe Lang
20 1 Jean-Philippe Lang
* Stable - feature complete, no major changes planned
21 1 Jean-Philippe Lang
* Beta - usable for integrations with some bugs or missing minor functionality
22 1 Jean-Philippe Lang
* Alpha - major functionality in place, needs feedback from API users and integrators
23 1 Jean-Philippe Lang
* Prototype - very rough implementation, possible major breaking changes mid-version. *Not recommended for integration*
24 1 Jean-Philippe Lang
* Planned - planned in a future version, depending on developer availability
25 1 Jean-Philippe Lang
26 24 Jean-Philippe Lang
h2. General topics
27 1 Jean-Philippe Lang
28 24 Jean-Philippe Lang
h3. Authentication
29 24 Jean-Philippe Lang
30 24 Jean-Philippe Lang
Most of the time, the API requires authentication. To enable the API-style authentication, you have to check *Enable REST API* in Administration -> Settings -> Authentication. Then, authentication can be done in 2 different ways:
31 24 Jean-Philippe Lang
* using your regular login/password via HTTP Basic authentication.
32 38 Jean-Philippe Lang
* using your API key which is a handy way to avoid putting a password in a script. The API key may be attached to each request in one of the following way:
33 38 Jean-Philippe Lang
** passed in as a "key" parameter
34 38 Jean-Philippe Lang
** passed in as a username with a random password via HTTP Basic authentication
35 38 Jean-Philippe Lang
** passed in as a "Redmine-API-Key" HTTP header (added in Redmine 1.1.0)
36 38 Jean-Philippe Lang
37 38 Jean-Philippe Lang
You can find your API key on your account page ( /my/account ) when logged in, on the right-hand pane of the default layout.
38 24 Jean-Philippe Lang
39 24 Jean-Philippe Lang
h3. Collection resources and pagination
40 24 Jean-Philippe Lang
41 24 Jean-Philippe Lang
The response to a GET request on a collection ressources (eg. @/issues.xml@, @/users.xml@) generally won't return all the objets available in your database. Redmine version:1.1.0 introduces a common way to query such ressources using the following parameters:
42 24 Jean-Philippe Lang
43 24 Jean-Philippe Lang
* @offset@: the offset of the first object to retrieve
44 24 Jean-Philippe Lang
* @limit@: the number of items to be present in the response (default is 25, maximum is 100)
45 24 Jean-Philippe Lang
46 25 Jean-Philippe Lang
Alternatively, you can use the @page@ parameter, instead of @offset@, in conjunction with @limit@.
47 24 Jean-Philippe Lang
48 24 Jean-Philippe Lang
Examples:
49 24 Jean-Philippe Lang
50 24 Jean-Philippe Lang
<pre>
51 24 Jean-Philippe Lang
GET /issues.xml
52 24 Jean-Philippe Lang
=> returns the 25 first issues
53 24 Jean-Philippe Lang
54 24 Jean-Philippe Lang
GET /issues.xml?limit=100
55 24 Jean-Philippe Lang
=> returns the 100 first issues
56 24 Jean-Philippe Lang
57 24 Jean-Philippe Lang
GET /issues.xml?offset=30&limit=10
58 24 Jean-Philippe Lang
=> returns 10 issues from the 30th
59 24 Jean-Philippe Lang
60 24 Jean-Philippe Lang
GET /issues.xml?page=3&limit=10
61 24 Jean-Philippe Lang
=> same as above
62 24 Jean-Philippe Lang
</pre>
63 24 Jean-Philippe Lang
64 24 Jean-Philippe Lang
Responses to GET requests on collection ressources provide information about the total object count available in Redmine and the offset/limit used for the response. Examples:
65 24 Jean-Philippe Lang
66 24 Jean-Philippe Lang
<pre>
67 24 Jean-Philippe Lang
GET /issues.xml
68 24 Jean-Philippe Lang
69 24 Jean-Philippe Lang
<issues type="array" total_count="2595" limit="25" offset="0">
70 24 Jean-Philippe Lang
  ...
71 24 Jean-Philippe Lang
</issues>
72 24 Jean-Philippe Lang
</pre>
73 24 Jean-Philippe Lang
74 24 Jean-Philippe Lang
<pre>
75 24 Jean-Philippe Lang
GET /issues.json
76 24 Jean-Philippe Lang
77 24 Jean-Philippe Lang
{ "issues":[...], "total_count":2595, "limit":25, "offset":0 }
78 24 Jean-Philippe Lang
</pre>
79 24 Jean-Philippe Lang
80 24 Jean-Philippe Lang
Note: if you're using a REST client that does not support such top level attributes (total_count, limit, offset), you can set the @nometa@ parameter or @X-Redmine-Nometa@ HTTP header to 1 to get responses without them. Example:
81 24 Jean-Philippe Lang
82 24 Jean-Philippe Lang
<pre>
83 24 Jean-Philippe Lang
GET /issues.xml?nometa=1
84 24 Jean-Philippe Lang
85 24 Jean-Philippe Lang
<issues type="array">
86 24 Jean-Philippe Lang
  ...
87 24 Jean-Philippe Lang
</issues>
88 24 Jean-Philippe Lang
</pre>
89 23 Jean-Philippe Lang
90 29 Etienne Massip
h3. Fetching associated data
91 29 Etienne Massip
92 29 Etienne Massip
Since of version:1.1.0, you have to explicitly specify the associations you want to be included in the query result by appending the @include@ parameter to the query url :
93 29 Etienne Massip
94 29 Etienne Massip
Example:
95 29 Etienne Massip
96 41 Jean-Philippe Lang
To retrieve issue journals with its description:
97 29 Etienne Massip
98 29 Etienne Massip
<pre>
99 29 Etienne Massip
GET /issues/296.xml?include=journals
100 29 Etienne Massip
101 29 Etienne Massip
<issue>
102 29 Etienne Massip
  <id>296</id>
103 30 Etienne Massip
  ...
104 29 Etienne Massip
  <journals type="array">
105 29 Etienne Massip
  ...
106 1 Jean-Philippe Lang
  </journals>
107 41 Jean-Philippe Lang
</issue>
108 41 Jean-Philippe Lang
</pre>
109 41 Jean-Philippe Lang
110 41 Jean-Philippe Lang
You can also load multiple associations using a coma separated list of items.
111 41 Jean-Philippe Lang
112 41 Jean-Philippe Lang
Example:
113 41 Jean-Philippe Lang
114 41 Jean-Philippe Lang
<pre>
115 41 Jean-Philippe Lang
GET /issues/296.xml?include=journals,changesets
116 41 Jean-Philippe Lang
117 41 Jean-Philippe Lang
<issue>
118 41 Jean-Philippe Lang
  <id>296</id>
119 41 Jean-Philippe Lang
  ...
120 41 Jean-Philippe Lang
  <journals type="array">
121 41 Jean-Philippe Lang
  ...
122 41 Jean-Philippe Lang
  </journals>
123 41 Jean-Philippe Lang
  <changesets type="array">
124 41 Jean-Philippe Lang
  ...
125 41 Jean-Philippe Lang
  </changesets>
126 29 Etienne Massip
</issue>
127 29 Etienne Massip
</pre>
128 29 Etienne Massip
129 42 Jean-Philippe Lang
h3. Working with custom fields
130 42 Jean-Philippe Lang
131 42 Jean-Philippe Lang
Most of the Redmine objects support custom fields. Their values can be found in the @custom_fields@ attributes.
132 42 Jean-Philippe Lang
133 42 Jean-Philippe Lang
XML Example:
134 42 Jean-Philippe Lang
135 42 Jean-Philippe Lang
<pre>
136 42 Jean-Philippe Lang
GET /issues/296.xml      # an issue with 2 custom fields
137 42 Jean-Philippe Lang
138 42 Jean-Philippe Lang
<issue>
139 42 Jean-Philippe Lang
  <id>296</id>
140 42 Jean-Philippe Lang
  ...
141 42 Jean-Philippe Lang
  <custom_fields type="array">
142 42 Jean-Philippe Lang
    <custom_field name="Affected version" id="1">
143 42 Jean-Philippe Lang
      <value>1.0.1</value>
144 42 Jean-Philippe Lang
    </custom_field>
145 42 Jean-Philippe Lang
    <custom_field name="Resolution" id="2">
146 42 Jean-Philippe Lang
      <value>Fixed</value>
147 42 Jean-Philippe Lang
    </custom_field>
148 42 Jean-Philippe Lang
  </custom_fields>
149 42 Jean-Philippe Lang
</issue>
150 42 Jean-Philippe Lang
</pre>
151 42 Jean-Philippe Lang
152 42 Jean-Philippe Lang
JSON Example:
153 42 Jean-Philippe Lang
154 42 Jean-Philippe Lang
<pre>
155 42 Jean-Philippe Lang
GET /issues/296.json      # an issue with 2 custom fields
156 42 Jean-Philippe Lang
157 42 Jean-Philippe Lang
{"issue":
158 42 Jean-Philippe Lang
  {
159 42 Jean-Philippe Lang
    "id":8471,
160 42 Jean-Philippe Lang
    ...
161 42 Jean-Philippe Lang
    "custom_fields":
162 42 Jean-Philippe Lang
      [
163 42 Jean-Philippe Lang
        {"value":"1.0.1","name":"Affected version","id":1},
164 42 Jean-Philippe Lang
        {"value":"Fixed","name":"Resolution","id":2}
165 42 Jean-Philippe Lang
      ]
166 42 Jean-Philippe Lang
  }
167 42 Jean-Philippe Lang
}
168 42 Jean-Philippe Lang
</pre>
169 42 Jean-Philippe Lang
170 42 Jean-Philippe Lang
You can also set/change the values of the custom fields when creating/updating an object using the same syntax (except that the custom field name is not required).
171 42 Jean-Philippe Lang
172 42 Jean-Philippe Lang
XML Example:
173 42 Jean-Philippe Lang
174 42 Jean-Philippe Lang
<pre>
175 42 Jean-Philippe Lang
PUT /issues/296.xml
176 42 Jean-Philippe Lang
177 42 Jean-Philippe Lang
<issue>
178 42 Jean-Philippe Lang
  <subject>Updating custom fields of an issue</subject>
179 42 Jean-Philippe Lang
  ...
180 42 Jean-Philippe Lang
  <custom_fields type="array">
181 42 Jean-Philippe Lang
    <custom_field id="1">
182 42 Jean-Philippe Lang
      <value>1.0.2</value>
183 42 Jean-Philippe Lang
    </custom_field>
184 42 Jean-Philippe Lang
    <custom_field id="2">
185 42 Jean-Philippe Lang
      <value>Invalid</value>
186 42 Jean-Philippe Lang
    </custom_field>
187 42 Jean-Philippe Lang
  </custom_fields>
188 42 Jean-Philippe Lang
</issue>
189 42 Jean-Philippe Lang
</pre>
190 42 Jean-Philippe Lang
191 42 Jean-Philippe Lang
Note: the @type="array"@ attribute on @custom_fields@ XML tag is strictly required.
192 42 Jean-Philippe Lang
193 42 Jean-Philippe Lang
JSON Example:
194 42 Jean-Philippe Lang
195 42 Jean-Philippe Lang
<pre>
196 42 Jean-Philippe Lang
PUT /issues/296.json
197 42 Jean-Philippe Lang
198 42 Jean-Philippe Lang
{"issue":
199 42 Jean-Philippe Lang
  {
200 42 Jean-Philippe Lang
    "subject":"Updating custom fields of an issue",
201 42 Jean-Philippe Lang
    ...
202 42 Jean-Philippe Lang
    "custom_fields":
203 42 Jean-Philippe Lang
      [
204 42 Jean-Philippe Lang
        {"value":"1.0.2","id":1},
205 42 Jean-Philippe Lang
        {"value":"Invalid","id":2}
206 42 Jean-Philippe Lang
      ]
207 42 Jean-Philippe Lang
  }
208 42 Jean-Philippe Lang
}
209 42 Jean-Philippe Lang
</pre>
210 42 Jean-Philippe Lang
211 1 Jean-Philippe Lang
h2. API Usage in various languages/tools
212 5 Jean-Philippe Lang
213 1 Jean-Philippe Lang
* [[Rest_api_with_ruby|Ruby]]
214 1 Jean-Philippe Lang
* [[Rest_api_with_php|PHP]]
215 23 Jean-Philippe Lang
* [[Rest_api_with_python|Python]]
216 27 Jean-Philippe Lang
* [[Rest_api_with_java|Java]]
217 1 Jean-Philippe Lang
* [[Rest_api_with_curl|cURL]]
218 37 Bevan Rudge
* "Drupal Redmine API module, 2.x branch (currently not stable)":http://drupal.org/project/redmine