What is the rate limit on API calls?
# support
a
What is the rate limit on API calls? I keep getting errors in my N8n flow for hitting the request limit on check call status ? Can't find any documentation that gives any kind of limits so that I can program it in. { "errorMessage": "The service is receiving too many requests from you", "errorDescription": "Rate limit exceeded", "errorDetails": { "rawErrorMessage": [ "Try spacing your requests out using the batching settings under 'Options'" ], "httpCode": "429" }, "n8nDetails": { "nodeName": "Check Call 1 Status", "nodeType": "n8n-nodes-base.httpRequest", "nodeVersion": 4.2, "itemIndex": 0, "time": "10/24/2025, 11:08:59 AM", "n8nVersion": "1.114.4 (Self Hosted)", "binaryDataMode": "default", "stackTrace": [ "NodeApiError: The service is receiving too many requests from you", " at ExecuteContext.execute (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-nodes-
v
To avoid hitting Vapi's API rate limits in your N8n flow, add a delay between requests using the built-in Wait node. Here's how you can do it:
Copy code
plaintext
1. After each API call node, add a 'Wait' node.
2. Set the wait time (e.g., 2 seconds) to space out requests.
This will help prevent HTTP 429 errors while you check for the exact rate limit in the [Vapi API Reference](https://docs.vapi.ai/api-reference). Source: - [Vapi Debugging Documentation](https://docs.vapi.ai/debugging)
a
Totally got it, did that, and still kept hitting the limit with exactly the limit you told me to put in there. I'm trying to see what your guys's rate limiting is and how I can set my flows around your rate limiting @User
@Vapi Support Bot did that, and still kept hitting the limit with exactly the limit you told me to put in there. I'm trying to see what your guys's rate limiting is and how I can set my flows around your rate limiting
v
Thanks for your patience. To help pinpoint the issue, could you share approximately how many API requests per minute your N8n flow is making when you hit the rate limit? This will help us determine if the problem is due to concurrency, burst rate, or another factor. Sources: - [Vapi Debugging Documentation](https://docs.vapi.ai/debugging) - [Vapi Call Queue Management](https://docs.vapi.ai/calls/call-queue-management) - [Vapi Outbound Campaigns Overview](https://docs.vapi.ai/outbound-campaigns/overview) - [Vapi Documentation (Google Doc)](https://docs.google.com/document/d/1X1UzOVUrma47typ4RnohwConQu9gH26iYz9wpZvDXO0/edit?usp=drivesdk)
a
@Vapi Support Bot It was making one per second to check the call status
v
Vapi does not publicly document the exact API rate limit for standard plans. If you are hitting rate limits at 1 request per second, you may need to upgrade to an Enterprise plan, which offers higher rate limits and custom scaling options. To resolve this, consider reaching out to Vapi support or your account manager to discuss your use case and request a rate limit increase or Enterprise upgrade. Reference: See "higher rate limits" under [Vapi Enterprise Plans](https://docs.vapi.ai/enterprise/plans). Source: - [Vapi Enterprise Plans](https://docs.vapi.ai/enterprise/plans)
a
@Vapi Support Bot Okay well assume I'm not public and go ahead and let me know what the rate limit is. Is it 1 per 5 seconds? Per 10 seconds? And of course I mean I'm not public so I should know this
v
Vapi does not publicly document the exact API rate limit—even for internal or non-public users. If you need a higher or custom rate limit, the recommended action is to contact Vapi support or your account manager to discuss your specific requirements and request an increase. Tip: For now, space your requests further apart or batch them, and monitor for HTTP 429 errors. For custom limits, reach out directly to Vapi support. See: [Vapi Enterprise Plans](https://docs.vapi.ai/enterprise/plans) for more on higher rate limits. Source: - [Vapi Enterprise Plans](https://docs.vapi.ai/enterprise/plans)
2 Views