Toggl APIConnect Toggl without building on its API
Toggl has a REST API. Self-serve for any Toggl Track user, with request quotas set by plan. If you're reading the docs because you need Toggl 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 Toggl and your other tools.
- APIREST (JSON)
- AuthAPI token
- AccessSelf-serve
What the Toggl API gives you
- Type
- REST (JSON)
- Authentication
- API token (or email/password) over HTTP Basic auth
- Who can get access
- Self-serve for any Toggl Track user, with request quotas set by plan.
- What it covers
- Time entries, projects, clients, tags, workspaces, organizations, reports, and webhooks.
- Limits
- Organization requests are capped per user per hour at 30 (Free), 240 (Starter), and 600 (Premium), with custom limits on Enterprise and a roughly 1 req/sec leaky-bucket safeguard.
Official docs: engineering.toggl.com. Checked September 2026. Vendors change access terms, so confirm with Toggl before you build.
Building on the Toggl API vs. having Caddi run it
| The job | Build it on the API | With Caddi |
|---|---|---|
| Getting access | Register an app, get Toggl credentials, and manage tokens and refreshes. | Connect your Toggl 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 Toggl 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 Toggl work off someone's desk, the build is the slow part.
What teams usually want the Toggl API for
Toggl-to-invoice
Caddi pulls billable hours from Toggl each cycle, applies the team's rate and write-off rules, and creates the invoice in QuickBooks or Xero with the supporting time detail attached.
Matter-level time rollup
Caddi rolls up Toggl hours by client and matter, maps them to the right task codes, and writes draft time entries into Clio for billing review.
Time review approval flow
Caddi posts each manager's review queue to Slack or email, captures approvals, and locks the approved entries in Toggl before they hit a bill.
Toggl API questions
Does Toggl have an API?
Yes. Toggl has a REST API, authenticated with API token (or email/password) over HTTP Basic auth. The official documentation is at https://engineering.toggl.com/docs/track/.
How do I get access to the Toggl API?
Self-serve for any Toggl Track user, with request quotas set by plan.
Does the Toggl API have rate limits?
Organization requests are capped per user per hour at 30 (Free), 240 (Starter), and 600 (Premium), with custom limits on Enterprise and a roughly 1 req/sec leaky-bucket safeguard.
Can I connect Toggl to my other tools without writing code against its API?
Yes. With Caddi you show the Toggl task once, the way you'd train a new hire, and Caddi builds it as verified code that runs across Toggl 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 Toggl with Caddi?
No. There is no integration code for you to write or maintain. Every automation Caddi builds for Toggl is reviewed before it runs in production, and every run is logged.
Connect Toggl without the build.
Drop your work email and pick a time. We'll show you Caddi running your Toggl workflow end to end.