request_resource_standby

Ask the creator, through the connector, to pick the chat that becomes the standby for one resource. Nothing is linked by the call itself.

Purpose

Linking a standby is a conversation with the creator on the connector: the bot messages them with a picker, and the standby is linked the moment they choose. The API cannot name the chat directly (that would take a platform identifier), so it starts the conversation. Needs the Growth plan and the project owner. Take an unanswered request back with withdraw_resource_standby_request. The REST twin is POST /v1/projects/{project}/resources/{resource}/standby/request.

Required ability

project-recovery:create

Input schema

{
    "type": "object",
    "required": [
        "resource_id"
    ],
    "properties": {
        "resource_id": {
            "type": "string",
            "description": "UUID of the resource that should get a standby."
        }
    }
}

Output shape

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

Example prompts

"Ask me to pick a standby channel for Signals."

Failure modes

VALIDATION_FAILED — the resource is a perk rather than a place, the creator cannot be reached on the connector, the plan lacks the prevention features, or the token is not the project owner's.
RESOURCE_NOT_FOUND — resource_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.

withdraw_resource_standby_request — take it back.
recovery.standby_registered — fires when the creator picks.
Recovery API