The QUOTA_EXCEEDED (429) error in Everbridge 360 appears when your organization sends too many API requests in a short period of time. This article explains what that message means, why it happens, and what you can do to prevent or reduce it.
Overview
When you see an HTTP status code 429 with the title QUOTA_EXCEEDED, it means the request was throttled. The API rate or quota limit for your organization has been reached, so additional requests are temporarily rejected until the quota allows more traffic.
Impact
In Everbridge 360, hitting the throttling limit can cause operators to be redirected to the legacy Everbridge platform and see a QUOTA_EXCEEDED (429) error instead of the expected Everbridge 360 page. This behavior indicates that too many API calls are being made at once for your organization.
Causes
Any burst of traffic can cause this error, but it often appears when an integration or user interface repeatedly calls a status or confirmation endpoint.
One common pattern is a surge of requests to a confirmation-status or similar endpoint when a Communications Details page or other UI remains open and is polling frequently for updates. Over time, this constant polling can push your organization over the configured API quota.
Resolution
Identify and reduce the source of the request surge
- Look for integrations, scripts, or dashboards that may be sending repeated API requests in a short period of time.
- Avoid leaving pages open that continuously poll for status or confirmation data, such as Communications Details views that refresh frequently.
- Adjust how often these clients poll, or change their behavior so they request updates less frequently.
Request an API quota increase or plan upgrade
- If your normal or expected usage regularly approaches the current limit, you may need a higher API quota.
- You can request an API quota increase or plan upgrade from Everbridge so your organization can handle more traffic without hitting throttling as quickly.
- Engineering can upgrade your API plan to mitigate immediate outages; after an upgrade, the Communications UI should load normally again.
Work with Everbridge Support
- If you are unsure which endpoint or client is causing the spike, contact Everbridge Support.
- Provide timestamps and examples of impacted users so Support can help identify which endpoint and client are generating the surge.
Summary
By understanding what the QUOTA_EXCEEDED (429) error means and managing your API usage accordingly, you can keep Everbridge 360 available and responsive for your operators.