Deprecated parameter is now entirely removed!

API route: Export contacts api
The usage of previously marked deprecated parameter has now entirely been removed.
contactFilter parameter of Export Contacts Api will no longer be available from now on. Please pass customContactFilter in the input instead. It has now become a mandatory parameter.
Related change logs: Added & Deprecated


Inbound Parse API

We are happy to introduce a new kind of API. Inbound parsing allows you to receive emails on your application as structured JSON payloads through a webhook.


Default date ranges added for response rendering

Get contact details: Along with the contact details, this endpoint will show the statistics of contact for the recent 90 days by default. To fetch the earlier statistics, please use Get contact campaign stats endpoint with the appropriate date ranges.
Get campaign stats of a contact: This endpoint will show the statistics of contact for the recent 90 days by default. To fetch the earlier statistics, please pass appropriate date filters in the request.


Dropped support for list counters

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


Total count in response modified to be in sync with last_modified filter

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.


Added uniqueSubscribers in response schema for fetching lists

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.


Sorting capability in GET responses

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.


New API endpoints introduced to manage blocked domains

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


Added templateId in response schema of getEmailEventReport

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


Remove template validation errors from send TransactionalEmail API

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.