2 results found
-
one webhook sent for each incoming call.
Multiple webhooks are being sent to Tracker RMS for a single call. Specifically, a webhook is being sent for every user in the main group for each incoming call. We only want one webhook sent for each incoming call.
2 votesWe will continue to track this idea, but generally this is not likely to be a feature we implement.
If your use case relates to call logging, App Connect can be used to achieve this.
-
Remove Draconian Rate Limits
RingCentral's rate limiting renders the API of limited use compared to competitors. Having worked with Twilio, Shopify, BigCommerce, Google, and many other players in the e-comm space, I can easily say RingCentral's API is the worst due to these limits. Even the stated rate limit/extension/minute fails when implemented properly and you must apply second level organizational limits on top of that. I, and many others, would benefit from more useful limits and ultimately, this would make RingCentral more competitive.
1 voteWe are unlikely to change our rate limit policy. Every API is carefully evaluated to understand what their throughput is, and rate limits are then set accordingly. We do, however, have a process where developers can request a change to their rate limit, which can often be accommodated.
- Don't see your idea?