request_resource_replacement

Ask the creator, through the connector, to pick the chat that replaces a resource's; the swap runs the moment they choose. Nothing is swapped by the call itself.

Purpose

Replacing a chat is a conversation with the creator on the connector: the bot messages them with a picker, and when they choose the resource is re-pointed, old links revoked, every active member re-admitted and a recovery operation recorded. For a degraded resource the swap spends the channel recovery allowance (or joins the recovery already absorbing swaps); for a healthy one it is on demand and free. Take an unanswered request back with withdraw_resource_replacement_request. The REST twin is POST /v1/projects/{project}/resources/{resource}/replacement/request.

Required ability

project-recovery:create

Input schema

{
    "type": "object",
    "required": [
        "resource_id"
    ],
    "properties": {
        "resource_id": {
            "type": "string",
            "description": "UUID of the resource whose chat should be replaced."
        }
    }
}

Output shape

{
    "data": {
        "resource_id": "b73c5f21-9d80-4a6e-8215-4f70ce13a9d6",
        "status": "request_sent"
    },
    "meta": {}
}

Example prompts

"Ask me to pick the new channel for Signals."

Failure modes

  • VALIDATION_FAILED — the resource is a perk rather than a place, the creator cannot be reached, or the allowance is spent with no recovery to join.
  • RESOURCE_NOT_FOUNDresource_id is not a resource the token can see.
  • AUTHENTICATION_REQUIRED — no authenticated user on the request.
  • TOKEN_MISSING_ABILITY — token lacks project-recovery:create.

How is this guide?

On this page

Subscriby is a product designed by you — for you.

No boardroom full of executives deciding what we ships next. Our roadmap always shaped by you with your feedback.

Share feedback or a request