@devries-cameron20 / composio-1 / commits / 8caa5988d
Fork 0

Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

docs: distinguish provider quotas from Composio limits

Vinayak Agarwal committed Oct 20, 2026 at 13:08 UTC 8caa5988dd0f2bad8884ca2b7ba2e08c959142e4
2 files changed +78 -14
docs/content/reference/rate-limits.mdx
+39 -7
@@ -1,10 +1,20 @@
1 ---
2 title: Rate Limits
3 -description: Composio API rate limits by plan, rate limit headers, and best practices
4 -keywords: [API rate limits, rate limiting, throttling, 429 too many requests, API quotas, request 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 rate limits **per organization** over a fixed one-minute window. Every authenticated endpoint draws from the same budget — tool execution, connected accounts, triggers, and the rest — so the limit below is your organization's total across all API calls.
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
@@ -37,15 +47,37 @@ When you exceed the rate limit, you'll receive a `429 Too Many Requests` respons
47
48 ## Best practices
49
40 -1. **Watch `X-RateLimit-Remaining`** — read it on each response to know how much headroom you have left in the window.
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 +## Provider quota errors
57 +
58 +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.
59 +
60 +These errors identify provider limits:
61 +
62 +| Error detail | Quota to investigate |
63 +| --- | --- |
64 +| Google Ads `RESOURCE_EXHAUSTED` with `rateScope: DEVELOPER` | The Google Ads developer token |
65 +| YouTube `Video Uploads per day` with a Google `project_number` | The Google API project's upload quota |
66 +| QuickBooks `ThrottleExceeded` | The Intuit limit named in the full provider response |
67 +
68 +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.
69 +
70 +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.
71 +
72 +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.
73
42 -2. **Honor `Retry-After`** — on a `429`, wait the number of seconds it gives you before retrying instead of hammering the endpoint.
74 +Auth configs belong to a project. A custom config in your Developer Platform project does not change an existing Composio For You connection.
75
44 -3. **Cache what doesn't change** — keep tool definitions and other static data client-side so you don't spend requests re-fetching them.
76 +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.
77
78 ## Need higher limits?
79
48 -If you hit these limits regularly, upgrade your plan or [talk to us](https://composio.dev/contact?utm_source=docs&cta_placement=docs-rate-limits) about custom limits for your use case.
80 +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.
81
82 <Cards>
83 <Card title="Errors" href="/reference/errors">
docs/content/reference/v3/rate-limits.mdx
+39 -7
@@ -1,10 +1,20 @@
1 ---
2 title: Rate Limits
3 -description: Composio API rate limits by plan, rate limit headers, and best practices
4 -keywords: [API rate limits, rate limiting, throttling, 429 too many requests, API quotas, request 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 rate limits **per organization** over a fixed one-minute window. Every authenticated endpoint draws from the same budget — tool execution, connected accounts, triggers, and the rest — so the limit below is your organization's total across all API calls.
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
@@ -37,15 +47,37 @@ When you exceed the rate limit, you'll receive a `429 Too Many Requests` respons
47
48 ## Best practices
49
40 -1. **Watch `X-RateLimit-Remaining`** — read it on each response to know how much headroom you have left in the window.
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 +## Provider quota errors
57 +
58 +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.
59 +
60 +These errors identify provider limits:
61 +
62 +| Error detail | Quota to investigate |
63 +| --- | --- |
64 +| Google Ads `RESOURCE_EXHAUSTED` with `rateScope: DEVELOPER` | The Google Ads developer token |
65 +| YouTube `Video Uploads per day` with a Google `project_number` | The Google API project's upload quota |
66 +| QuickBooks `ThrottleExceeded` | The Intuit limit named in the full provider response |
67 +
68 +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.
69 +
70 +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.
71 +
72 +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.
73
42 -2. **Honor `Retry-After`** — on a `429`, wait the number of seconds it gives you before retrying instead of hammering the endpoint.
74 +Auth configs belong to a project. A custom config in your Developer Platform project does not change an existing Composio For You connection.
75
44 -3. **Cache what doesn't change** — keep tool definitions and other static data client-side so you don't spend requests re-fetching them.
76 +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.
77
78 ## Need higher limits?
79
48 -If you hit these limits regularly, upgrade your plan or [talk to us](https://composio.dev/contact?utm_source=docs&cta_placement=docs-rate-limits) about custom limits for your use case.
80 +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.
81
82 <Cards>
83 <Card title="Errors" href="/reference/v3/errors">