We are experiencing 429 errors although we're not using the API very extensively. We are not exceeding our call concurrency limit and this is not the issue. Our issue is that when we use the API get e.g. GET a call we get the 429 error. Even after waiting minutes and retrying we are getting the error. Our org id is: dfa21930-04c6-4006-b84c-d7e1c96ae23f

Hi there! 👋 I see you're experiencing 429 "Too many requests" errors with the VAPI API's "GET a call" endpoint, even after waiting several minutes between requests. While I don't have specific information about why your organization is experiencing these errors despite the cooldown period, I can definitely help with some troubleshooting steps and potential causes. ## Potential Causes & Troubleshooting Steps ### Rate Limiting Considerations According to the information I found, most VAPI APIs have rate limits to prevent abuse and ensure fair usage. When you reach these limits, the API typically sends a 429 response with a "Retry-After" header indicating how long to wait before retrying [(Source)](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336432266305339473). ### Check API Authentication & Configuration - **Verify API Key**: Ensure you're using the correct API key with the necessary permissions [(Source)](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1328923059905630238) - **Check Endpoint Path**: Verify that you're using the correct endpoint URL:

https://api.vapi.ai/call/:id

[(Source)](https://docs.vapi.ai/api-reference/calls/get-call) - **Headers**: Make sure you're including the required

Authorization

header with the format

Bearer <token>

[(Source)](https://docs.vapi.ai/api-reference/calls/get-call) ### Potential Edge Cases Some edge cases that might cause persistent 429 errors include: 1. **Using Your Own API Key**: If you're using your own API key (e.g., for a Google model), it might have rate limiting applied [(Source)](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1340022199687577680) 2. **Inefficient API Usage**: Even with cooldowns, inefficient API patterns might trigger rate limits. Consider optimizing by caching results or batching requests [(Source)](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336171779772907692)

Sorry. but the mentioned fixes don't help us

Hey Henning, sorry for the bad experience, we are currently looking into it thanks for your patience

Thanks! In the meantime we are now able to make API requests again. We've increased logging on our side so next time this error occurs we could help you folks out with the http cooldown period header that VAPI would return. On a different note: can you pls increase our quota? We're growing and have hit the tate limit 1-2 times per week during crunch time

It's been fixed, you can try after 5 minutes

Addressed in email.

Hey @Henning did your issue get resolved? Or are you still seeing the 429 error?