update_recovery_settings

Change one project's Disaster Recovery settings: switch automatic failover on or off (with the fee consent), and choose how members are told after a swap. Fields left out keep their value.

Purpose

Drives the two actions the Prevention page drives, so a refusal is the same sentence the dashboard shows. Switching auto_failover on needs accepts_email_fee: true in the same call, because a failover may email the members the bot cannot reach at a per-email fee the creator must agree to, and it needs the Growth plan. email_delivery is self or platform. Only the project owner may change these; a teammate is refused. Returns the settings as they now stand. The REST twin is PATCH /v1/projects/{project}/recovery/settings.

Required ability

project-recovery:update

Input schema

{
    "type": "object",
    "required": [
        "project_id"
    ],
    "properties": {
        "project_id": {
            "type": "string",
            "description": "UUID of the project."
        },
        "auto_failover": {
            "type": "boolean",
            "description": "Switch automatic failover on (true) or off (false). Omit to leave it."
        },
        "accepts_email_fee": {
            "type": "boolean",
            "description": "Required true when switching failover on."
        },
        "email_delivery": {
            "type": "string",
            "description": "`self` or `platform`. Omit to leave it.",
            "enum": [
                "self",
                "platform"
            ]
        }
    }
}

Output shape

{
    "data": {
        "project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13",
        "auto_failover_enabled": true,
        "auto_failover_email_consented_at": "2026-09-01T14:20:00Z",
        "email_delivery": "platform",
        "email_delivery_label": "Subscriby emails them",
        "standby_installation_registered": true
    },
    "meta": {}
}

Example prompts

"Turn on automatic failover for Research Premium; yes, I accept the email fee."

"Have Subscriby email my members after a channel swap instead of me."

Failure modes

  • VALIDATION_FAILED — failover switched on without accepts_email_fee, the plan lacks the prevention features, an unknown email_delivery, or the token is not the project owner's; the context carries the reason.
  • RESOURCE_NOT_FOUNDproject_id is not a project the token can see.
  • AUTHENTICATION_REQUIRED — no authenticated user on the request.
  • TOKEN_MISSING_ABILITY — token lacks project-recovery:update.

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