Todoist · Rate Limits

Todoist Rate Limits

Todoist's developer documentation acknowledges rate limits exist and references a "Request limits" section, but exact per-second/per-minute thresholds are not exposed in the public reference. The OAuth dynamic client registration and metadata document endpoints are explicitly described as rate limited per caller. The API returns standard 429/500/503 status codes. Per-account/per-token limits apply; consult the live docs or response headers for the authoritative numbers.

Todoist Rate Limits is the machine-readable rate-limit profile for Todoist on the APIs.io network, in the API Commons Rate Limits shape.

It captures 3 rate-limit definitions, measuring varies.

An exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled, serverError, and serviceUnavailable.

Tagged areas include Productivity, Tasks, Task Management, Collaboration, and Rate Limiting.

3 Limits Exhausted: HTTP 429
Method: generated, dated 2026-05-05.
Written by API Evangelist on 2026-05-05 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
ProductivityTasksTask ManagementCollaborationRate Limiting

Limits

Sync & REST API request limits account
varies
see https://developer.todoist.com/api/v1 (Request limits section)
Documentation references a Request Limits section; exact RPS/RPM values not published in the public OpenAPI reference. Limits scope to the authenticated user/account.
OAuth dynamic client registration caller
varies
rate limited per caller
/oauth/register rejects too many registrations in a short period; retry later.
OAuth client metadata document fetch caller
varies
rate limited per caller
Too many metadata document fetches in a short period are rejected.

Policies

Standard 429 Handling
A 429 Too Many Requests response indicates the user has sent too many requests in a given amount of time; clients should back off before retrying.
Refresh Token Rotation
Refresh tokens are rotated on every successful refresh, with a 60-second grace window to distinguish legitimate retries from replay attempts.
Consult Response Headers
Because exact thresholds are not published, applications should observe rate-limit headers on responses and treat any 429 as authoritative for their account.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/todoist-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.