Message webhooks
Use the event subscription supported by the product you are connecting.
Outgoing product events
Verify endpoint subscriptions support verify.started, verify.succeeded, verify.failed and verify.*. Manage them through /api/v1/verify/webhooks using the documented Verify authentication. Their delivery log and test endpoint are covered in the Verify Services reference.
Task automation has a separate admin-authenticated endpoint at /api/v1/integrations/automation/webhooks for agent.completed and agent.failed. Use https://app.message.com/settings/integrations/automation for its dashboard setup.
Delivery contract
Message outgoing deliveries contain eventId, topic, createdAt and data. X-Message-Topic identifies the topic and X-Message-Signature authenticates the timestamp and raw body. HTTPS receivers must be publicly reachable; redirects are not followed. Retry and signature details are in the related guides.
Callbacks received by Message
Provider email, phone and integration callbacks are a different direction of communication. They have provider-specific routes and authentication. They are not generic webhook subscriptions for your own application.
Check the topic catalogue
Do not assume a generic conversation.*, message.*, ticket.* or call.* subscription exists because another Message product supports webhooks. For agent Inbox events, consult the authenticated real-time interface and its workspace permissions.
Test your receiver
Use a dedicated public HTTPS test receiver under your control. Check the product’s test and delivery-log controls, validate signatures and duplicate handling, then trigger a representative real event in a test account.