Skip to content
Mumara

Developer

Your systems, notified the moment it happens.

Mumara ONE fires HMAC-signed webhook events for delivery, opens, clicks, bounces, complaints, unsubscribes, form submissions, and automation steps — pushed to your endpoint the instant they occur, with retry on failure. The push counterpart to the REST API.

Get started Event types →
webhook · delivery
Event click · [email protected]

POST https://acme.example/hooks

X-Signature: hmac-sha256 ✓

{ "event": "click", "url": "..." }

200 OK retries on failure
signed & verifiablereal-time

How it works

Fire, sign, retry.

Every event type

Delivery, open, click, bounce, complaint, unsubscribe, form submission, trigger action, and workflow step can each fire a webhook. Subscribe an endpoint to exactly the events it cares about and ignore the rest.

Signed, so you can trust it

Every payload is HMAC-signed. Your receiver verifies the signature with a shared secret before acting, so you know the event genuinely came from Mumara and wasn't forged or tampered with in transit.

Resilient delivery

If your endpoint is briefly down, Mumara retries with exponential backoff rather than dropping the event — so a momentary blip on your side doesn't cost you data.

Event types

Subscribe to what you need.

From delivery status to engagement to automation steps — point each endpoint at the events that matter to it, and route them wherever your stack makes decisions.

  • delivery
  • open
  • click
  • bounce
  • complaint
  • unsubscribe
  • form submit
  • trigger action
  • workflow step

What it replaces

The cost of finding out late.

  • Polling for changes

    Repeatedly asking the API "anything new?" is wasteful and always lags. Webhooks push the event the instant it happens, so your systems learn in real time.

  • Unverifiable callbacks

    An unsigned webhook could be forged by anyone who learns the URL. HMAC signing lets your receiver confirm each payload genuinely came from Mumara.

  • Lost events on a blip

    A webhook that fires once and gives up loses data when your endpoint hiccups. Exponential-backoff retries make sure the event still lands.

  • Engagement trapped in the ESP

    If opens and clicks only live in the dashboard, your CRM is blind. Webhooks push them to wherever your team actually acts on them.

What teams wire up

Events, routed to where decisions happen.

  • Sync to your CRM

    The event
    An open or click happens.
    What your stack does
    Push engagement straight into your CRM so sales sees who's warm — instead of it being trapped in the ESP dashboard.

  • React to a bounce

    The event
    A hard bounce or complaint fires.
    What your stack does
    Update the contact's status in your own database the instant it happens, keeping your records in step with reality.

  • Trigger downstream automation

    The event
    A form submit or workflow step occurs.
    What your stack does
    Kick off a process in another system — provision an account, notify a channel, start a fulfilment job — in real time.

  • Feed a data warehouse

    The event
    Any event you subscribe to.
    What your stack does
    Stream signed events into your analytics pipeline so reporting reflects what happened seconds ago, not last night.
“We pipe click and bounce events straight into our CRM over webhooks, so sales sees engagement in real time and dead contacts get flagged automatically. The HMAC signature was the dealbreaker detail — our security team wouldn't accept an unsigned callback, and here verifying it was a few lines.”

Verified review

Mumara ONE customer

G2

Common questions

What buyers usually ask.

What events can fire a webhook?

Delivery, open, click, bounce, complaint, unsubscribe, form submission, trigger action, and workflow step. You subscribe each endpoint to the specific event types it needs rather than receiving everything.

How do I know a webhook is genuine?

Every payload is HMAC-signed. Your receiver computes the signature with the shared secret and compares it — if it matches, the event genuinely came from Mumara and wasn't tampered with. Reject anything that doesn't verify.

What happens if my endpoint is down?

Mumara retries with exponential backoff rather than dropping the event, so a brief outage on your side doesn't lose data. Once your endpoint recovers, the queued events are delivered.

How does this relate to the REST API?

They're two halves of a real-time integration: the REST API lets you pull data and take actions, while webhooks push events to you as they happen. Together they cover both directions without polling.

Which plans include webhooks?

Webhooks are available on the Pro and Business tiers of Mumara ONE.

Related

Pages that pair with this one.

Mumara ONE · Webhooks

Stop polling. Start listening.

HMAC-signed events for delivery, engagement, and automation — pushed to your endpoint in real time, with retries so nothing is lost. Pro and Business tiers.

Get started See pricing