429 responses.
Webhooks are enabled per team on request. Contact your Impala account team to turn them on.
Set up an endpoint
- Ask your Impala account team to enable webhooks for your team.
- In Settings, add an HTTPS endpoint that accepts
POSTrequests. - Ask us to send a test event and check that it arrives.
Route with the limits
Set Impala’s weight in your router so your expected peak stays under the new limits, and send overflow to another provider. Requests above the limit return429. Rejected requests appear as request errors on the Usage page.
Before your router acts on events, log a few and check that your update logic would have produced the routing you expect.
See your limit on the Usage page
The Throughput chart on the Usage page draws your RPM limit as a dashed line labeledRate limit: <N> req/min. Use it to check how close your traffic runs to the limit.
- All models: the line shows your team’s RPM limit.
- A single model: if that model has its own RPM limit, the line shows the lower of the team limit and the model limit. Otherwise, the line shows the team limit, and the chart compares it with your busiest minute across all models.
- Busiest minute: the highest request count in any minute, plotted next to the percentiles.
- Rejected (429): red dots on the time buckets where requests were rejected with
429.

