iemails
Pricing
Log inGet started
Get started
WebhooksSigned with HMAC-SHA256

Know the moment
anything happens

Get a signed POST to your server the instant an email is delivered, opened, clicked or bounced — or a contact signs up or opts out. Build on real events instead of polling.

Start sending free Read the guide
14 event typesSigned requestsAutomatic retries
POSTapi.acme.com/webhooksListening
Waiting for events…
RequestWaiting…
content-type: application/json
user-agent: iemails-webhooks/1
webhook-id: whev_31676
webhook-timestamp: 1794225912
webhook-signature: v1,5f0c9a1e…b72d
Body
1{
2 "type": "email.delivered",
3 "created_at": "2026-11-11T12:04:32.240Z",
4 "data": {
5 "email_id": "em_7Hk2Qp9vX",
6 "to": ["[email protected]"],
7 "subject": "Confirm your account",
8 "recipient": "[email protected]"
9 }
10}
Real timeEvents reach your endpoint seconds after they happen.
SignedHMAC-SHA256 on every request, with a timestamp you can check.
Retried for youSix attempts over about nine hours when your endpoint is down.
Replay anythingSend any past event again with one click.
Real-time events

Listen to
everything that matters

Subscribe each endpoint to the events it needs. Every payload has the same shape: a type, a timestamp and the data, so one handler can route them all.

Email
Contacts
Broadcasts
Inbound
email.deliveredAccepted by the inbox provider.
1{
2 "type": "email.delivered",
3 "created_at": "2026-11-11T12:04:32.240Z",
4 "data": {
5 "email_id": "em_7Hk2Qp9vX",
6 "to": ["[email protected]"],
7 "subject": "Confirm your account",
8 "recipient": "[email protected]"
9 }
10}
14 event typesSame envelope for every event
Secure by default

Trust every request.
Verify it in ten lines.

Anyone can POST to a URL. A valid signature proves the request came from iemails and was not changed on the way.

  • Every request is signed with HMAC-SHA256 using a secret only you and iemails know.
  • A timestamp in the signature lets you reject old requests, so a captured one can’t be replayed.
  • Rotate the signing secret at any time from the dashboard.
  • We only deliver to public HTTPS addresses and never follow redirects.
app/api/webhooks/route.ts
1import crypto from 'node:crypto';
2
3export async function POST(req: Request) {
4 const body = await req.text();
5 const id = req.headers.get('webhook-id') ?? '';
6 const ts = req.headers.get('webhook-timestamp') ?? '';
7 const sig = req.headers.get('webhook-signature') ?? '';
8
9 // Reject anything older than five minutes.
10 if (Math.abs(Date.now() / 1000 - Number(ts)) > 300) {
11 return new Response('Stale', { status: 400 });
12 }
13
14 const expected = 'v1,' + crypto
15 .createHmac('sha256', process.env.IEMAILS_WEBHOOK_SECRET!)
16 .update(`${id}.${ts}.${body}`)
17 .digest('hex');
18
19 const ok = sig.length === expected.length &&
20 crypto.timingSafeEqual(Buffer.from(sig), Buffer.from(expected));
21 if (!ok) return new Response('Bad signature', { status: 401 });
22
23 const event = JSON.parse(body);
24 if (event.type === 'email.bounced') {
25 await markUndeliverable(event.data.to);
26 }
27 return new Response(null, { status: 204 });
28}
Observability

See every attempt,
and replay any of them

Each delivery keeps the exact request we sent and what your server answered, attempt by attempt. Something went wrong? Fix it, then replay.

app.iemails.co/webhooks/events
email.bounced→ https://api.acme.com/webhooks
Attempts
  1. 1503 Service UnavailableDeploy in progress11:52:10
  2. 2Timed outNo response within 10 seconds11:53:10
  3. 3200 OK41 ms round trip11:58:20
Request body
{ "type": "email.bounced", "data": { … } }
Last response
{ "received": true }
Data integrity

A blip on your side
never loses an event

If your endpoint is down, slow or returns an error, we keep trying on a schedule that backs off. Pick an outage and see when the event gets through.

Delivery scheduleDelivered on attempt 4
  1. 1First attemptNo 2xx within 10 sNow
  2. 2Retry 1No 2xx within 10 s+1 min
  3. 3Retry 2No 2xx within 10 s+6 min
  4. 4Retry 3200 OK — delivered+36 min
  5. 5Retry 4Not needed+2 h 36 min
  6. 6Retry 5Not needed+8 h 36 min
After 20 failures in a row an endpoint is switched off, so a dead URL never piles up retries. Turn it back on and replay what you missed.
Easy to use

Live in
three steps

Point us at a URL, choose your events and check the signature. That is the whole setup.

1

Add an endpoint

Paste a public HTTPS URL and tick the events you care about.

https://api.acme.com/webhooks ☑ email.delivered ☑ email.bounced ☑ contact.unsubscribed
2

Copy the signing secret

Each endpoint gets its own whsec_ secret for checking signatures.

IEMAILS_WEBHOOK_SECRET= whsec_k2Lq8Vx…
3

Return a 2xx

Answer within 10 seconds. Anything else, and we try again.

HTTP/1.1 204 No Content # within 10 seconds
FAQ

Questions
about Webhooks

Wiring webhooks into something unusual? Tell us about it and an engineer will help.

Talk to an engineer

Email queued, sent, delivered, delivery delayed, opened, clicked, bounced, complained and failed; contact created, updated and unsubscribed; broadcast sent; email received for inbound mail; and inbox events — inbox created, updated and deleted, thread created, moved and relabelled, email received and sent, and draft created, updated, sent and deleted. Each endpoint picks its own.

A POST with a JSON body containing type, created_at and data. It carries three headers: webhook-id, webhook-timestamp and webhook-signature, plus a user agent of iemails-webhooks/1.

Compute an HMAC-SHA256 of “id.timestamp.body” with your endpoint’s signing secret, prefix it with “v1,” and compare it to the webhook-signature header. Reject timestamps more than five minutes old.

We retry up to six times: right away, then after 1 minute, 5 minutes, 30 minutes, 2 hours and 6 hours. Any 2xx response within 10 seconds counts as delivered.

No. After 20 failures in a row the endpoint is switched off and we stop sending to it. Fix it, turn it back on, and replay anything you missed.

Yes. Open any event in the dashboard and replay it, whether it failed or succeeded. Replays are signed fresh and logged as new attempts.

Every attempt is kept with the request body and headers, the response status, the first 8 KB of the response body, any error, and how long it took.

Retries mean the same event can arrive more than once, and events from different emails may arrive out of order. Use webhook-id to skip duplicates and created_at to order them.

Hear about every email
the moment it happens

Add an endpoint, pick your events and start building on real-time data today. Every plan includes at least one endpoint.

Sign up for free See pricing
iemails

Email infrastructure for teams who would rather read a trace than a support ticket.

Keizersgracht 241
1016 EA Amsterdam, NL

All systems operational·Status
Features
Email APISMTP relayAutomationsAudiencesBroadcastsInboundTemplatesWebhooksDedicated IPs
Resources
ChangelogPricingEnterpriseSecuritySOC 2GDPRBrand
Company
AboutBlogCareersCustomersPhilosophy
Help
SupportStatusMigrateKnowledge baseLegal
Community
EventsOpen sourceInsidersWallpapers
SOC 2 Type IIGDPR readyISO 2700199.99% uptime SLA
© 2026 iemails, Inc. Built in Amsterdam and Bengaluru.
PrivacyTermsDPASecurityCookies