---
title: "A subscriber connects a platform account to their membership."
method: POST
path: "member.identity_linked"
tags: ["member.* events"]
---

# A subscriber connects a platform account to their membership.

`POST member.identity_linked` (webhook)

### When this fires

A member of the project gains a connected account on a connector: the platform account that signs them in to the portal and that the project's bot knows them by. Three doors raise it: the member completes **Connect …** from the portal's Account & Recovery screen and the project's bot confirms the account; the member signs in to the portal through a connector the project had not seen them on before; or the member taps **Use the same account** to adopt an account they already use in another of the creator's projects. Each connected account emits its own event. Nothing is emitted when an account the member already holds is confirmed again.

### Caveats

- `identity_id` is the account row, not the link: the same value appears in `member.identity_unlinked` and in the `identities` of [the member endpoint](https://docs.subscriby.net/api/v1/reference/members). The link's own `id` (what the disconnect endpoint takes) is only in the REST payloads.
- Accounts the bot creates on first contact are mirrored into the identity tables without raising this event; it is reserved for acts the member takes.

### Related events

- `member.identity_unlinked`: paired transition.

## Headers

- `SB-Signature` string, required
- `SB-Event-Id` string, required
- `SB-Event-Name` string, required
- `Content-Type` string, required
- `User-Agent` string, required

## Payload

- object: The envelope every event is delivered in.
  - `id` string, required: A ULID unique to the event, prefixed `evt_`. Every retry carries the same id, so it is the key to deduplicate on.
  - `type` 'member.identity_linked', required: The event name, always `member.identity_linked` here.
  - `created_at` string, date-time, required: When the event was emitted, server time, ISO 8601.
  - `api_version` string, required: The contract version of the payload shape, `2026-05-01` today. A breaking change to a shape ships under a new version.
  - `project_id` string, uuid, nullable, required: The project the event belongs to; null for team-scoped and billing events.
  - `data` object, required: The event-specific payload. Keys that do not apply to a given emission are omitted rather than sent as null, so check for presence.
    - `subscriber_id` string, uuid, required: Subscriber's project-scoped user id.
    - `identity_id` string, uuid, required: The connector account row. One account is one row however many projects link it.
    - `connector` string, required: Connector key the account is on.
    - `external_id` string, required: The platform's own id for the account.
    - `display_name` string, nullable, required: What the platform calls the person, when known.
    - `source` 'handshake' | 'portal' | 'adopted' | 'bot' | 'backfill', required: How the link was proven. `handshake` covers both Connect … and a portal sign-in.
    - `preferred` boolean, required: Whether this account is the one the project reaches first. A member's first account is.

## Acknowledgement `2XX`

Your endpoint acknowledged the delivery. Any 2xx status within 30 seconds marks it delivered; the response body is ignored.

## Other responses

- `default`: Any other status, a connection failure, or no answer within 30 seconds counts as a failed attempt. The delivery is retried 8 times, after 10 seconds, 30 seconds, 2 minutes, 10 minutes, 1 hour, 6 hours, 1 day, 3 days; the last failure dead-letters it, and it can be retried from the dashboard or `POST /v1/webhook-deliveries/{delivery}/retry`. After 20 consecutive failures the endpoint is paused until it is resumed.

---

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