Getting startedRate limits

Rate limit headers

Understand and use rate limit response headers to manage API request throttling

Overview

When you exceed a rate limit, the Brevo API returns a 429 Too Many Requests status code along with response headers describing the current rate limit status. Use these headers to monitor API usage and implement retry logic.

Use rate limit headers to:

  • Track remaining request capacity
  • Determine when rate limits reset
  • Implement exponential backoff
  • Prevent unnecessary API calls

Rate limit headers

All rate-limited endpoints include the following headers in their responses:

HeaderDescription
x-sib-ratelimit-limitMaximum number of requests allowed in the current time window before receiving a 429 status code
x-sib-ratelimit-remainingNumber of requests remaining in the current time window
x-sib-ratelimit-resetTime remaining until the rate limit resets, expressed in the granularity unit (typically seconds)