What are Webhooks
Hub Chatt2.me sends HTTPS POST requests to your receiver for subscribed channel events. Registering a webhook alone does not subscribe it: create and verify the endpoint, then configure its channel events.
A delivery succeeds on any 2xx response within 30 seconds. Endpoint verification has a 10-second timeout and additionally requires the validation token in the response body. Authenticate and validate each event, persist it or enqueue it durably, then acknowledge promptly. Process accepted events with your own worker and retry policy. An acknowledged event is successful in Hub logs even if your later processing fails.
Delivered eventType | Purpose |
|---|---|
message | Inbound messages and supported outbound messages/echoes |
message_status | Delivery, read, playback, error, transcription or deletion status |
comment_automation | Instagram private reply produced by a comment rule |
flag_for_review, session_transfer, end_chat | Agent review, transfer and closure |
appointment_action_required, appointment_confirmed, appointment_alternatives_requested, appointment_rescheduled, appointment_cancelled, appointment_rejected, appointment_expired | Appointment lifecycle |
partner_app_uninstalled, account_disconnected | WhatsApp connection lifecycle |
Subscription names differ by provider; they are configured per channel and are not a webhook CRUD eventType field. See the subscription mapping and payloads.
Your endpoint must be reachable over HTTPS with a valid certificate, accept verification with an empty body, and preserve raw event bytes if signing is enabled. Custom receiver authentication is independent of the API key used to call Hub.