> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://support.toggl.com/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# API & Webhook limits

To keep Toggl Track fast, reliable, and scalable for everyone, **we’re introducing usage limits for our APIs and webhooks starting September 5th, 2025.** These changes help ensure fair access to our API infrastructure, protect system stability, and support ongoing improvements.

### **What’s changing**

**Webhooks (per workspace):**

* **Free:** 1 webhook (up to 3 events per webhook)
* **Starter:** 2 webhooks (up to 6 events per webhook)
* **Premium:** 3 webhooks (up to 12 events per webhook)

### **API Limits**

Our API limits are applied based on the type of request. There are two distinct limits:

#### **1. Workspace/Organization API Limits**

These limits apply to requests that point to a specific workspace or organization (e.g., fetching reports, time entries, or projects for a workspace). The API quota is determined by the Organization's subscription plan.

* **Free:** 30 requests per hour, per user, per organization
* **Starter:** 240 requests per hour, per user, per organization
* **Premium:** 600 requests per hour, per user, per organization

Higher, custom limits are available on **Enterprise** plans.

#### **2. User-Specific API Limits**

This limit applies to requests that are about your personal user data and are not targeting a specific workspace. For example, using the `https://api.track.toggl.com/api/v9/me` endpoint.

Requests of this nature will have a 30-request per hour limit per user for users on Free, Starter and Premium organizations. Users who are only members of an Enterprise organization will have unlimited user-specific limits.

#### **Understanding how API limits work**

Toggl employs a **sliding window algorithm** to enforce its API quotas. The count begins when the initial request is made and remains valid for 60 minutes. After 60 minutes, the count resets. When you reach your limit, the server responds with an **HTTP 402 status code**, indicating you should pause further requests.

**What you need to do**

* [**Review your current usage**](https://track.toggl.com/profile#api-token) and adjust your systems as needed.
* **Upgrade your plan** if your usage requires higher limits.
* **Implement exponential backoff** in your integrations to handle API limits efficiently (wait progressively longer between retries when encountering HTTP 402 responses).
* **Monitor for HTTP 402 responses** in your integration workflows and suspend additional requests temporarily when encountered.

**Optimizing your API usage** To minimize the likelihood of hitting API limits:

* **Reduce integration frequency**: Adjust external connectors like Zapier to make fewer API calls
* **Implement caching**: Store frequently accessed data within your own systems
* **Streamline automation**: Audit workflows to eliminate redundant or obsolete API calls

**Need more help or have ideas to share? Join our Community to connect with our team and other users — ask questions, share feedback, and help shape what comes next!**