Public API

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

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 .

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

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

I would like to search existing tasks with name and add if the task not found. As of now there is no way to search existing tasks with name.

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.

I'd like to use DraftsApp (or other deeplink crafting) to add tasks, notes & ambiguous markdown to taskade. This is definitely a power user feature so I'd be okay with using long node_ids and a number of required querystring parameters Right now I'm aware taskade:// will open the app on iOS, iPad. My request is to include documentation on this for power users (with warning its likely to change if it's not a finalized or public API) for taskade://paths... and/or taskade://...?args... I could include in a querystring to construct a URI that would then add what I passed to it into taskade they be documented. If it doesn't exist beyond taskade:// being registered (to just open the app). Some thoughts I have which would be nifty are: create a project providing markdown in a querystring paramater as a blob (no limit to how much text a querystring can contain) taskade://new?markdown=... or with a specific title taskade://new?title=My%20Project&markdown=... or with tasks/bullets/paragraphs taskade://new?title=My%20Project&tasks=One%0ATwo%0AThird%20Task&bullets=One%0ATwo%0AThree&paragraphs=%0A%0AParagraph%20with%20two%20new%20lines%20above%20and%20below%0A%0A add task/bullets/paragraph/markdown as a child to a specific node_id with an optional querystring paramter to indicate whether it should be top or bottom (defaults to bottom if not present) taskade://add/<node_id>?top&tasks=One%0ATwo%0AThird%20Task&bullets=One%0ATwo%0AThree&paragraphs=%0A%0AParagraph%20with%20two%20new%20lines%20above%20and%20below%0A%0A add task/bullets/paragraph/markdown as a sibling(s) to a specific node_id , with an optional querystring parameter to indicate whether it should be above or below taskade://add/sibling/<node_id>?above&tasks=One%0ATwo%0AThird%20Task&bullets=One%0ATwo%0AThree&paragraphs=%0A%0AParagraph%20with%20two%20new%20lines%20above%20and%20below%0A%0A Adding things is sufficient enough for me, while I'm assuming if I provide a specific node_id I don't need to say which project/block_title it's under.

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

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/ )