Changelog

November 10, 2021

Email API now supports idempotency.

Passing the IdempotencyKey in the transactional email headers now allows you to be sure the request will be processed only once and that not repeated emails will be sent to your recipients mailbox.

The idempotencyKey needs to be a unique identifier every time it is passed. We recommend to use a UUID v4 for this purpose.

The TTL for the idempotencyKey is 15 minutes.

Endpoint supporting Idempotency

1curl --request POST \
2     --url https://api.sendinblue.com/v3/smtp/email \
3     --header 'Accept: application/json' \
4     --header 'Content-Type: application/json' \
5     --data '
6{
7     "sender": {
8          "name": "Mauricio",
9          "email": "mauricio@sendinblue.com"
10     },
11     "to": [
12          {
13               "email": "mauricio2@sendinblue.com",
14               "name": "Mauricio2"
15          }
16     ],
17     "headers": {
18          "idempotencyKey": "b52dbf-81dd-4a08-b807-085c" -----> New attribute 🎉🎉🎉 !
19     },
20     "subject": "This is a unique email",
21     "templateId": 1
22}
23'

Unicode option on all SMS endpoints

It’s now posible to define special characters as non-unicode. Whenever the flag is set to false any unicode characters in the message payload will be converted to their english equivalents.

Example characters that are considered unicode
À  â È Ê ê Ë ë Î î Ï ï Ô ô Œ œ Ù Û û Ÿ ÿ ç

Endpoints supporting this change:

1{
2     "unicodeEnabled": true,
3     "name": "RecipientName",
4     "sender": "Sendinblue Inc.",
5     "content": "Message body containing unicode characters À Â â È Ê"
6}