Available statuses: 200 OK, 204 No Content, 404 Not Found

Object: Ticket

Location: n/a

Formats: XML, JSON

Returns tickets list. If no report is specified, default report set for space will be used.


Param Description
report Specify report id. Assembla provides following predefined reports associated with IDs:

  • 0: All Tickets, order by priority
  • 1: Active Tickets, order by milestone
  • 2: All Tickets, no order
  • 3: Active Tickets, order by user
  • 4: Closed Tickets, order by milestone
  • 5: Closed Tickets, order by date
  • 6: All user tickets (authenticated user)
  • 7: All user's active tickets (authenticated user)
  • 8: All user's closed tickets (authenticated user)
  • 9: All user's followed open tickets (authenticated user)
Also custom reports are available when created from UI, all custom reports start with the letter "u" before the report ID itself i.e. a custom report id looks like "u12": 12 is the report id.

Check the custom reports list API query for a list of custom reports.
page Parameter to specify which page to request, see per_page to determine how many items per page.
per_page Specify the number of tickets fetched per one page, default is 10.
sort_order Sort order, acceptable values are asc or desc, default is asc.
sort_by Field to sort by, acceptable values are id number summary priority completed_date created_on importance is_story milestone_id updated_at working_hours estimate total_estimate total_invested_hours total_working_hours.
number Ticket number or numbers to be listed. It can be one ticket number number=1 or a list of numbers number[]=1&number[]=2&.... All other params are ignored if number param is given.


Request JSON, using cURL utility:

curl -H "Authorization: Bearer _token"


HTTP/1.1 200 OK
Server: nginx/0.8.55
Date: Mon, 18 Jun 2012 11:31:32 GMT
Content-Type: application/json; charset=utf-8
Transfer-Encoding: chunked
Connection: keep-alive
Status: 200

    "custom_fields":{"Text Field":"","list":""},
    "summary":"A nice ticket",

JSON is formatted here for readability, in a real response JSON body is inline with no indentation.

Request XML, using cURL utility:

curl -H "Authorization: Bearer _token"


HTTP/1.1 200 OK
Server: nginx/0.8.55
Date: Mon, 18 Jun 2012 11:35:32 GMT
Content-Type: application/xml; charset=utf-8
Transfer-Encoding: chunked
Connection: keep-alive
Status: 200

<?xml version="1.0" encoding="UTF-8"?>
<tickets type="array">
    <total-working-hours type="float">0.0</total-working-hours>
    <status type="integer">1</status>
    <milestone-id nil="true"></milestone-id>
    <summary>A nice ticket</summary>
    <estimate type="float">0.0</estimate>
    <is-story type="boolean">false</is-story>
    <permission-type type="integer">0</permission-type>
    <assigned-to-id nil="true"></assigned-to-id>
    <updated-at type="datetime">2012-04-12T10:32:58Z</updated-at>
    <story-importance type="integer">0</story-importance>
    <total-invested-hours type="float">0.0</total-invested-hours>
    <total-estimate type="float">0.0</total-estimate>
    <working-hours type="float">0.0</working-hours>
    <created-on type="datetime">2011-09-02T10:21:48Z</created-on>
    <importance type="float">0.0</importance>
    <completed-date nil="true"></completed-date>
    <id type="integer">10</id>
    <component-id nil="true"></component-id>
    <priority type="integer">1</priority>
    <number type="integer">8</number>

Description for each field: ticket object fields reference