Public API

I'd like to do the following via API: Prompt Agent and Receive Response Run Agent Command Add or Remove from Agent Knowledge Edit Agent Instructions Create/Edit/Delete Agent Commands

It would be nice if there was a POST /projects/{projectId}/complete similar to the POST /projects/{projectId}/tasks/{taskId}/complete for tasks. Here's my use case: https://pastebin.com/raw/7cYd8aGY

It would be nice if there was a details page for projects like GET /projects/{projectId} where it could show some more information about a project. For me it would be especially helpful if it showed tags . Here's my use case: https://pastebin.com/raw/7cYd8aGY

While not a big thing since there is a copy project feature, it would be nice if there was a way to create a project from a template. And of course it would therefore also be necessary to have an endpoint to list all templates. Here's my use case: https://pastebin.com/raw/7cYd8aGY

It would be nice if there was more information on projects listed via GET /folders/{folderId}/projects. Currently it seems to just be id and name. It would be especially useful for me it it listed tags . Here's my use case: https://pastebin.com/raw/7cYd8aGY

An additional route for a PUT /projects/{projectId}/tasks/{taskId}/note for adding a NOTE attachment to a task. This is hopefully a smaller request than implementing all items that can appear in the ➕ menu, assuming NOTE s (added with Shift + Enter) are like attachments too. This also builds off my request for editing a task body. I would be able to edit this note directly by replacing it. https://www.taskade.com/feedback/public-api/p/update-taskcontent-route I would also want to be able to GET /projects/{projectId}/tasks/{taskId}/note . For reading a task.note .

Would like to have a PUT /{taskId}/content (or eventually a PATCH /{taskId}/ ) route be available for updating atomically the task content. I understand there's a PUT pattern now for DATE s and ASSIGNEES , I think that would be fine pattern to adopting too, with a PUT /projects/{projectId}/tasks/{taskId}/content to update the content directly. To expand on mentioning PATCH routes, I think a PATCH would work at the root path of /projects/{projectId}/tasks/{taskId}/ , without any path indicating what we're updating on the task in the body ( content , assignee , [attachments] ...), and using what I see the API has now as the pattern going forward. I see the pattern as "PUT == create or update a /{piece} of item" (uses selection of item at .../collection/item/piece/ ) POST == create the whole item (uses root of item at .../collection/item/ ) PATCH == update a part of the already-created item (uses root of item at .../collection/item/ )

Add a route for grabbing a task due date, a GET /projects/{projectId}/tasks/{taskId}/date to add to the DELETE & PUT actions currently available for that route. Eventually including it in the GET /projects/{projectId}/tasks collection response and a GET /projects/projectId}/tasks/{taskId} item response would be nice too.

It would be great if there was a way to set an optional filter for tasks. For example .../tasks?completed=false to get all open tasks and not have to process them afterwards.

Also return the emoji icon and project color set on a project as a new endpoint or as an added field in the GET folders/{folderId}/projects endpoint.