Use webhooks for Nimriz event delivery

Receive signed, replayable lifecycle events from Nimriz in your own backend, with HMAC signatures, retry schedules, and a delivery history you can operate.

Read setup docs All integrations

Link created
Link updated
Link availability updated
Domain verification updated

Event flow

Async delivery

Link createdLink updatedDomain verified

Nimrizredact · filter · map

Webhooks

Bot traffic is excluded by default. Delivery runs off the redirect path with automatic retries.

Why Webhooks with Nimriz

Webhooks are infrastructure, so Nimriz treats them that way. Every delivery is signed with a timestamped HMAC SHA-256 signature, carries a stable event ID for deduplication, retries on failure with exponential backoff, and stays inspectable in a delivery history with manual replay.

Signed and verifiable

Each request carries a timestamped HMAC SHA-256 signature plus stable event ID, event type, and delivery attempt headers, so your backend can verify authenticity and reject replays before parsing a byte of JSON.

Built for failure

Failed deliveries retry up to six times with exponential backoff before landing in a dead-letter state. The delivery history shows status, attempts, and response codes, and any delivery can be replayed manually.

Operable without support tickets

Send test deliveries, rotate signing secrets, and pause an endpoint without deleting it. The lifecycle of a webhook endpoint is fully self-serve in the dashboard.

Signed delivery

Signed, replayable, and documented end to end.

Lifecycle events

link.created
link.updated
link.deleted
link.takedown_updated
domain.verification_updated

Signed delivery headers

X-Nim-Event-Id
X-Nim-Event-Type
X-Nim-Timestamp
X-Nim-Signature
X-Nim-Delivery-Attempt
X-Nim-Delivery-Reason

Under the hood

What Nimriz sends, and how.

Manage webhook endpoints, signed deliveries, retries, replay paths, and event schemas using the docs.

Plan note

Connector access, mapping controls, and event volume depend on plan. Use pricing and setup docs to confirm the right path before configuring production delivery.

Events: Link created, link updated, link availability updated, domain verification updated
Security: Timestamped HMAC SHA-256 signatures with self-serve secret rotation
Reliability: At-least-once delivery, six retries with exponential backoff, dead-letter on exhaustion
Operations: Delivery history, manual replay, test deliveries, endpoint pause and resume
Click streams: For click and scan event delivery, pair webhooks with the Generic HTTP destination

Guided setup

Connected in four reviewed steps.

01
Register an endpoint
Add your HTTPS endpoint and choose which event types it should receive.
02
Verify signatures
Validate the HMAC signature on raw request bytes before parsing, using the documented verification snippet.
03
Send a test delivery
Use the test delivery button to confirm your endpoint accepts and verifies a real envelope.
04
Monitor and replay
Watch the delivery history, replay failures after fixes, and rotate secrets on your schedule.

Use cases

Custom integrations
Internal data pipelines
Operational event handling

Privacy notes

Nimriz uses destination-aware payloads and privacy-aware analytics language. Do not send secrets, raw personal data, or provider credentials in public links.

Nimriz never forwards raw IP addresses or complete User-Agent strings in integration payloads. Strict privacy mode omits visitor hashes and selected granular fields such as city.

Analytics privacy docs

Pair Webhooks with the rest of the catalog.

Live

Generic HTTP

Deliver link, QR, card, and conversion events to any HTTPS endpoint with custom methods, custom headers, and fully templated JSON payloads.

Live

Zapier

Trigger Zaps instantly from link, QR, and click activity, and create or update branded links from any of the apps your team already automates with.

Live

Make

Feed link, click, and QR scan events into Make scenarios over instant webhooks, and manage branded links from modules inside the visual builder.

Live

n8n

Use the Nimriz community node to trigger self-hosted or cloud n8n workflows from link activity, and manage branded links with a dedicated operations node.