Todoist API changes

1

Todoist has a new, integrated API that supercedes both their previous “REST” and “SYNC” APIs. At the moment, the shipping version of Drafts integrates using these old APIs. The old APIs will be phased out and shut down in early 2026, so I’m working on migrating Drafts’ integrations to use the new API – but wanted to give a heads up to anyone relying on custom Todoist actions that they may want to consider updating to support the new APIs.

Information on migration to the new API is available on Todoist’s site.

This is what I expect so far, based on my review, if you are using Todoist actions:

  • If you use Drafts’ “Todoist” action step in actions, the change will be invisible and those will just keep working.
  • If you are using custom Todoist actions that are scripted, the authors of these actions may need to update them to keep working before the old API shuts down in the Spring.

And what to know if you author Todoist actions:

  • If you scripted actions that use the convenience methods (like “getTasks”, “getProjects”, etc.) provided by Drafts’ Todoist script object, these scripts may need review. The new results objects have changed slightly.
  • If you use scripted actions that use the request method on the Todoist object, you provide a full endpoint URL to the calls, and these will need to be migrated to the endpoints of the new API. They will continue to work as-is until Todoist actually shuts down the old API, but can be migrated now. In most cases that will just mean changing the endpoint URL you pass from the old https://api.todoist.com/rest/v2/ API to the equivalent endpoint under the https://api.todoist.com/api/v1 API, and reviewing the results changes. For the most part, these changes related to the addition of paginated results.

Let me know if you have any questions about these changes.

1 Like