openapi: 3.0.1
info:
title: Rocketlane Comments Tasks API
description: Rocketlane API
version: '1.0'
servers:
- url: https://api.rocketlane.com/api
description: Production
- url: https://api.nitro.run/api
description: Staging
- url: https://project.api.orbits.run/api
description: Orbits
security:
- api-key:
- 'read : write'
tags:
- name: Tasks
description: Endpoints for tasks resource
paths:
/1.0/tasks/{taskId}:
get:
tags:
- Tasks
summary: Get task by Id
operationId: get-task
parameters:
- name: taskId
in: path
description: The task's unique, system-generated identifier, which can be used to identify the task globally.
required: true
schema:
minimum: 0
type: integer
format: int64
default: 1
example: 200
- name: includeFields
in: query
description: 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.
required: false
style: form
explode: false
schema:
type: array
items:
type: string
enum:
- startDateActual
- dueDateActual
- type
- phase
- assignees
- followers
- dependencies
- billable
- csatEnabled
- priority
- timeEntryCategory
- financialsBudget
- taskPrivateNote
- parent
- externalReferenceId
- name: includeAllFields
in: query
description: 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.
required: false
schema:
type: boolean
example: true
responses:
'200':
description: The requested action was successfully executed.
content:
application/json:
schema:
$ref: '#/components/schemas/TaskPublicAPIResponseEntity'
'400':
description: This error typically happens when the request payload contains an error. If you want to make sure that the request's parameters are named correctly and are the right data types, you can examine the request's syntax.
content:
application/json:
schema:
$ref: '#/components/schemas/badRequestErrorlist'
'401':
description: You see this error when trying to access this resource without being authenticated. Check the API request header to make sure it is not empty and has a valid api-key that you acquired from the Rocketlane API Settings tab.
content:
application/json:
schema:
$ref: '#/components/schemas/unauthorizedErrorlist'
'404':
description: If we were unable to locate the resource you were looking for or the proper API endpoint you were looking for, this error would show up.
content:
application/json:
schema:
$ref: '#/components/schemas/notFoundErrorlist'
put:
tags:
- Tasks
summary: Update task by Id
operationId: update-task
parameters:
- name: taskId
in: path
description: The task's unique, system-generated **identifier**, which can be used to identify the task globally
required: true
schema:
minimum: 0
type: integer
format: int64
default: 1
example: 200
- name: includeFields
in: query
description: 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.
required: false
style: form
explode: false
schema:
type: array
items:
type: string
enum:
- startDateActual
- dueDateActual
- type
- phase
- assignees
- followers
- dependencies
- billable
- csatEnabled
- priority
- timeEntryCategory
- financialsBudget
- taskPrivateNote
- parent
- externalReferenceId
- name: includeAllFields
in: query
description: 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.
required: false
schema:
type: boolean
example: true
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/TaskPublicUpdateAPIRequestEntity'
responses:
'200':
description: The requested action was successfully executed.
content:
application/json:
schema:
$ref: '#/components/schemas/TaskPublicAPIResponseEntity'
'400':
description: This error typically happens when the request payload contains an error. If you want to make sure that the request's parameters are named correctly and are the right data types, you can examine the request's syntax.
content:
application/json:
schema:
$ref: '#/components/schemas/badRequestErrorlist'
'401':
description: You see this error when trying to access this resource without being authenticated. Check the API request header to make sure it is not empty and has a valid api-key that you acquired from the Rocketlane API Settings tab.
content:
application/json:
schema:
$ref: '#/components/schemas/unauthorizedErrorlist'
'404':
description: If we were unable to locate the resource you were looking for or the proper API endpoint you were looking for, this error would show up.
content:
application/json:
schema:
$ref: '#/components/schemas/notFoundErrorlist'
'500':
description: This error denotes that there is an error that occured within our servers. The response body could help narrow down the cause for the error by our support team.
content:
application/json:
schema:
$ref: '#/components/schemas/serverErrorErrorlist'
delete:
tags:
- Tasks
summary: Delete task by Id
operationId: delete-task
parameters:
- name: taskId
in: path
description: The ID of the task object
required: true
schema:
minimum: 0
type: integer
format: int64
default: 1
example: 200
responses:
'204':
description: The resource was successfully removed from the database.
content:
application/json:
schema:
type: string
'400':
description: This error typically happens when the request payload contains an error. If you want to make sure that the request's parameters are named correctly and are the right data types, you can examine the request's syntax.
content:
application/json:
schema:
$ref: '#/components/schemas/badRequestErrorlist'
'401':
description: You see this error when trying to access this resource without being authenticated. Check the API request header to make sure it is not empty and has a valid api-key that you acquired from the Rocketlane API Settings tab.
content:
application/json:
schema:
$ref: '#/components/schemas/unauthorizedErrorlist'
'404':
description: If we were unable to locate the resource you were looking for or the proper API endpoint you were looking for, this error would show up.
content:
application/json:
schema:
$ref: '#/components/schemas/notFoundErrorlist'
/1.0/tasks/{taskId}/remove-followers:
post:
tags:
- Tasks
summary: Remove followers from a task by Id
operationId: remove-followers-from-task
parameters:
- name: taskId
in: path
description: The task's unique, system-generated **identifier**, which can be used to identify the task globally
required: true
schema:
minimum: 0
type: integer
format: int64
default: 1
example: 200
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/TaskAddFollowersPublicRequest'
responses:
'200':
description: The requested action was successfully executed.
content:
application/json:
schema:
$ref: '#/components/schemas/TaskPublicAssigneeAPIResponseEntity'
'400':
description: This error typically happens when the request payload contains an error. If you want to make sure that the request's parameters are named correctly and are the right data types, you can examine the request's syntax.
content:
application/json:
schema:
$ref: '#/components/schemas/badRequestErrorlist'
'401':
description: You see this error when trying to access this resource without being authenticated. Check the API request header to make sure it is not empty and has a valid api-key that you acquired from the Rocketlane API Settings tab.
content:
application/json:
schema:
$ref: '#/components/schemas/unauthorizedErrorlist'
'404':
description: If we were unable to locate the resource you were looking for or the proper API endpoint you were looking for, this error would show up.
content:
application/json:
schema:
$ref: '#/components/schemas/notFoundErrorlist'
/1.0/tasks/{taskId}/remove-dependencies:
post:
tags:
- Tasks
summary: Remove dependencies from a task by Id
operationId: remove-dependencies-from-task
parameters:
- name: taskId
in: path
description: The task's unique, system-generated **identifier**, which can be used to identify the task globally
required: true
schema:
minimum: 0
type: integer
format: int64
default: 1
example: 200
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/TaskDependencyPublicAPI'
responses:
'200':
description: The requested action was successfully executed.
content:
application/json:
schema:
$ref: '#/components/schemas/TaskPublicDependenciesAPIResponseEntity'
'400':
description: This error typically happens when the request payload contains an error. If you want to make sure that the request's parameters are named correctly and are the right data types, you can examine the request's syntax.
content:
application/json:
schema:
$ref: '#/components/schemas/badRequestErrorlist'
'401':
description: You see this error when trying to access this resource without being authenticated. Check the API request header to make sure it is not empty and has a valid api-key that you acquired from the Rocketlane API Settings tab.
content:
application/json:
schema:
$ref: '#/components/schemas/unauthorizedErrorlist'
'404':
description: If we were unable to locate the resource you were looking for or the proper API endpoint you were looking for, this error would show up.
content:
application/json:
schema:
$ref: '#/components/schemas/notFoundErrorlist'
/1.0/tasks/{taskId}/remove-assignees:
post:
tags:
- Tasks
summary: Remove assignees from a task by Id
operationId: remove-assignees-from-task
parameters:
- name: taskId
in: path
description: The task's unique, system-generated **identifier**, which can be used to identify the task globally
required: true
schema:
minimum: 0
type: integer
format: int64
default: 1
example: 200
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/TaskAssigneePublicRequestAPI'
responses:
'200':
description: The requested action was successfully executed.
content:
application/json:
schema:
$ref: '#/components/schemas/TaskPublicAssigneeAPIResponseEntity'
'400':
description: This error typically happens when the request payload contains an error. If you want to make sure that the request's parameters are named correctly and are the right data types, you can examine the request's syntax.
content:
application/json:
schema:
$ref: '#/components/schemas/badRequestErrorlist'
'401':
description: You see this error when trying to access this resource without being authenticated. Check the API request header to make sure it is not empty and has a valid api-key that you acquired from the Rocketlane API Settings tab.
content:
application/json:
schema:
$ref: '#/components/schemas/unauthorizedErrorlist'
'404':
description: If we were unable to locate the resource you were looking for or the proper API endpoint you were looking for, this error would show up.
content:
application/json:
schema:
$ref: '#/components/schemas/notFoundErrorlist'
/1.0/tasks/{taskId}/move-phase:
post:
tags:
- Tasks
summary: Move a task to the phase by Id
operationId: move-task-to-given-phase
parameters:
- name: taskId
in: path
description: The task's unique, system-generated **identifier**, which can be used to identify the task globally
required: true
schema:
minimum: 0
type: integer
format: int64
default: 1
example: 200
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/MovePhasePublicAPI'
responses:
'200':
description: The requested action was successfully executed.
content:
application/json:
schema:
$ref: '#/components/schemas/TaskPublicMovePhaseAPIResponseEntity'
'400':
description: This error typically happens when the request payload contains an error. If you want to make sure that the request's parameters are named correctly and are the right data types, you can examine the request's syntax.
content:
application/json:
schema:
$ref: '#/components/schemas/badRequestErrorlist'
'401':
description: You see this error when trying to access this resource without being authenticated. Check the API request header to make sure it is not empty and has a valid api-key that you acquired from the Rocketlane API Settings tab.
content:
application/json:
schema:
$ref: '#/components/schemas/unauthorizedErrorlist'
'404':
description: If we were unable to locate the resource you were looking for or the proper API endpoint you were looking for, this error would show up.
content:
application/json:
schema:
$ref: '#/components/schemas/notFoundErrorlist'
/1.0/tasks/{taskId}/add-followers:
post:
tags:
- Tasks
summary: Add followers to a task by Id
operationId: add-followers-to-task
parameters:
- name: taskId
in: path
description: The task's unique, system-generated **identifier**, which can be used to identify the task globally
required: true
schema:
minimum: 0
type: integer
format: int64
default: 1
example: 200
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/TaskAddFollowersPublicRequest'
responses:
'200':
description: The requested action was successfully executed.
content:
application/json:
schema:
$ref: '#/components/schemas/TaskPublicAssigneeAPIResponseEntity'
'400':
description: This error typically happens when the request payload contains an error. If you want to make sure that the request's parameters are named correctly and are the right data types, you can examine the request's syntax.
content:
application/json:
schema:
$ref: '#/components/schemas/badRequestErrorlist'
'401':
description: You see this error when trying to access this resource without being authenticated. Check the API request header to make sure it is not empty and has a valid api-key that you acquired from the Rocketlane API Settings tab.
content:
application/json:
schema:
$ref: '#/components/schemas/unauthorizedErrorlist'
'404':
description: If we were unable to locate the resource you were looking for or the proper API endpoint you were looking for, this error would show up.
content:
application/json:
schema:
$ref: '#/components/schemas/notFoundErrorlist'
/1.0/tasks/{taskId}/add-dependencies:
post:
tags:
- Tasks
summary: Add dependencies to a task by Id
operationId: add-dependencies-to-task
parameters:
- name: taskId
in: path
description: The task's unique, system-generated **identifier**, which can be used to identify the task globally
required: true
schema:
minimum: 0
type: integer
format: int64
default: 1
example: 200
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/TaskDependencyPublicAPI'
responses:
'200':
description: The requested action was successfully executed.
content:
application/json:
schema:
$ref: '#/components/schemas/TaskPublicDependenciesAPIResponseEntity'
'400':
description: This error typically happens when the request payload contains an error. If you want to make sure that the request's parameters are named correctly and are the right data types, you can examine the request's syntax.
content:
application/json:
schema:
$ref: '#/components/schemas/badRequestErrorlist'
'401':
description: You see this error when trying to access this resource without being authenticated. Check the API request header to make sure it is not empty and has a valid api-key that you acquired from the Rocketlane API Settings tab.
content:
application/json:
schema:
$ref: '#/components/schemas/unauthorizedErrorlist'
'404':
description: If we were unable to locate the resource you were looking for or the proper API endpoint you were looking for, this error would show up.
content:
application/json:
schema:
$ref: '#/components/schemas/notFoundErrorlist'
/1.0/tasks/{taskId}/add-assignees:
post:
tags:
- Tasks
summary: Add assignees to a task by Id
operationId: add-assignee-to-task
parameters:
- name: taskId
in: path
description: The task's unique, system-generated **identifier**, which can be used to identify the task globally
required: true
schema:
minimum: 0
type: integer
format: int64
default: 1
example: 200
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/TaskAssigneePublicRequestAPI'
responses:
'200':
description: The requested action was successfully executed.
content:
application/json:
schema:
$ref: '#/components/schemas/TaskPublicAssigneeAPIResponseEntity'
'400':
description: This error typically happens when the request payload contains an error. If you want to make sure that the request's parameters are named correctly and are the right data types, you can examine the request's syntax.
content:
application/json:
schema:
$ref: '#/components/schemas/badRequestErrorlist'
'401':
description: You see this error when trying to access this resource without being authenticated. Check the API request header to make sure it is not empty and has a valid api-key that you acquired from the Rocketlane API Settings tab.
content:
application/json:
schema:
$ref: '#/components/schemas/unauthorizedErrorlist'
'404':
description: If we were unable to locate the resource you were looking for or the proper API endpoint you were looking for, this error would show up.
content:
application/json:
schema:
$ref: '#/components/schemas/notFoundErrorlist'
/1.0/tasks:
get:
tags:
- Tasks
summary: Get all tasks
operationId: get-all-tasks
parameters:
- name: pageSize
in: query
description: 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.
schema:
minimum: 0
type: number
format: int32
example: 100
- name: pageToken
in: query
description: 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.
schema:
type: string
example: 59c12a42-dd10-11ed-afa1-0242ac120002
- name: includeFields
in: query
description: 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.
style: form
explode: false
schema:
type: array
items:
type: string
enum:
- startDateActual
- dueDateActual
- type
- phase
- assignees
- followers
- dependencies
- billable
- csatEnabled
- priority
- timeEntryCategory
- financialsBudget
- taskPrivateNote
- parent
- externalReferenceId
- name: includeAllFields
in: query
description: 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.
schema:
type: boolean
example: true
- name: sortBy
in: query
description: You can use the sortBy param to sort the responses by the given field.
schema:
type: string
enum:
- taskName
- startDate
- dueDate
- startDateActual
- dueDateActual
- name: sortOrder
in: query
description: The sortOrder param can be used to specify the sorting order, which can be Ascending (ASC) or Descending (DESC). Descending is the default option.
schema:
type: string
enum:
- ASC
- DESC
- name: match
in: query
description: You can use the match param to specify if we need to filter the entries using either AND(all) / OR(any). Defaults to AND.
schema:
type: string
enum:
- all
- any
- name: startDate.gt
in: query
description: You can use this param to specify some date and the responses will contain tasks whose date are greater than the given date.
schema:
type: string
example: '2023-03-28'
- name: startDate.eq
in: query
description: You can use this param to specify some date and the responses will contain exact matches of tasks that match the given date.
schema:
type: string
example: '2023-03-28'
- name: startDate.lt
in: query
description: You can use this param to specify some date and the responses will contain tasks whose date are less than the given date.
schema:
type: string
example: '2023-03-28'
- name: startDate.ge
in: query
description: 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.
schema:
type: string
example: '2023-03-28'
- name: startDate.le
in: query
description: 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.
schema:
type: string
example: '2023-03-28'
- name: dueDate.gt
in: query
description: You can use this param to specify some date and the responses will contain tasks whose date are greater than the given date.
schema:
type: string
example: '2023-03-28'
- name: dueDate.eq
in: query
description: You can use this param to specify some date and the responses will contain exact matches of tasks that match the given date.
schema:
type: string
example: '2023-03-28'
- name: dueDate.lt
in: query
description: You can use this param to specify some date and the responses will contain tasks whose date are less than the given date.
schema:
type: string
example: '2023-03-28'
- name: dueDate.ge
in: query
description: 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.
schema:
type: string
example: '2023-03-28'
- name: dueDate.le
in: query
description: 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.
schema:
type: string
example: '2023-03-28'
- name: startDateActual.gt
in: query
description: You can use this param to specify some date and the responses will contain tasks whose date are greater than the given date.
schema:
type: string
example: '2023-03-28'
- name: startDateActual.eq
in: query
description: You can use this param to specify some date and the responses will contain exact matches of tasks that match the given date.
schema:
type: string
example: '2023-03-28'
- name: startDateActual.lt
in: query
description: You can use this param to specify some date and the responses will contain tasks whose date are less than the given date.
schema:
type: string
example: '2023-03-28'
- name: startDateActual.ge
in: query
description: 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.
schema:
type: string
example: '2023-03-28'
- name: startDateActual.le
in: query
description: 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.
schema:
type: string
example: '2023-03-28'
- name: dueDateActual.gt
in: query
description: You can use this param to specify some date and the responses will contain tasks whose date are greater than the given date.
schema:
type: string
example: '2023-03-28'
- name: dueDateActual.eq
in: query
description: You can use this param to specify some date and the responses will contain exact matches of tasks that match the given date.
schema:
type: string
example: '2023-03-28'
- name: dueDateActual.lt
in: query
description: You can use this param to specify some date and the responses will contain tasks whose date are less than the given date.
schema:
type: string
example: '2023-03-28'
- name: dueDateActual.ge
in: query
description: 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.
schema:
type: string
example: '2023-03-28'
- name: dueDateActual.le
in: query
description: 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.
schema:
type: string
example: '2023-03-28'
- name: createdAt.gt
in: query
description: 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.
schema:
type: integer
format: int64
example: 1625164800000
- name: createdAt.eq
in: query
description: 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.
schema:
type: integer
format: int64
example: 1625164800000
- name: createdAt.lt
in: query
description: 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.
schema:
type: integer
format: int64
example: 1625164800000
- name: createdAt.ge
in: query
description: 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.
schema:
type: integer
format: int64
example: 1625164800000
- name: createdAt.le
in: query
description: 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.
schema:
type: integer
format: int64
example: 1625164800000
- name: updatedAt.gt
in: query
description: 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.
schema:
type: integer
format: int64
example: 1625164800000
# --- truncated at 32 KB (98 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/rocketlane/refs/heads/main/openapi/rocketlane-tasks-api-openapi.yml