Easily Integrate Sendinblue To Your Project.

Guides    API Reference

Rate limits

You will find here all the information regarding how to properly execute API calls in bulks.

Our public API is a service accessible to all Sendinblue users, we want to provide the best possible experience when you integrate to our platform. In order to ensure this we have put in place some limits to the number of requests that can be executed in a period of time.

General Rate Limiting

Our endpoint list has been optimised in such way that we ensure the critical routes can efficiently handle as many requests as possible without compromising stability. This translates to the following numbers:

EndpointRate Limiting
POST /v3/smtp/email 16 RPS / 1000 RPM
All other endpoints6 RPS / 400 RPM

RPS: HTTP requests per second
RPM: HTTP requests per minute

How to prevent my API requests from being rejected ?

If you execute request bursts in a shorter timeframe other than the specified above you might get as a result a 429 status code or "Too many requests". This means you're hitting the limit for the number of requests allowed in a single endpoint. Here are some recommendations on how to prevent this error from appearing:

1- Make sure you properly calculate your allowance per minute. You need to send your bulk requests equally distributed through the minute, this means that you should not query the API all at once. Let's say you intend to send 1000 emails through the endpoint POST /v3/smtp/email , you want to make sure you execute (as a maximum) the endpoint ~16 times every second.
~16 RPS x 60 seconds = ~1000 RPM.

2- Create a retry mechanism. If you consider your application could easily hit the limits defined for each endpoint, it would be a good idea to implement on your side a retry mechanism which can identify whenever a 429 error message is returned and execute again the failed action after adding a delay for the re try.

Extended Rate Limit Add-On

If you have an enterprise account and you require more throughput in your API operations it's possible to request the rate limit add-on on top of the general rate limit policy. This throttling is represented by the following numbers:

EndpointRate Limiting
All API endpoints100 000  RPM

RPM: HTTP requests per minute

If your business needs require further limiting please reach out to our customer service

Hourly quota for email sending

To help new transactional senders build a positive reputation over time, we apply an hourly sending bandwidth for accounts using our shared IPs.

Transactional senders who are using our shared IPs will start with the capacity of sending 40 emails per hour. This bandwidth will increase or decrease automatically based on your engagement metrics and sending volume.

Senders who wish to send non-transactional materials (such as marketing emails) through the SMTP platform may only do so by using a dedicated IP.

You can learn more about the hourly quota on this help article

Updated 13 days ago


Rate limits


You will find here all the information regarding how to properly execute API calls in bulks.

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.