---
title: "Switch to the backup account"
method: POST
path: "/v1/me/recovery/backup-identity/switch"
tags: ["Disaster Recovery"]
---

# Switch to the backup account

`POST /v1/me/recovery/backup-identity/switch`

## Request

- Base URL: `https://api.subscriby.net`
- URL: `https://api.subscriby.net/v1/me/recovery/backup-identity/switch`
- Auth: HTTP bearer

Moves the sign-in to the backup right now, keeping the previous account as the new backup; spends the account allowance and offers the same undo as a relink. Answers `200` with the recovery operation and raises `recovery.identity_relinked` beside the operation's `recovery.operation_started` and `recovery.operation_completed`.

## Headers

- `Idempotency-Key` string, uuid, required

## Response `200`

200 with the recovery operation.

- object
  - `data` RecoveryOperationResource, required: A recovery operation: one recovery run by the creator, by the platform on their behalf, or on demand, with its undo state.
    - `id` string, required: The operation's id, the value the revert, nudge and notify endpoints take.
    - `kind` string, required: `account` (a sign-in relink), `bot` (a bot replacement) or `resources` (a channel swap).
    - `kind_label` string, required: The kind in the connector's own words, in the creator's language.
    - `status` string, required: `started` while the recovery runs, then `completed`, `failed` (with `failure_reason`) or `reverted`.
    - `status_label` 'In progress' | 'Completed' | 'Failed' | 'Reverted', required: The status in the creator's language.
    - `connector` string, nullable, required: The connector the recovery ran on, by key; null when it concerns no connector.
    - `project_id` string, nullable, required: The project concerned; null for an account relink.
    - `project_name` string, nullable, required: That project's name; null for an account relink.
    - `grant_id` string, nullable, required: The support grant that paid for the recovery when the self-service allowance was already spent; null otherwise.
    - `automatic` boolean, required: True when the platform ran the recovery on the creator's behalf, the failover they sleep through.
    - `on_demand` boolean, required: True for a Swap & Grant of a healthy resource, which spends no allowance.
    - `failure_reason` unknown, required
    - `started_at` string, required: When the recovery started, ISO 8601. The row exists from that moment, because it is the quota ledger and the audit trail at once.
    - `completed_at` string, nullable, required: When it finished, ISO 8601; null while running or after failing.
    - `reverted_at` string, nullable, required: When it was undone, ISO 8601; null otherwise.
    - `revertible` boolean, required: Whether the creator may still undo it **right now**: completed, of a kind that can be undone (an account relink or a channel swap, never a bot replacement), and inside the undo window. Show the undo exactly when this is true.
    - `revert_window_ends_at` string, nullable, required: When the undo window closes, ISO 8601; null for a recovery that cannot be undone.

## Other responses

- `400`: `IDEMPOTENCY_KEY_MISSING`: every write needs an `Idempotency-Key` header. Send a fresh UUID per distinct operation.
- `401`: `AUTHENTICATION_REQUIRED`: the request carries no bearer token, or one that is revoked, malformed, or minted for another environment (an `sbt_test_` token on production).
- `403`: `TOKEN_MISSING_ABILITY`: the token is valid but does not carry the ability this endpoint requires; `error.context.required_ability` names the one to grant. An endpoint that also checks who owns a row or which tier the account is on answers `FORBIDDEN`, `TEAM_TIER_REQUIRED` or `CONNECTOR_TIER_REQUIRED` with the same status, and says so in its own description.
- `409`: `IDEMPOTENCY_KEY_REUSED`: the key was already used in the last 24 hours with a different request body.
- `422`: `VALIDATION_FAILED`: when no backup is registered, the account allowance is spent, or the caller is not the account holder.
- `425`: `IDEMPOTENCY_REPLAY_IN_PROGRESS`: the first request with this key is still running; retry in a few seconds and the original response is replayed.
- `429`: `RATE_LIMITED`: the token has spent its 300 requests a minute or 10,000 an hour; `Retry-After` says when the next one is accepted.

---

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