Get the caller's recovery account

curl https://api.subscriby.net/v1/me/recovery \  -H "Authorization: Bearer $SUBSCRIBY_TOKEN"

Recovering the creator's sign-in account, and keeping a backup account ahead of a ban, are two-sided handshakes: the API mints a code, the creator taps the link (or types the code) from the account to detect, the connector records which account that was, and the API confirms. Both sides have to agree, which is what keeps a leaked link from binding a stranger. These endpoints live under /v1/me because they are about the caller, never a project, and the actions behind them refuse anyone but the account holder.

These flows are deliberately not offered as MCP tools: moving a sign-in is a human act, and get_me already shows which accounts are linked.

primary_display_name and backup_display_name name the accounts as the connector reported them; their identifiers on the connector never appear.
relink_handshake and backup_handshake are the newest handshake of each kind, in whatever state, so a client can pick up a flow the creator started on the dashboard or in the bot.

Requires ability

project-recovery:view

The token must hold this ability, or the call is refused with 403.

Authorization

bearerToken

AuthorizationBearer <token>

A personal access token minted on the dashboard under Settings, then Tokens, sent as Authorization: Bearer sbt_live_…. The token carries the abilities each endpoint lists under Requires ability and is frozen to one team.

In: header

Responses

200OKapplication/json

200 with the summary.

data*

The response's payload.

401UnauthorizedAUTHENTICATION_REQUIREDapplication/json

The request carries no bearer token, or one that is revoked, malformed, or minted for another environment (an sbt_test_ token on production).

error*

The one envelope every failure uses.

403ForbiddenTOKEN_MISSING_ABILITYapplication/json

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.

error*

The one envelope every failure uses.

429Too many requestsRATE_LIMITEDapplication/json

The token has spent its 300 requests a minute or 10,000 an hour; Retry-After says when the next one is accepted.

error*

The one envelope every failure uses.

Call it from your code

A sample request in your language, the body each status answers with, and the types to hold them.

curl -X GET "https://example.com/v1/me/recovery"

{  "data": {    "primary_display_name": "Ada",    "backup_identity_registered": true,    "backup_display_name": "Backup Ada",    "relink_handshake": null,    "backup_handshake": {      "id": "0c4f9e2a-7b31-4d68-a5e2-9f1c3b7d6e80",      "kind": "backup",      "kind_label": "Backup account",      "status": "consumed",      "status_label": "Consumed",      "code": "K7PM2QXA",      "start_link": null,      "connector": "telegram",      "detected_display_name": "Backup Ada",      "detected_identity_id": "3c9e1f7a-8b25-4d60-a1f4-7e2c5b9d0a18",      "expires_at": "2026-09-01T14:35:00Z",      "completed_at": "2026-09-01T14:22:09Z",      "created_at": "2026-09-01T14:20:00Z"    }  }}

Type definitions

The shapes above as types, ready to paste into your client.

export interface Response {  data: RecoveryAccountResource;}export interface RecoveryAccountResource {  primary_display_name: string | null;  backup_identity_registered: boolean;  backup_display_name: string | null;  relink_handshake: unknown[] | null;  backup_handshake: unknown[] | null;}

Get the caller's recovery account

AuthorizationCopy Anchor Link

ResponsesCopy Anchor Link

Authorization

Responses