Webhooks
Was this helpful?
Was this helpful?
Webhooks allow us to push raw events we collect about your emails over to your servers. Batches of events are delivered through a POST request to the defined target URL. You can use this endpoint to create and manage webhooks, or you can create one from the app.
Any webhook batch that does not receive an HTTP 200 response will be retried for a total of 8 hours before the data is discarded.
Each webhook batch contains the header X-MessageSystems-Batch-ID
, which is useful for detecting and prevention of processing duplicate batches. Additionally within each event the event_id
is unique and can also be used in duplicate detection and prevention.
Webhooks posting to your endpoint will timeout after 10 seconds. For best results, write webhook batches to disk and then process asynchronously to minimize data loss if you have a problem with your database.
Webhook batch status is available for 24 hours via the UI or the API.
See for more information on how best to consume webhooks.
See for highly recommended security measures.
You can receive any of the following types of events in webhook payloads:
Message Status Events:
injection
: Message was accepted for delivery
delivery
: Message was successfully delivered
delay
: Message delivery was delayed
bounce
: Message delivery failed
spam_complaint
: Recipient marked message as spam
out_of_band
: Message bounced after initial acceptance
policy_rejection
: Message was rejected by policy
generation_failure
: Message generation failed
generation_rejection
: Message was rejected during generation
Recipient Engagement Events:
open
: Message was opened
initial_open
: First time message was opened
click
: Link in message was clicked
initial_click
: First time a link was clicked
amp_click
: Link in AMP version was clicked
amp_open
: AMP version was opened
The validation request sends an example message event batch to the target URL, validates that the target responds with HTTP 200, and returns information on the response received.
The ID of the workspace
The ID of the webhook
Webhook validation successful
Get status information about webhook batches. Status information is provided for failed batches and those that succeeded on retry. Batch status is available for 24 hours.
The ID of the workspace
The ID of the webhook
Maximum number of results to return
1000
Successfully retrieved batch status information
Create a new webhook. When a webhook is created, a test POST request is sent to the target URL. If this request does not receive an HTTP 200 response, your request will fail with HTTP 400 and the webhook will not be created. If created successfully, the webhook will begin to receive event data after 1 minute.
The ID of the workspace
Name for webhook
URL of the target to which to POST event batches
Array of event types this webhook will send
The status of the webhook
true
Object of custom headers to be used during POST requests to target
Type of authentication to be used during POST requests to target
none
Possible values: Update an existing webhook. If you change the target URL, a test POST request will be sent. If this request does not receive an HTTP 200 response, your request will fail with HTTP 400.
The ID of the workspace
The ID of the webhook
Name for webhook
URL of the target to which to POST event batches
Array of event types this webhook will send
The status of the webhook
Object of custom headers to be used during POST requests to target
Type of authentication to be used during POST requests to target
Object containing details needed for OAuth 2.0 authentication
Object containing credentials for Basic Authentication