Webhooks push real-time updates about message events straight into your own system. Filter by source or event type, add custom headers for authentication, and stop checking for status.
Checking an API on a timer wastes calls and still leaves a gap between an event and your system knowing about it. Spotler SendPro fixes this by sending webhooks to your endpoint the moment it happens.
Filter by source, by event type, or both. Leave either unset and the webhook delivers everything.
Add custom headers when you set up a webhook. Use them for authentication or simply to identify which webhook made the call.
A failed call is retried on a schedule, not abandoned after one attempt. Only a full day of failures disables it.
A webhook is one form to fill in and a set of events to push. No account-wide switch, no custom polling job to maintain.
Leave sources and event types unfiltered and a webhook delivers every event from every source. Narrow either one to cut the noise.
A webhook covers every source and every event type by default. Filter by source, by event type, or both to narrow it down. Custom headers handle authentication or identification, so your endpoint only accepts calls it recognises.
A failed call retries on a schedule. Direct attempt first, then 5-minute retries, then 30-minute, then hourly, then a final sweeper for anything still stuck. After 24 hours without a successful delivery, the webhook is disabled and you’re notified.
Use a webhook to flag a message worth pulling from the archive, without waiting on a report.
Filter webhook events by Source to match the same systems already sending your mail.
The same delivery, open and click events also land in your dashboard, the moment they happen.
A way to receive real-time updates about message events in your own system. It’s useful for integrating multiple systems together or for building a custom frontend on top of the API.
No. Leave both unfiltered and the webhook delivers every event from every source. Set either filter, or both, to narrow it down to what your integration actually needs.
Add custom headers when you set up the webhook. Use them for authentication, or simply to identify which webhook made the call once it reaches your endpoint.
SendPro retries on a schedule: a direct attempt, then 5-minute retries, then 30-minute, then hourly, then a final sweeper group. After 24 hours without a successful delivery, the webhook is disabled and you get notified, including when it drops to a slower retry group along the way.
Delivery events like DELIVERED and POSTED, bounce and complaint events, processing events like SUBMITTED and REJECTED, error and status events, engagement events like OPENED and CLICKED, and workflow events including RESENT and CUSTOM. Filter down to only the ones your integration needs.
Webhooks are an add-on and need account manager approval before they’re switched on. Ask your account manager to enable it if it isn’t already available.