We are pushing a few changes to ensure a better latency to all the contact related endpoints.

Get all contacts and get contacts from list api's will now show the value of count in response considering the *last_modified* value, if passed in the query parameters.

You will now receive uniqueSubscribers for a list for the below routes which denotes the total number of unique contacts (totalBlacklisted and totalSubscribers) present in a list.

You can now sort the results in the response of GET endpoints in ascending or descending order by passing a query parameter named sort in the request. Value of sort parameter can either be asc or desc. This feature is available in the following endpoints.

Three new api endpoints have been introduced to manage blocked domains:

Route: https://developers.sendinblue.com/reference#getemaileventreport-1
You will now receive templateId for events in the response of this route. templateId field will only be present in case of template based emails

Route: https://developers.sendinblue.com/reference#sendtransacemail
You will no longer receive any template validation error from the API while sending a transactional email. Your email credits will not be deducted if there are any template validation errors while sending the email. You will also receive a daily alert consolidating all the template validation errors for a particular day, if there are any.

Route: https://developers.sendinblue.com/reference#createwebhook
The number of webhook creation (marketing + transactional) is now limited to a maximum of 40. If a client already has more than 40 webhooks, they will not be allowed to create any more until they delete some of the existing webhooks to bring the total count to less than 40.

Route: https://developers.sendinblue.com/reference#updateemailcampaign
Following rule, apart from existing ones, will also be followed for the validation of the request parameters from now on:

Route: https://developers.sendinblue.com/reference#createemailcampaign-1
Following rule, apart from existing ones, will also be followed for the validation of the request parameters from now on: