Know what happened, in your own system.
Hopwire tells your system about each change as it happens. Events are signed, carry the tenant and environment, and can be replayed from the log.
What you get
Message lifecycle
Sent, delivered, read, failed, expired, unknown, cancelled, suppressed and fallback events, each with the reason code.
Replies and opt-outs
Inbound WhatsApp replies, STOP and START, as they arrive.
Things that need attention
Template status changes and sender restrictions, so you can act before sends fail.
Retries, then a clear stop
Failed deliveries retry for about three days. Then the endpoint is disabled and its owners are emailed.
Replay from the log
Inspect every attempt and replay a delivery once your endpoint is fixed.
Filter by tenant and event
Point each endpoint at the tenants and event types it cares about.
Tenant lifecycle events
At launchOnboarding steps, approvals and quality changes for platforms whose businesses never log in.
Questions
Do webhooks include OTP codes?
No. They never include variable values, and the recipient number is masked.
Are events in order?
Not guaranteed. Each message event carries a sequence number, and every event has an ID to deduplicate on.
Can I send a test event?
Yes. Testing an endpoint sends a webhook.test event.
Related
- WebhooksAvailableStandard Webhooks signatures, at-least-once delivery, event IDs to deduplicate on, secret rotation and replay.
- Message explorerAvailableFind any message and open a step-by-step audit trail of its checks, attempts, provider responses and webhooks, with sensitive values masked.
- ConversationsAvailableReceive WhatsApp replies and opt-out keywords as webhooks, routed to the right business. A conversations view is planned for Release 1.
Start with the beta.
Hopwire is free during the invite-only beta. Tell us what you send and we will reply by email.