List the caller's linked accounts

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

Every account linked to the caller's creator account, by connector then purpose. Never paginated.

purpose is primary (the account that signs you in and receives alerts) or backup (the account registered for Disaster Recovery).
source says how the link was proven: handshake (you completed a link from Settings), bot (the account came in through the connector's own flow), backfill (migrated from before connectors), portal or adopted.
external_id is the platform's own id for the account, username its handle when the platform has one. Secrets and chat rows are never returned.

Linking has no endpoint. Linking is a two-sided proof: you open it from Settings → Security → Linked accounts and finish it from the account itself, by opening the link or sending the code to the connector's bot. A token cannot stand in for a person on the connector, so there is nothing to POST here.

Requires ability

account:read

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

MCP tool

get_me

Runs the same action from an agent, behind the same ability.

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

Array of UserIdentityResource

data*array<>

The items.

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/identities"

{  "data": [    {      "id": "0c2d8a7e-4b1f-4d3e-9a6b-2f5e8c1d7a90",      "connector": "telegram",      "purpose": "primary",      "source": "handshake",      "external_id": "123456789",      "display_name": "Ada Lovelace",      "username": "ada",      "linked_at": "2026-09-12T10:05:00Z",      "verified_at": "2026-09-12T10:05:00Z"    }  ]}

Type definitions

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

export interface Response {  data: UserIdentityResource[];}export interface UserIdentityResource {  id: string;  connector: string;  purpose: string;  source: string;  external_id: string;  display_name: string | null;  username: string | null;  linked_at: string;  verified_at: string | null;}

List the caller's linked accounts

AuthorizationCopy Anchor Link

ResponsesCopy Anchor Link

Authorization

Responses