v1
latestOpenAPI 3.0.12026-07-2464217456.8 KBGet all tasks
Query parameters
This parameter sets the maximum number of responses to be displayed per page. If the page size is insufficient to accommodate the whole number of responses obtained, the pagination object will include a link to the next page as well as the next page token. If left blank, it defaults to 100.
Use this parameter to specify the pageToken of a page to which you want to navigate. This pageToken can be obtained from a previous request which specified a limit and will only be active for 15 minutes after it is created.
This query parameter allows you to specify which fields should be returned in the response body by selecting from the drop down. To get the relevant fields, use comma separated values. If the field is left blank, the default properties are returned.
This query parameter allows you to specify if all the fields should be returned in the response body. If the field is left blank, the default properties are returned.
You can use the sortBy param to sort the responses by the given field.
The sortOrder param can be used to specify the sorting order, which can be Ascending (ASC) or Descending (DESC). Descending is the default option.
You can use the match param to specify if we need to filter the entries using either AND(all) / OR(any). Defaults to AND.
You can use this param to specify some date and the responses will contain tasks whose date are greater than the given date.
You can use this param to specify some date and the responses will contain exact matches of tasks that match the given date.
You can use this param to specify some date and the responses will contain tasks whose date are less than the given date.
You can use this param to specify some date and the responses will contain tasks whose date are greater than or equal to the given date.
You can use this param to specify some date and the responses will contain tasks whose date are less than or equal to the given date.
You can use this param to specify some date and the responses will contain tasks whose date are greater than the given date.
You can use this param to specify some date and the responses will contain exact matches of tasks that match the given date.
You can use this param to specify some date and the responses will contain tasks whose date are less than the given date.
You can use this param to specify some date and the responses will contain tasks whose date are greater than or equal to the given date.
You can use this param to specify some date and the responses will contain tasks whose date are less than or equal to the given date.
You can use this param to specify some date and the responses will contain tasks whose date are greater than the given date.
You can use this param to specify some date and the responses will contain exact matches of tasks that match the given date.
You can use this param to specify some date and the responses will contain tasks whose date are less than the given date.
You can use this param to specify some date and the responses will contain tasks whose date are greater than or equal to the given date.
You can use this param to specify some date and the responses will contain tasks whose date are less than or equal to the given date.
You can use this param to specify some date and the responses will contain tasks whose date are greater than the given date.
You can use this param to specify some date and the responses will contain exact matches of tasks that match the given date.
You can use this param to specify some date and the responses will contain tasks whose date are less than the given date.
You can use this param to specify some date and the responses will contain tasks whose date are greater than or equal to the given date.
You can use this param to specify some date and the responses will contain tasks whose date are less than or equal to the given date.
You can use this param to provide an epoch milli value and the responses will contain tasks whose date are greater than the given tasks created date.
You can use this param to provide an epoch milli value and the responses will contain exact matches of tasks that match the given tasks created date.
You can use this param to provide an epoch milli value and the responses will contain tasks whose date are less than the given tasks created date.
You can use this param to provide an epoch milli value and the responses will contain tasks whose date are greater than or equal to the given tasks created date.
You can use this param to provide an epoch milli value and the responses will contain tasks whose date are less than or equal to the given tasks created date.
You can use this param to provide an epoch milli value and the responses will contain tasks whose date are greater than the given tasks updated date.
You can use this param to provide an epoch milli value and the responses will contain exact matches of tasks that match the given tasks updated date.
You can use this param to provide an epoch milli value and the responses will contain tasks whose date are less than the given tasks updated date.
You can use this param to provide an epoch milli value and the responses will contain tasks whose date are greater than or equal to the given tasks updated date.
You can use this param to provide an epoch milli value and the responses will contain tasks whose date are less than or equal to the given tasks updated date.
You can use this param to specify some value as project id and the responses will contain exact matches of tasks that match the given value.
You can use this param to specify some value as phase id and the responses will contain exact matches of tasks that match the given value.
You can use this param to specify some task name and the responses will contain exact matches of tasks that match the given name.
You can use this param to specify some task name and the responses will contain matches of tasks that match the given name.
You can use this param to specify some task name and the responses will not contain matches of tasks that match the given name.
You can use this param to specify some value as effort and the responses will contain exact matches of tasks that match the given value.
You can use this param to specify some value as effort and the responses will contain exact matches of tasks greater than that of the given value.
You can use this param to specify some value as effort and the responses will contain exact matches of tasks lesser than that of the given value.
You can use this param to specify some value as progress and the responses will contain exact matches of tasks that match the given value.
You can use this param to specify some value as progress and the responses will contain exact matches of tasks greater than that of the given value.
You can use this param to specify some value as progress and the responses will contain exact matches of tasks lesser than that of the given value.
You can use this parameter to specify whether responses will include the archived tasks.
You can use this param to provide status and the responses will contain tasks that are equal to the given status
You can use this param to provide statuses and the responses will contain tasks that contains the given status
You can use this param to provide statuses and the responses will not contain tasks that are equal to the given status
You can use this param to provide status of project and the responses will contain tasks whose project's status are equal to the given status
You can use this param to provide statuses of project and the responses will contain tasks whose project's statuses that contains the given status
You can use this param to provide statuses of project and the responses will not contain tasks whose project's statuses are equal to the given status(es)
You can use this param to provide external reference id and the responses will contain tasks that are equal to the given id
Response
The requested action was successfully executed.
Example response
{
"data": [
{
"taskId": 201,
"taskName": "Kick off",
"taskDescription": "<p>Schedule Kick off meeting with the stakeholders involved.</p>",
"startDate": "2023-03-28",
"dueDate": "2023-03-28",
"effortInMinutes": 3000,
"progress": 50,
"atRisk": true,
"createdAt": 1681319726000,
"updatedAt": 1681319726000,
"createdBy": {
"emailId": "john.doe@rocketlane.com",
"userId": 201,
"firstName": "John",
"lastName": "Doe"
},
"updatedBy": {
"emailId": "john.doe@rocketlane.com",
"userId": 201,
"firstName": "John",
"lastName": "Doe"
},
"project": {
"projectId": 201,
"projectName": "Acme onboarding"
},
"status": {
"value": 2,
"label": "In progress"
},
"fields": [
{
"fieldId": 201,
"fieldLabel": "MRR",
"fieldValueLabel": "1000"
}
],
"startDateActual": "2023-03-28",
"dueDateActual": "2023-03-28",
"type": "MILESTONE",
"phase": {
"phaseId": 201,
"phaseName": "Go live"
},
"assignees": {
"members": [
{
"emailId": "john.doe@rocketlane.com",
"userId": 201,
"firstName": "John",
"lastName": "Doe"
}
],
"placeholders": [
{
"placeholderId": 201,
"placeholderName": "Customer Success",
"role": {
"roleId": 101,
"roleName": "Designer"
}
}
]
},
"followers": {
"members": [
{
"emailId": "john.doe@rocketlane.com",
"userId": 201,
"firstName": "John",
"lastName": "Doe"
}
]
},
"dependencies": [
{
"taskId": 201,
"taskName": "Kick off"
}
],
"parent": {
"taskId": 201,
"taskName": "Kick off"
},
"externalReferenceId": "task_8171",
"billable": true,
"timeEntryCategory": {
"categoryId": 201,
"categoryName": "Pre-sales"
},
"financialsBudgets": [
{
"budgetId": 201,
"budgetName": "Pre-sales"
}
],
"priority": {
"value": 2,
"label": "High"
}
}
],
"pagination": {
"pageSize": 100,
"hasMore": true,
"totalRecordCount": 10398,
"nextPage": "https://api.rocketlane.com/api/1.0/tasks?includeFields=category,minutes&billable.eq=false&sortBy=startDate&sortOrder=desc&pageToken=e4a3dd8e-e338-11ed-b5ea-0242ac120002&limit=100&assignee.any=1&startDate.gt=2022-01-02",
"nextPageToken": "e4a3dd8e-e338-11ed-b5ea-0242ac120002"
}
}