Platform

Webhook architecture

Tamanor verifies every inbound webhook's signature, routes Facebook and Instagram events through one unified connector, rejects replays, and always resolves the tenant from the connected account — never from the payload.

Trustworthy by construction

Inbound events are verified with an HMAC signature before anything is trusted. A stable dedup key rejects replayed deliveries. Only signature-valid events are ever processed; forged or unsigned events are stored for audit but never acted upon.

The tenant is always derived from the matched connected account, never from the webhook body, so a crafted payload cannot cross tenant boundaries.

Frequently asked questions

What stops a replayed or forged webhook?
Signature verification plus a unique dedup key: replays collapse to one event and unsigned events are never processed.
Webhook architecture — Tamanor signed, deduplicated events