I’ve been noticing 429 - Rate Limit Exceeded error...
# general-english
m
I’ve been noticing 429 - Rate Limit Exceeded errors while making outbound calls through API. I am however, only making single, sequential calls and not hitting our concurrency limits. Could anyone help understand how the current rate limits are structured on your end? Also, is there a way to align the rate limits with the number of available slots? In our setup, if a call isn’t connected, I trigger the next one as soon as I receive an ended status from Vapi—so ideally, the flow stays efficient and within limits. Anyone please help with this
5 Views