---
title: "The creator undid a recovery inside its window: a swapped channel put back, or the previous sign-in account restored."
method: POST
path: "recovery.operation_reverted"
tags: ["recovery.* events"]
---

# The creator undid a recovery inside its window: a swapped channel put back, or the previous sign-in account restored.

`POST recovery.operation_reverted` (webhook)

### 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

- `SB-Signature` string, required
- `SB-Event-Id` string, required
- `SB-Event-Name` string, required
- `Content-Type` string, required
- `User-Agent` string, required

## Payload

- object: The envelope every event is delivered in.
  - `id` string, required: A ULID unique to the event, prefixed `evt_`. Every retry carries the same id, so it is the key to deduplicate on.
  - `type` 'recovery.operation_reverted', required: The event name, always `recovery.operation_reverted` here.
  - `created_at` string, date-time, required: When the event was emitted, server time, ISO 8601.
  - `api_version` string, required: The contract version of the payload shape, `2026-05-01` today. A breaking change to a shape ships under a new version.
  - `project_id` string, uuid, nullable, required: The project the event belongs to; null for team-scoped and billing events.
  - `data` object, required: The event-specific payload. Keys that do not apply to a given emission are omitted rather than sent as null, so check for presence.
    - `operation_id` string, uuid, required: The operation being undone.
    - `kind` 'account' | 'resources', required: `account` or `resources`; a bot replacement cannot be undone.
    - `connector` string, nullable, required: The connector the recovery acted on.
    - `project_id` string, uuid, nullable, required: The project, or null for an account recovery.
    - `resource_id` string, uuid, nullable, required: The resource put back onto its old chat; null for an account relink.
    - `reverted_at` string, date-time, required: When the undo happened.

## Acknowledgement `2XX`

Your endpoint acknowledged the delivery. Any 2xx status within 30 seconds marks it delivered; the response body is ignored.

## Other responses

- `default`: Any other status, a connection failure, or no answer within 30 seconds counts as a failed attempt. The delivery is retried 8 times, after 10 seconds, 30 seconds, 2 minutes, 10 minutes, 1 hour, 6 hours, 1 day, 3 days; the last failure dead-letters it, and it can be retried from the dashboard or `POST /v1/webhook-deliveries/{delivery}/retry`. After 20 consecutive failures the endpoint is paused until it is resumed.

---

[API](https://skmtc.dev/memberpass/apis/subscriby-rest-api.md) · [All operations](https://skmtc.dev/memberpass/apis/subscriby-rest-api/llms.txt) · [OpenAPI document](https://skmtc.dev/memberpass/apis/subscriby-rest-api/revisions/59c4df91d764?raw)