---
title: "A recovery finished and its changes stand; when it can be undone, the window is open from now."
method: POST
path: "recovery.operation_completed"
tags: ["recovery.* events"]
---

# A recovery finished and its changes stand; when it can be undone, the window is open from now.

`POST recovery.operation_completed` (webhook)

### When this fires

When the recovery's changes are in place: the creator signs in with the new account, the project's bot answers under the new token, the resource points at its replacement and re-admission has been queued. For a channel recovery this fires once, when the first swap completes; later swaps absorbed into the same operation fire `recovery.resource_replaced` only.

### Caveats

- Completion means the changes stand, not that every member is back in. Read the roll call at [the roll call endpoint](https://docs.subscriby.net/api/v1/reference/disaster-recovery) for that.
- The creator also receives the recovery report by email a few minutes later, once the first re-admissions have landed.

### Related events

- `recovery.operation_reverted`: the creator undid it inside the window.
- `recovery.resource_failed_over`, `recovery.resource_replaced`, `recovery.identity_relinked`: what the recovery did.

## 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_completed', required: The event name, always `recovery.operation_completed` 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.
    - `kind` 'account' | 'bot' | 'resources', required: What the recovery acted on.
    - `connector` string, nullable, required: The connector the recovery acted on.
    - `project_id` string, uuid, nullable, required: The project, or null for an account recovery.
    - `automatic` boolean, required: True when the platform ran it without the creator.
    - `on_demand` boolean, required: True for a Swap & Grant of a healthy resource.
    - `started_at` string, date-time, required: When it began.
    - `completed_at` string, date-time, required: When its changes were in place.
    - `revert_window_ends_at` string, date-time, nullable, required: When the undo closes; null for a bot replacement, which cannot be undone.

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