Todoist APIConnect Todoist without building on its API
Todoist has a REST API. Self-serve for any Todoist user or developer. If you're reading the docs because you need Todoist to talk to the rest of your stack, Caddi does that without you writing or maintaining integration code: you show it the job once, and it runs it across Todoist and your other tools.
- APIREST (JSON)
- AuthPersonal API token or OAuth 2.0
- AccessSelf-serve
What the Todoist API gives you
- Type
- REST (JSON)
- Authentication
- Personal API token or OAuth 2.0
- Who can get access
- Self-serve for any Todoist user or developer.
- What it covers
- Tasks, projects, sections, labels, filters, comments, reminders, workspaces, and collaborators.
- Limits
- Per user: 1,000 partial-sync requests and 100 full-sync requests per 15 minutes.
Official docs: developer.todoist.com. Checked September 2026. Vendors change access terms, so confirm with Todoist before you build.
Building on the Todoist API vs. having Caddi run it
| The job | Build it on the API | With Caddi |
|---|---|---|
| Getting access | Register an app, get Todoist credentials, and manage tokens and refreshes. | Connect your Todoist account once. Caddi holds the connection. |
| Writing the integration | A developer maps fields, handles pagination, retries and rate limits, and writes the sync. | You show Caddi the Todoist task the way you'd train a new hire. It writes verified code for it. |
| Steps the API doesn't cover | Screens with no endpoint stay manual, or need a separate RPA tool. | Caddi uses a secure, audited browser session where there's no API, in the same automation. |
| The other systems in the loop | Each extra tool is another API, another set of credentials, another integration to own. | One automation runs across all the tools the job touches. |
| Keeping it running | Someone owns the code when the API version, fields or your process change. | Every automation is reviewed before it runs in production, and every run is logged. |
Building on the API is the right call when you have engineers and the integration is your product. When the goal is getting Todoist work off someone's desk, the build is the slow part.
What teams usually want the Todoist API for
Email to task
Caddi reads the incoming email in Outlook and creates the matching Todoist task.
Assign to team
Caddi creates the Todoist task and assigns it, then notes it in Salesforce.
Notify the team
Caddi posts the right new Todoist task to the channel.
Todoist API questions
Does Todoist have an API?
Yes. Todoist has a REST API, authenticated with Personal API token or OAuth 2.0. The official documentation is at https://developer.todoist.com/api/v1/.
How do I get access to the Todoist API?
Self-serve for any Todoist user or developer.
Does the Todoist API have rate limits?
Per user: 1,000 partial-sync requests and 100 full-sync requests per 15 minutes.
Can I connect Todoist to my other tools without writing code against its API?
Yes. With Caddi you show the Todoist task once, the way you'd train a new hire, and Caddi builds it as verified code that runs across Todoist and the other tools the job touches. Where a step has no API, Caddi uses a secure, audited browser session in the same automation.
Do I need a developer to automate Todoist with Caddi?
No. There is no integration code for you to write or maintain. Every automation Caddi builds for Todoist is reviewed before it runs in production, and every run is logged.
Connect Todoist without the build.
Drop your work email and pick a time. We'll show you Caddi running your Todoist workflow end to end.