---
title: "The creator pointed a resource at a replacement channel or group: in a recovery after a ban, or on demand for a healthy resource."
method: POST
path: "recovery.resource_replaced"
tags: ["recovery.* events"]
---

# The creator pointed a resource at a replacement channel or group: in a recovery after a ban, or on demand for a healthy resource.

`POST recovery.resource_replaced` (webhook)

### When this fires

The creator swaps a resource onto another chat: a replacement channel after a ban, the standby in one click, or a healthy resource moved to a new supergroup on demand (**Swap & Grant**, which spends no allowance). The resource is re-pointed, the old links revoked and every active member's re-admission queued. One event per resource swapped, each under the `operation_id` of the recovery absorbing it.

### Caveats

- A swap onto the standby chat also fires `recovery.standby_removed` with `reason: used`.
- `project.resource.updated` fires for the same resource with `changes.space_id`, as it does for any swap.

### Related events

- `recovery.resource_failed_over`: the same swap made by the platform.
- `recovery.operation_reverted`: the swap put back inside the window.

## 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.resource_replaced', required: The event name, always `recovery.resource_replaced` 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 recovery the swap ran under; several swaps inside the grace period share one.
    - `project_id` string, uuid, required: The project.
    - `resource_id` string, uuid, required: The resource, now pointing at the replacement.
    - `resource_title` string, nullable, required: The resource's title, as plans show it.
    - `connector` string, nullable, required: The connector the chats live on.
    - `replaced_at` string, date-time, required: When the resource was re-pointed.
    - `on_demand` boolean, required: True for a Swap & Grant of a healthy resource with no open incident, which spends no allowance.

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