brevo · Rate Limits
Brevo Rate Limits
Brevo enforces API rate limits using two metrics, requests-per-second (RPS) and requests-per-hour (RPH), with limits scaling across three tiers - General (all accounts), Advanced (Professional / Enterprise), and Extended (Enterprise only). Per-endpoint ceilings are highest for transactional email and SMS sends. Overages return HTTP 429 and Brevo includes rate-limit headers on every response.
10 Limits
Throttle: 429
EmailTransactionalSMSMarketingCRMRate Limiting
Limits
General - POST /v3/smtp/email account
1000
Also 3,600,000 requests/hour. All account types.
General - POST /v3/transactionalSMS/send account
150
Also 540,000 requests/hour.
General - GET /v3/smtp/emails account
2
Also 7,200 requests/hour.
General - /v3/contacts/{...} account
10
Also 36,000 requests/hour.
General - all other endpoints account
100
Advanced - email send account
2000
Email and SMS limits double on Professional / Enterprise; contacts reach 20 RPS / 72,000 RPH; other endpoints reach 200 RPH.
Advanced - contact endpoints account
20
Extended - email send account
6000
Enterprise-only ceiling.
Extended - SMS send account
250
Extended - contact endpoints account
60
Policies
Backoff Strategy
Apply exponential backoff with jitter on 429 responses; rate-limit headers are included on all responses to support proactive throttling.
Tiered Capacity
Capacity is bound to account tier; upgrade from Free / Starter to Professional / Enterprise to lift to Advanced or Extended tiers.
Endpoint-Specific Limits
Bulk send endpoints (email / SMS) have 1-2 orders of magnitude higher RPS than read or contact-management endpoints; design clients to batch and avoid per-record loops on contacts.