4012: Request rate exceeded.

HTTP status: 429.

Each API key may make a burst of requests and then a steady number per second. The limit is a safeguard set far above what an ordinary integration needs, and it stops runaway loops before they slow the service for everyone. Nothing was done for this request. The response carries Retry-After, mirrored in error.retry_after, with the whole seconds to wait before a request from this key is accepted again.

• Wait error.retry_after seconds, then retry; back off further if the refusal repeats.
• Look for a loop that retries without waiting, or that polls a read in a tight cycle; use the event stream or webhooks instead of polling.

• Request rate
• Events guide