Skip to main content
Question

How to avoid hitting rate limits when using call monitoring apis ?

  • February 12, 2025
  • 6 replies
  • 43 views

Forum|alt.badge.img

I am hitting rate limits while making api calls for monitoring calls for individual extensions. What I am doing is authenticating with a super admin cred and subscribing to individual extension telephony session events. I want to supervise parties and not a call so need to hit the active call session api as well. This scenarios will probably raise rate limit errors( and is) while supervising for multiple agents. what is the recommended way to avoid hitting rate limits since retry will delay monitoring calls upto 60s which is not ideal.

PhongVu
Community Manager
Forum|alt.badge.img
  • Community Manager
  • February 12, 2025

The Supervise Call Party API rate group is Light, which is 50 API calls per minutes. This should be enough for starting to supervise 25 calls (2 parties per call) every minute.

If you have a call monitoring group with many agents (e.g > 50), you can specify multiple supervisors and build your own logic to use different supervisor’s access token to supervise the call. Or easier, create multiple smaller call monitoring group.

Alternatively, if the number of agents is not huge and the high number of calls happens just during some peak hours, you may want to submit a support request to ask for higher rate limit for your app. Remember to provide your app client id and good justification why you need higher rate limit for your app.


Forum|alt.badge.img
  • Known Participant
  • February 12, 2025

hey ​@PhongVu really appreciate you answering this queries, very helpful.


PhongVu
Community Manager
Forum|alt.badge.img
  • Community Manager
  • February 12, 2025
kutbuddin wrote:

hey ​@PhongVu really appreciate you answering this queries, very helpful.

BTW, if you face the 429 errors more often recently (since yesterday or so) without actual increasing numbers of API calls, it could be due to a current issue on our API gateway. The team is investigating and resolve it asap.


Forum|alt.badge.img
  • Known Participant
  • February 13, 2025

Yeah, facing this since yesterday


Forum|alt.badge.img
  • Known Participant
  • February 13, 2025

This looks like fixed today ​@PhongVu . any idea on what the issue was?


PhongVu
Community Manager
Forum|alt.badge.img
  • Community Manager
  • February 13, 2025
kutbuddin wrote:

This looks like fixed today ​@PhongVu . any idea on what the issue was?

There were some problems in the load balancers which impacted some regions. I believed that the team has fixed the problems last night.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings