v1
latestOpenAPI 3.0.12026-07-2464217456.8 KBGet all phases
Query parameters
The identifier of the project is generated by the system and can be used to identify the project globally.
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 phases 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 phases that match the given date.
You can use this param to specify some date and the responses will contain phases whose date are less than the given date.
You can use this param to specify some date and the responses will contain phases 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 phases 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 phases 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 phases that match the given date.
You can use this param to specify some date and the responses will contain phases whose date are less than the given date.
You can use this param to specify some date and the responses will contain phases 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 phases 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 phases 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 phases that match the given date.
You can use this param to specify some date and the responses will contain phases whose date are less than the given date.
You can use this param to specify some date and the responses will contain phases 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 phases 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 phases 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 phases that match the given date.
You can use this param to specify some date and the responses will contain phases whose date are less than the given date.
You can use this param to specify some date and the responses will contain phases 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 phases 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 phases whose date are greater than the given phases created date.
You can use this param to provide an epoch milli value and the responses will contain exact matches of phases that match the given phases created date.
You can use this param to provide an epoch milli value and the responses will contain phases whose date are less than the given phases created date.
You can use this param to provide an epoch milli value and the responses will contain phases whose date are greater than or equal to the given phases created date.
You can use this param to provide an epoch milli value and the responses will contain phases whose date are less than or equal to the given phases created date.
You can use this param to provide an epoch milli value and the responses will contain phases whose date are greater than the given phases updated date.
You can use this param to provide an epoch milli value and the responses will contain exact matches of phases that match the given phases updated date.
You can use this param to provide an epoch milli value and the responses will contain phases whose date are less than the given phases updated date.
You can use this param to provide an epoch milli value and the responses will contain phases whose date are greater than or equal to the given phases updated date.
You can use this param to provide an epoch milli value and the responses will contain phases whose date are less than or equal to the given phases updated date.
You can use this param to specify some phase name and the responses will contain exact matches of phases that match the given name.
You can use this param to specify some phase name and the responses will contain matches of phases that match the given name.
You can use this param to specify some phase name and the responses will not contain matches of phases that match the given name.
Response
The requested action was successfully executed.
Example response
{
"data": [
{
"phaseId": 201,
"phaseName": "Kick off",
"project": {
"projectId": 201,
"projectName": "Acme onboarding"
},
"startDate": "2023-03-28",
"dueDate": "2023-03-28",
"startDateActual": "2023-03-28",
"dueDateActual": "2023-03-28",
"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"
},
"status": {
"value": 2,
"label": "In progress"
},
"private": true
}
],
"pagination": {
"pageSize": 100,
"hasMore": true,
"totalRecordCount": 10398,
"nextPage": "https://api.rocketlane.com/api/1.0/phases?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"
}
}