Toggl Track API v9 uses a sliding-window quota per user per organisation: 30 requests per hour on Free, 240 on Starter and 600 on Premium (as of Nov 2026), with custom quotas on Enterprise. User-specific calls such as /me get 30 per hour on every plan. A separate leaky bucket allows about 1 request per second.
Toggl runs two limits at once
Most APIs have one rate limit. Toggl Track has two, and each returns a different error. An hourly quota counts your requests over a sliding window and returns HTTP 402 when you run out. A leaky bucket stops short bursts and returns HTTP 429. Knowing which one you've hit tells you how long to wait.
| Request type | Limit | Scope |
|---|---|---|
| Organisation-specific (reports, time entries, projects) | 30 per hour | Per user per organisation, Free plan (as of Nov 2026) |
| Organisation-specific | 240 per hour | Per user per organisation, Starter plan |
| Organisation-specific | 600 per hour | Per user per organisation, Premium plan |
| Organisation-specific | Custom quotas | Enterprise plans |
| User-specific, such as /me | 30 per hour | Per user, all plans |
| Burst safeguard | About 1 request per second | Per API token per IP |
The hourly quota and HTTP 402
The quota is per user per organisation, so one person has different quotas in different organisations. When it runs out, the API returns 402 and the client must wait before trying again. Two response headers help: X-Toggl-Quota-Remaining shows how many requests are left, and X-Toggl-Quota-Resets-In shows the seconds until the window resets. Read them on every response and you'll never be surprised.
A 402 doesn't always mean the quota, though. It can also mean the workspace needs an upgrade to use a particular feature. If you get a 402 on your very first call to an endpoint, check the plan before you check the quota.
The leaky bucket and HTTP 429
The second limit protects against bursts. When the bucket's full, the request gets 429 and the client must wait until it empties. Toggl says a safe pace is 1 request per second, applied per API token per IP. On a 429, Toggl advises backing off for a few minutes. On 5xx errors, it suggests a random delay before retrying.
The /me cap nobody can raise
Toggl Engineering's API overview spells out the trap. User-specific requests, such as the /me endpoint, are limited to 30 per hour per user regardless of plan, and no higher quotas are offered. An integration that calls /me before every action will hit that wall fast, even on Enterprise. Call /me once, store the result, and reuse it.
A worked example: a nightly export
Say you run a Starter workspace and want a script to pull each day's time entries into a spreadsheet. That's organisation-specific, so you get 240 requests an hour. Pulling a day's entries for ten people, plus their projects, might take 20 or 30 calls. Spaced at one a second, that's well under a minute and nowhere near the quota.
Now imagine the script calls /me at the start of each person's export. Ten calls to /me is fine. But if it runs every few minutes through the day, those calls add up toward the 30-per-hour cap, and the export fails partway with a 402. The fix is to call /me once per run.
Writing friendlier requests
- Send JSON only, since the API accepts only JSON requests.
- When updating, send only the fields that changed.
- Newly created entities may take 2 to 5 seconds to appear in the session, so allow up to 3 retries before treating something as missing.
If your script polls Toggl just to spot changes, see my explainer on APIs and webhooks for when a webhook saves you requests.
How Clockify counts requests
Clockify's API limits depend on workspace plan and are counted per workspace. It lists 30 requests per hour on its free tier and 20 requests per second on Basic, Standard and Pro (as of Nov 2026). For more options, see my roundup of Toggl alternatives.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
My advice for Toggl integrations
Pace calls at one a second, read the quota headers on every response, and cache /me. Treat 402 as either the quota or a feature lock, and 429 as a signal to back off for a few minutes. If you need more than Premium's hourly quota, Enterprise custom quotas are the only route.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.
Frequently asked questions
What's the Toggl Track API rate limit?
It depends on plan: 30, 240 or 600 requests per hour per user per organisation, plus about 1 request per second.
What does HTTP 402 mean?
You've hit the quota, or the workspace needs an upgrade for that feature.
What does HTTP 429 mean?
The leaky bucket is full. Back off for a few minutes.
Can the limit be raised?
Enterprise plans can have custom quotas; /me calls can't be raised.
How do I see my remaining quota?
Read X-Toggl-Quota-Remaining and X-Toggl-Quota-Resets-In.
