The creator undid a recovery inside its window: a swapped channel put back, or the previous sign-in account restored.
When this fires
Inside the undo window the creator can put a swapped resource back onto its old chat, or move their sign-in back to the previous account. A channel recovery is undone one swap at a time, so this fires once per resource put back, with resource_id; the operation itself is marked reverted when its last standing swap is undone. An account relink is undone whole, in one event with resource_id: null, and opens an account incident (relink_disputed) so support reviews it.
Caveats
- Undoing a swap re-admits every active member into the old chat again; expect a second round of member.resource_* events for the same members.
- The undo window is 24 hours from completion by default; an attempt after it is refused and fires nothing.
Related events
- recovery.operation_completed: the recovery being undone.
- recovery.incident_opened: the disputed-relink incident an account undo opens.
Headers
t=<unix seconds>,v1=<hex>: the HMAC-SHA256 of "<t>.<raw body>" under the endpoint's secret. Verify it before acting, and refuse a t more than 300 seconds from now. During a secret rotation a v0= signature under the previous secret may precede v1=.
The event's ULID, bare. The envelope's id is the same ULID prefixed evt_, so strip the prefix before comparing. Deduplicate on it: a retry carries the same id.
The event name, the same as the envelope's type.
Always application/json.
Always Subscriby-Webhooks/1.0.
Payload
Response
Your endpoint acknowledged the delivery. Any 2xx status within 30 seconds marks it delivered; the response body is ignored.
Changes
Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.