Emma is an email marketing platform. With Emma you can design stylish email campaigns with easy-to-use features, send those campaigns to customers and collect statistics about how well they perform.
Emma got into the API space early. They've had some version of their API for almost 7 or 8 years now. Since then, the API landscape has changed dramatically.
Their original SOAP version was replaced a few years ago with a modern REST API. Only a few months after launching their REST API, they added REST hook support based on initial feedback.
Over the last year or so, they've expanded their webhook coverage significantly. The biggest advantages of REST Hooks for Emma is how granular and simple they are.
Hooks allow Emma to avoid complex integrations with partners. Before, integrations with partners would take months and Emma would spend a lot of time guiding developers through setting up polling infrastructure and other details.
With REST Hooks, Emma can point to their lighter weight, more granular hook based system for getting at very specific information, like email bounces.
Emma targets small and medium size companies which often don't have dedicated IT teams or people with domain knowledge about APIs. REST Hooks dramatically simplify how much time and effort they need to put into 3rd party developer support.
Let's take a look at how Emma uses REST Hooks.
|REST hook feature||Implemented?|
|Order of delivery|
Emma's REST API supports several methods for interacting with webhooks. Classically, you can create, update, view, and delete hooks through their REST API. Additionally, there is an endpoint to access a list of available events which the user could choose from.
Emma sends all their hooks as skinny payloads. This means the hook payload itself simply contains IDs and references back to their REST API. This is a useful security mechanism because it guarentees that the receiver of the hook has a valid API key before allowing access to any sensitive business data.