---
title: "List the caller's linked accounts"
method: GET
path: "/v1/me/identities"
tags: ["Identities"]
---

# List the caller's linked accounts

`GET /v1/me/identities`

## Request

- Base URL: `https://api.subscriby.net`
- URL: `https://api.subscriby.net/v1/me/identities`
- Auth: HTTP bearer

```bash
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](https://docs.subscriby.net/account/account-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.

## Response `200`

Array of `UserIdentityResource`

- object
  - `data` UserIdentityResource[], required: The items.
    - `id` string, required: The link's id, the value the unlink endpoint takes.
    - `connector` string, required: The connector the account is on, by key.
    - `purpose` string, required: `primary` for the account that signs the creator in and receives alerts; `backup` for the account registered for Disaster Recovery.
    - `source` string, required: How the link was proven: `handshake` (completed from Settings), `bot` (the account came in through the connector's own flow), `backfill` (migrated from before connectors), `portal` or `adopted`.
    - `external_id` string, required: The platform's own id for the account, so an integration can match the creator against the connector's records.
    - `display_name` string, nullable, required: What the platform calls the person.
    - `username` string, nullable, required: The account's handle when the platform has one; null otherwise.
    - `linked_at` string, required: When the account was linked, ISO 8601.
    - `verified_at` string, nullable, required: When the link was proven, ISO 8601; null while unverified.

## Other responses

- `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.
- `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)