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

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

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.

A small quirk between documentation and an endpoint I was playing with, I didn't do a deep investigation to see if this difference occurs for all DELETE routes The DELETE /projects/{projectId}/tasks/{taskId} doesn't return the expanded item in response, it'll return { "ok": true, "item": null } screenshots are of the expected response shape from the OpenAPI Playground at https://www.taskade.com/api/documentation/static/index.html#/Task/taskDelete and https://developers.taskade.com/docs/api/tasks gitbook

Figure I'd mention another quirk, although in practice it wouldn't matter that much While PUT /projects/{projectId}/tasks/{taskId}/date accepts a JSON body with two keys of start and stop , they're read differently. You must include seconds in a start.time , like 16:12:00 , while an end.time doesn't care, and both 18:12 and 18:12:00 will be parsed correctly, and be the same time. Another quirk is that the GitBook docs don't explain what format each field is expecting (1st screenshot) https://developers.taskade.com/docs/api/tasks/date While the OpenAPI playground page shows the expected format, however it's got a few problems (2nd screenshot) and body snippet copied below https://www.taskade.com/api/documentation/static/index.html#/Task/taskPutDate The first part of the quirk of the OpenAPI example body sometimes shows seconds on the end.time key, but it only fails if it's not included on the start.time key. The other is that these dates are wayyyy off into the future. Other times it will show seconds on start.time , the values are faked, or mocked which makes sense. It's a superficial issue, but I figured I include it since I wasn't sure if I was supposed to use some other calendar at first, when I started to get errors for not including seconds in start.time :P from the OpenAPI Playground Example Body - different than the screenshot, and sometimes it will render a start.time with seconds, it's random: { "start": { "date": "8692-82-26", "time": "23:44", "timezone": "string" }, "end": { "date": "5809-32-83", "time": "21:56:45", "timezone": "string" } } The error when not including :SS on start.time is the 3rd screenshot and is like: HTTP 500 { "ok": false }

Not sure if this is necessarily required. I don't have a use case other than hiding them or not listing them with my toy CLI. (Most of my use cases only require a single project and a place on the project after::taskId at the moment.) If I were to list all workspaces / folders it may be useful to know if the folder is Archived, so I skip fetching them and displaying them to the user for selecting from their familiar taxonomy of Workspace -> Folder -> Project.

I don't have a use case for this at the moment, other than thinking about whether or not to show projects in a listing for the user to select. It would be helpful to include a completed property on the project. While writing this suggestion I noticed the path to the "completed" projects in a folder is actually under /archive , like /spaces/WORKSPACE_ID/subspaces/FOLDER_ID/archive so this might relate to another suggestion, asking for exposing the archive property on Folders and Workspaces, for a similar reason (not showing to the user when listing): https://www.taskade.com/feedback/public-api/p/the-archived-property-on-folders-workspaces