Checklists
The Checklists API manages checklist items that belong to a parent resource (for example a task or a project), plus their status, ordering and comments.New to the API? Start with Getting started (base URL, response envelope, errors, pagination) and Authentication (API keys). Those conventions apply to every endpoint below and are not repeated here.
Identifier note: checklist items are addressed by their numericchecklist_id. Each item belongs to a parent identified bychecklistresource_type+checklistresource_id(e.g.task/123). Listing is always scoped to a parent.
The checklist object
| Field | Type | Notes |
|---|---|---|
id | integer | Checklist item id. Used in all URLs. |
text | string | The checklist item text. |
status | string | pending or completed. |
position | integer | Manual sort order within the parent. |
resource | object | The parent: { type, id }. |
comments_count | integer | Number of comments on the item. |
dates | object | created, updated. |
List / search checklists
resource_type and resource_id are required. The list
response includes a meta.progress summary for the parent’s full checklist set.
Query parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
resource_type | string | yes | Parent type (e.g. task, project). |
resource_id | integer | yes | Parent id. |
sort | string | no | checklist_position (default), checklist_status, checklist_created. |
order | string | no | asc (default) or desc. |
limit | integer | no | Results per page (max 100). |
page | integer | no | Page number. |
Example request
Example response — 200 OK
Get a checklist
200) with message “Checklist retrieved successfully.”
Create a checklist item
Body parameters
| Parameter | Type | Required | Notes |
|---|---|---|---|
checklistresource_type | string | yes | Parent type (e.g. task, project). |
checklistresource_id | integer | yes | Parent id. |
checklist_text | string | yes | The item text. |
Example request
Example response — 201 Created
Update a checklist item
| Parameter | Type | Required | Notes |
|---|---|---|---|
checklist_text | string | yes | The new item text. |
200) with message “Checklist updated successfully.”
Delete a checklist item
Example response — 200 OK
Change status
| Parameter | Type | Required | Notes |
|---|---|---|---|
status | string | yes | pending or completed. |
200) with message “Checklist status updated successfully.”
Reorder checklist items
| Parameter | Type | Required | Notes |
|---|---|---|---|
checklist_ids | array of integers | yes | Checklist ids in the desired order. |
Example response — 200 OK
Comments
A checklist item can have comments.List comments
{ "data": [ { "id": 9, "text": "...", "creator": { "id": 1, "name": "Admin" } } ], "message": "..." }.
Add a comment
| Parameter | Type | Required | Notes |
|---|---|---|---|
comment | string | yes | The comment text. |
201) with message “Checklist comment added successfully.”
Delete a comment
{ "data": { "id": 9 }, "message": "Checklist comment deleted successfully." }.
Errors
See Getting started for the shared error format. Checklist-specific:| Status | Meaning |
|---|---|
404 Not Found | The checklist (or comment) id does not exist. |
422 Unprocessable Entity | Validation failed (e.g. missing resource_type/resource_id on list, missing checklist_text, or an invalid status). |