---
title: "A subscriber joins by redeeming an access code against a paid plan."
method: POST
path: "member.joined"
tags: ["member.* events"]
---

# A subscriber joins by redeeming an access code against a paid plan.

`POST member.joined` (webhook)

### When this fires

A subscriber redeems an access code against a plan with no trial window, gaining access to the project.

That is the only path that emits this event. A card, wallet, or crypto checkout emits `subscription.activated` and `payment.succeeded`, but no `member.*` join event at all. If the redeemed plan carries a trial, `member.trial_joined` fires instead of this event.

> This event is **access-code-only**. Paid checkouts do not emit it. For a paying audience, use `subscription.activated` as the join signal.

### Caveats

- The payload does not carry the subscriber's connected accounts. Resolve them with [the member endpoint](https://docs.subscriby.net/api/v1/reference/members) using `data.subscriber_id`, which embeds `identities`, one row per connected account with the connector key and the platform's own id.
- Resource-level grants emit separate `member.resource_added` events as the dispatcher processes each invite.
- This event always accompanies `subscription.created` and `access_code.redeemed` for the same subscription.

### Related events

- `subscription.activated`: the paid-checkout join signal.
- `subscription.created`: fires alongside on this path.
- `member.trial_joined`: trial counterpart.

## 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.joined', required: The event name, always `member.joined` 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.
    - `subscription_id` string, uuid, required: Subscription that triggered the join.
    - `project_id` string, uuid, required: Mirrors the envelope `project_id`.
    - `plan_id` string, uuid, required: Plan the subscription is on.
    - `subscriber_id` string, uuid, required: Subscriber's project-scoped user id.
    - `access_code` string, required: The **full redeemed code**, not masked. Always present.

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