Every event delivered. Every time.
Spensr Events handles the retries, fan-out, dead-letter handling, and audit trail so your team does not have to. Send JSON — we guarantee delivery.
Try it now (no signup)Fail-Safe Delivery
Events are delivered at-least-once with automatic retry on failure. If a destination returns a non-2xx response, Spensr Events retries on a fixed backoff schedule until the delivery succeeds or attempts are exhausted.
Retry backoff: +5s, +30s, +5min, +30min after first failure.
Max delivery attempts: 1 on Anonymous and Verified plans, 3 on Simple, 5 on Pro.
Events that exhaust all retry attempts are held in a dead-letter store and can be replayed manually from the console.
Delivery is at-least-once. Use the X-Idempotency-Key header on ingest to deduplicate repeated sends at the ingest layer.
Fan-Out Delivery
Route a single inbound event to multiple destinations simultaneously. Fan-out is available on the Pro plan and supports up to 20 destinations per webhook configuration.
Up to 20 destinations per config on Pro. Anonymous and Simple plans are limited to 1 destination.
A destination is automatically disabled after 10 consecutive delivery failures to protect your retry budget and prevent cascading load.
Full Visibility
Every inbound event and every outbound delivery attempt is recorded with status, response code, headers, and payload. No black boxes.
Log entries capture the full request and response for each attempt, including timing, HTTP status, and any error detail returned by the destination.
Security
Outbound requests are signed per-destination with HMAC-SHA256 so your endpoints can verify they originated from Spensr Events. Inbound signature verification is available on the Pro plan.
Per-destination outbound HMAC-SHA256 signing is available on all paid plans. Your endpoint validates the signature to confirm the request is authentic.
Inbound HMAC signature verification — confirming that events arriving at your Spensr inbound URL are genuinely from your source — is a Pro plan feature.
Event Retention and Priority
Events are retained in the log for the duration of your plan's TTL. Pro plan events also enter a priority queue, ensuring time-sensitive deliveries are processed before lower-priority traffic.
Simple plan: 48-hour event retention. Events older than 48 hours cannot be replayed.
Pro plan: 14-day event retention plus a priority delivery queue for time-sensitive events.
Cron Scheduling
Trigger events on a schedule using EventBridge-backed cron expressions. Available on the Pro plan. Define the schedule in your webhook config and Spensr Events fires the event on time — no external scheduler required.
Event Ingest
Send any JSON payload to your inbound URL via HTTP POST. The request returns HTTP 202 immediately after the event is written to the queue — your producer is never blocked waiting for downstream delivery.
Maximum payload size per event: 200 KB.
Thinking about building this yourself?
We put together an honest look at what each path involves — retry logic, observability, HMAC signing, and time to first delivery.
See the build-vs-buy breakdown →