This is the newer, REST-based version of this API. If you are maintaining an older application, it might be using the legacy, non-RESTful version of this API, which can be found documented here.
Returns a page full of time entries for the given project, in descending order by date. Each page contains up to 50 time entry records. To select a different page of data, set the “page” query parameter to a value greater than zero. The X-Records HTTP header will be set to the total number of time entries in the project, X-Pages will be set to the total number of pages, and X-Page will be set to the current page.
<time-entries type="array">
<time-entry>
...
</time-entry>
...
</time-entries>
Returns all time entries associated with the given todo item, in descending order by date.
<time-entries type="array">
<time-entry>
...
</time-entry>
...
</time-entries>
Creates a new time entry for the given project.
<time-entry>
<person-id>#{person-id}</person-id>
<date>#{date}</date>
<hours>#{hours}</hours>
<description>#{description}</description>
</time-entry>
Returns HTTP status code 201 (Created) on success, with the Location header set to the URL of the new time entry. The integer ID of the entry may be extracted from that URL.
Creates a new time entry for the given todo item.
<time-entry>
<person-id>#{person-id}</person-id>
<date>#{date}</date>
<hours>#{hours}</hours>
<description>#{description}</description>
</time-entry>
Returns HTTP status code 201 (Created) on success, with the Location header set to the URL of the new time entry. The integer ID of the entry may be extracted from that URL.
Returns a blank “template” XML record for defining a new time entry. Simply modify the fields accordingly, and submit as described by the X-Create-Action HTTP header.
<time-entry>
...
</time-entry>
Retrieves a single time-entry record, given its integer ID.
<time-entry>
...
</time-entry>
Returns the requested time-entry record, but only those fields that may be edited. Simply modify the fields and submit as described by the X-Update-Action HTTP header.
<time-entry>
...
</time-entry>
Updates the given time-entry record with the data given.
<time-entry>
<person-id>#{person-id}</person-id>
<date>#{date}</date>
<hours>#{hours}</hours>
<description>#{description}</description>
<!-- if associated with a todo-item -->
<todo-item-id>#{todo-item-id}</todo-item-id>
</timeentry>
Returns HTTP status code 200 on success.
Destroys the given time entry record.
Returns HTTP status code 200 on success.
Return the set of time entries that match the given criteria. This action accepts the following query parameters: “from”, “to”, “subject_id”, “todo_item_id”, “filter_project_id”, and “filter_company_id”. Both “from” and “to” should be dates in “YYYYMMDD” format, and can be used to restrict the result to a particular date range. (No more than 6 months’ worth of entries may be returned in a single query, though). The “subject_id” parameter lets you constrain the result to a single person’s time entries. “todo_item_id” restricts the result to only those entries relating to the given todo item. “filter_project_id” restricts the entries to those for the given project, and “filter_company_id” restricts the entries to those for the given company.
<time-entries type="array">
<time-entry>
...
</time-entry>
...
</time-entries>