Disaster Recovery

Open a recovery handshake

curl -X POST https://api.subscriby.net/v1/me/recovery/handshakes \
  -H "Authorization: Bearer $SUBSCRIBY_TOKEN" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{"kind": "relink"}'

kind is relink (move the sign-in to a new account; needs the account recovery allowance) or backup (register a backup account; needs the Growth plan). Answers 201 with the pending handshake: code is the eight-character code to type into the bot, start_link the link that opens the bot on it (null when the creator cannot be reached on the connector), and the handshake expires fifteen minutes after it was minted.

post/v1/me/recovery/handshakes

Request

Base URL: https://api.subscriby.net
URL: https://api.subscriby.net/v1/me/recovery/handshakes
Auth: HTTP bearer

Headers

Idempotency-Keystring uuid required

A key unique to this operation, such as a fresh UUID. The same key replays the original 2xx response for 24 hours (with Idempotent-Replay: true), so a retry after a timeout never repeats the write; the same key with a different body is refused with 409.

Request body

kind'relink' | 'backup' required

What a completed identity handshake is for. The same deep link and the same bot-side verification serve two purposes: replacing the creator's identity after a ban (Relink), and registering a second identity ahead of time so a later ban is a one-click switch (Backup). The kind is fixed when the handshake opens, so a link minted to register a backup can never be used to replace the primary identity.

Response

201 with the pending handshake, its code and link.

Changes

No recorded changes to this operation across all 1 revision of this API.