One event per request, compact UTF-8 JSON, at most 256 KB, from the published egress IP. Verify the signature over the raw body: base64(HMAC-SHA256(base64decode(secret without "whsec_"), webhook-id + "." + webhook-timestamp + "." + body)), compared in constant time; refuse a timestamp more than 300 seconds away; drop repeats by webhook-id (keep ids for at least 35 days). During a secret rotation webhook-signature carries two space-separated v1 values. Answer 2xx within 10 seconds and process later. Any other answer is retried: 12 attempts in total, the first included, over about 76 hours; 410 suspends the endpoint. Delivery is at least once and FIFO per contact; message.status carries previous_status for reordering. message.status can carry status expired (added within v1; previous_status queued): the ttl of the send ran out before UPPU handed it to the provider, nothing was sent, error.code is ttl_expired. When an earlier attempt got an error answer from the provider, the ttl ends the send as failed with that error instead. Rank expired with accepted and unknown, below sent: in the rare case that the provider took the message after all (UPPU could not reach it and counted the attempt as not delivered), a later sent, failed, delivered or read still moves it forward. message.received carries service_window {open, closes_at}, counted from Meta's timestamp of the message: a message Meta delivered late (received_at far after sent_at) can arrive with open false; on WhatsApp answer it with a template. On Messenger and Instagram the person's reaction opens the window as a message does (added within v1). On web chat, Telegram and e-mail service_window is null (no reply window). contact.reachability_changed (added within v1, Telegram) carries {contact_id, channel_id, identity: {type, value}, reachable, reason, occurred_at}; reason is blocked_by_contact, send_forbidden (both reachable false), unblocked_by_contact or contact_wrote (both reachable true). channel.status_changed carries {channel_id, status, previous_status, mode, previous_mode, reason}; when Meta tells UPPU that a WhatsApp Business account left UPPU, status is disconnected and reason is partner_removed, account_deleted or account_offboarded (the last two added within v1). Accept unknown reasons. conversation.updated (produced within v1; subscribe to it explicitly, new endpoints leave it off) carries ConversationUpdate: the conversation as GET /conversations/{id} returns it, change (handed_over, returned_to_bot, released, resolved, reopened, assigned, unassigned), reason, actor {type, api_key_prefix} and occurred_at. It is written only while an endpoint of the company subscribes to it, so GET /events has it only then too. Accept unknown changes, reasons and actor types. contact.updated (added within v1; subscribe to it explicitly, new endpoints leave it off) carries ContactUpdate: the contact as GET /contacts/{id} returns it to a key for all channels, changes (the names of the fields that changed: display_name, identities, merged_into, notes, attributes, language), reason and occurred_at; the envelope's channel is null. One change sends one event; a change of the team's notes alone sends none. The contact carries its identities on all channels, so an endpoint with a channel filter gets it only when all of the contact's identities and conversations are on that channel. It is written only while an endpoint of the company subscribes to it. UPPU switches it on per environment; until then it can be subscribed to and nothing is sent. The opening of a contact is not a change (message.received carries it). Accept unknown changes and reasons. account.service_stop_scheduled and account.service_resumed (added within v1; on by default for new endpoints, which can leave them out of their event list) go to every subscribed endpoint of the company whatever its channel filter; the envelope's channel is null, so GET /events lists them only for an all-channels key. account.service_stop_scheduled carries {stop_at, reason, occurred_at} (reason billing_overdue or subscription_ended): the service stops at stop_at unless the payment is recorded first. If the warning reached nobody and goes again, a second account.service_stop_scheduled names a later stop_at: the instant only moves later, and UPPU-Service-Stop-At always carries the current one. account.service_resumed carries {stopped_at, resumed_at, occurred_at}. A stopped company produces no other event; its due deliveries end dead with last_error service_stopped and are not sent by themselves after the resume (resend them). An endpoint can opt in to a weekly test event (weekly_test; added within v1): UPPU then sends webhook.test, test true, once a week. A failed weekly test is only a warning on the endpoint (weekly_test.failed_at); the endpoint is never suspended for it. template.category_changed, channel.quality_changed and template.category_change_closed (added within v1; subscribe to them explicitly, new endpoints leave them off, and they can be chosen only while UPPU's account protection is on for the company) are written whether or not an endpoint subscribes, so GET /events lists them. template.category_changed carries TemplateCategoryChangeEvent: the template as template.updated carries it and the category change UPPU recorded (kind changed, announced or created_as). A completed change also sends template.updated with field category, an announcement and a creation do not; a change back is a change of its own. Its envelope's channel is null and it is ordered per template. template.category_change_closed carries TemplateCategoryChangeClosedEvent when UPPU stops following a change, once per change: state appealed or dismissed (a team member marked it), reverted (the template's category went back), expired (60 days passed; for an announcement, 60 days after the announced date, or after UPPU saw it when Meta gave no date), gone (the template was deleted) or superseded (Meta completed the announced change; sent just before that change's template.category_changed). Its data is the template, the category change with its current values, the state and closed_at. UPPU's protection round closes reverted, expired and gone changes, so these arrive up to about 5 minutes after UPPU sees the cause. Its envelope's channel is null and it is ordered per template. channel.quality_changed carries ChannelQualityChange: a WhatsApp number's quality rating (field quality) or messaging limit (field messaging_limit) going down or up as UPPU's protection round observes it. UPPU's channel checks read the values from Meta every 15 minutes (sooner when Meta reports a change on the account) and the round compares them every 5 minutes, so the event can arrive up to about half an hour after Meta's change, or later while UPPU cannot read Meta; the first reading of a number and an unrated value send nothing. It is ordered per channel. Accept unknown kinds, states, fields and values.