Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
| 1 | --- |
| 2 | title: Rate Limits |
| 3 | description: Distinguish Composio API limits from provider quotas and recover from 429 errors |
| 4 | keywords: [API rate limits, rate limiting, throttling, 429 too many requests, API quotas, request limits, provider quotas, managed auth] |
| 5 | --- |
| 6 | |
| 7 | Composio enforces API rate limits **per organization** over a fixed one-minute window. Every authenticated endpoint draws from the same budget, including tool execution, connected accounts, and triggers. |
| 8 | |
| 9 | A tool call can also hit the connected app's own quota. Check the full error before changing your Composio plan: |
| 10 | |
| 11 | | Limit | What it measures | Where to look | |
| 12 | | --- | --- | --- | |
| 13 | | Composio API rate limit | Requests across your organization in one minute | The rate limit response and headers below | |
| 14 | | Composio plan usage | Your plan's tool-call allowance | Your Composio usage and billing | |
| 15 | | Provider quota | Requests or operations allowed by the connected app | The provider error in the tool result, including its quota name and request ID | |
| 16 | |
| 17 | Unused Composio allowance does not prevent a provider from rejecting a request. |
| 18 | |
| 19 | ## Rate limits by plan |
| 20 | |
| 21 | | Plan | Rate limit | Window | |
| 22 | |------|------------|--------| |
| 23 | | Hobby | 2,000 requests | 1 minute | |
| 24 | | Pro | 10,000 requests | 1 minute | |
| 25 | | Enterprise | Custom | - | |
| 26 | |
| 27 | ## Rate limit headers |
| 28 | |
| 29 | Every response includes headers so you can track usage without guessing: |
| 30 | |
| 31 | | Header | Description | |
| 32 | |--------|-------------| |
| 33 | | `X-RateLimit` | Total requests allowed in the current window | |
| 34 | | `X-RateLimit-Remaining` | Requests remaining in the current window | |
| 35 | | `X-RateLimit-Window-Size` | Window size (e.g., `60s` for 60 seconds) | |
| 36 | | `Retry-After` | Seconds until the window resets (only on 429 responses) | |
| 37 | |
| 38 | ## Rate limit response |
| 39 | |
| 40 | When you exceed the rate limit, you'll receive a `429 Too Many Requests` response: |
| 41 | |
| 42 | ```json |
| 43 | { |
| 44 | "message": "Rate limit exceeded. Limit: 10000 requests per 1 minutes" |
| 45 | } |
| 46 | ``` |
| 47 | |
| 48 | ## Best practices |
| 49 | |
| 50 | 1. **Watch `X-RateLimit-Remaining`.** Read it on each response to know how much headroom you have left in the window. |
| 51 | |
| 52 | 2. **Honor `Retry-After`.** On a Composio `429`, wait the number of seconds it gives you before retrying. |
| 53 | |
| 54 | 3. **Cache what doesn't change.** Keep tool definitions and other static data client-side so you don't spend requests re-fetching them. |
| 55 | |
| 56 | For retry code in Python and TypeScript, telling Composio limits from provider quotas, and capping concurrency per connected account, see [Avoid and recover from rate limits](/docs/poc-to-prod/avoid-rate-limits). |
| 57 | |
| 58 | ## Provider quota errors |
| 59 | |
| 60 | Providers can limit an OAuth app, developer token, workspace, account, or individual API operation. With managed auth, some of those quotas are shared across connections using Composio's provider credentials. |
| 61 | |
| 62 | These errors identify provider limits: |
| 63 | |
| 64 | | Error detail | Quota to investigate | |
| 65 | | --- | --- | |
| 66 | | Google Ads `RESOURCE_EXHAUSTED` with `rateScope: DEVELOPER` | The Google Ads developer token | |
| 67 | | YouTube `Video Uploads per day` with a Google `project_number` | The Google API project's upload quota | |
| 68 | | QuickBooks `ThrottleExceeded` | The Intuit limit named in the full provider response | |
| 69 | |
| 70 | Follow the provider's retry or reset window. A short burst limit and an exhausted daily or monthly quota need different recovery steps. Repeated retries do not increase the available quota. |
| 71 | |
| 72 | Upgrading your Composio plan alone does not move an existing managed connection to a different provider app or dedicated quota. Reconnecting the same managed connection does not switch it to your own OAuth app either. |
| 73 | |
| 74 | On the Developer Platform, you can [create a custom auth config](/docs/authentication/custom-app-vs-managed-app) with your own provider credentials where supported. Authorize a new connected account under that config and select it in your workflow. The provider's approval requirements and limits still apply. Google Ads, for example, uses a developer token in addition to an OAuth client ID and secret. |
| 75 | |
| 76 | Auth configs belong to a project. A custom config in your Developer Platform project does not change an existing Composio For You connection. |
| 77 | |
| 78 | If you need help tracing a limit, include the UTC timestamp, tool slug, Composio execution or request ID, provider request ID, exact error, and whether you use managed or custom auth. Keep credentials out of the report. |
| 79 | |
| 80 | ## Need higher limits? |
| 81 | |
| 82 | If you regularly hit Composio's organization API limit, upgrade your plan or [talk to us](https://composio.dev/contact?utm_source=docs&cta_placement=docs-rate-limits) about custom limits. For a provider quota, use the provider recovery steps above. |
| 83 | |
| 84 | If you keep hitting a provider quota on a Composio-managed app, the fix is to move to your own OAuth app, so your connections draw from your own provider quota. See [Managed vs custom auth](/docs/authentication/custom-app-vs-managed-app). |
| 85 | |
| 86 | <Cards> |
| 87 | <Card title="Errors" href="/reference/errors"> |
| 88 | Understanding API error responses |
| 89 | </Card> |
| 90 | <Card title="Pricing" href="https://composio.dev/pricing"> |
| 91 | Compare plans and limits |
| 92 | </Card> |
| 93 | </Cards> |