The Dotdigital API is a family of REST web services that provides programmatic access to a huge range of Dotdigital's functionality.
The API allows you to automate many everyday tasks you might otherwise have to carry out manually, and send real-time messages to your customers across a wide array of channels. This is useful if you want to increase your productivity within the Dotdigital, and enhance your customer engagement.
You can use the API to connect almost any system to Dotdigital. Provided your CRM, website or any back office system also has an API, then it can be quickly connected, allowing you to keep your data easily in sync. Data can be imported and exported on a schedule, and most common tasks available in Dotdigital can be automated using the API.
We provide omnichannel messaging and transactional email APIs to send messages from your systems or applications to engage and serve your customers. You can send to any messaging or notification channel like SMS, Facebook Messenger, WhatsApp, in-app messaging or push notifications, and more. All through one simple API.
The API has the following major functional areas:
- Accounts and utilities - calls that manage or get details about your Dotdigital account and that provide utility functions for you.
- Contacts and data - calls that allow you to manage your contacts and associated additional data.
- Insight data - calls that allow you to create, read, update and delete Insight data.
To learn more, check out the Developer's guide to Insight data.
- Marketing and automation - calls to support marketing campaigns, pages and forms, and automated programs.
- Communications - real-time, high volume transactional communications across a variety of channels.
The following diagrams show additional details of the available methods in the functional areas:
API training videos
To learn more about our API and its common uses, check out our API training videos here
Our API functionality is delivered over a range of services which are either implemented on our v2 API framework or v3 API framework. Both API frameworks are RESTful and are secured using the same API users, but do differ slightly in their capabilities and calling conventions.
With the launch of unified contacts we have started to introduce our v3 services that are specifically designed to work with unified contacts and use the latest industry best practices for RESTful services.
You are likely to require a combination of v2 and v3 services to achieve your integration goals, however we would encourage the use of the v3 services wherever possible due to the advantages they offer.
The key differences in v3 services are as follows:
- They support referring to contacts using your specified identifier type; choose from contact id, email or phone number.
- They use a slightly different pagination mechanism; see API conventions for more details.
- They use a different error response that provides more information in both human and machine readable formats; see API conventions for more details.
It's simple to identify if a call is provided by a v2 or v3 service by looking at the calls URI. If the URI contains /v2/ it is provided by an API v2 service, and if the URI contains /v3/ then it is provided by a API v3 service.
Example: API v2 service URI
Example: API v3 service URI
Updated 7 months ago