GET /time_tracking_entries

Required scope: time_tracking_entries:read

Returns a list of time tracking entries filtered to a task, attributed project, portfolio or user.

Servers

Query parameters

Name Type Required Description
portfolio String No

Globally unique identifier for the portfolio to filter time tracking entries by.

opt_pretty Boolean No

Provides “pretty” output. Provides the response in a “pretty” format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging.

entered_on_end_date String No

The end date for filtering time tracking entries by when they were entered.

attributable_to String No

Globally unique identifier for the project the time tracking entries are attributed to.

timesheet_approval_status String No

Globally unique identifier for the timesheet approval status to filter time tracking entries by.

limit Integer No

Results per page. The number of objects to return per page. The value must be between 1 and 100.

user String No

Globally unique identifier for the user to filter time tracking entries by.

entered_on_start_date String No

The start date for filtering time tracking entries by when they were entered.

task String No

Globally unique identifier for the task to filter time tracking entries by.

opt_fields[] Array No

This endpoint returns a resource which excludes some properties by default. To include those optional properties, set this query parameter to a comma-separated list of the properties you wish to include.

workspace String No

Globally unique identifier for the workspace. At least one of entered_on_start_date or entered_on_end_date must be provided when filtering by workspace.

offset String No

Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, which can be used as an input parameter to the next request. If an offset is not passed in, the API will return the first page of results. Note: You can only pass in an offset that was returned to you via a previously paginated request.

How to start integrating

  1. Add HTTP Task to your workflow definition.
  2. Search for the API you want to integrate with and click on the name.
    • This loads the API reference documentation and prepares the Http request settings.
  3. Click Test request to test run your request to the API and see the API's response.