---
title: "A member row was created as a lead."
method: POST
path: "member.lead_created"
tags: ["member.* events"]
---

# A member row was created as a lead.

`POST member.lead_created` (webhook)

### When this fires

Somebody the project had never seen opened its bot, arrived through a Smart Link or a referral link, signed in to its portal or wrote to its support, and a member row was created for them with the status `lead`. It fires once per row, whichever door they came through, the moment the row is written; it never fires for a connected account adopted from a sibling project or linked by a backfill, because nobody just walked in. The lead sequences of Lead nurture enrol the member on the same event.

### Caveats

- The payload carries no name and no connected account. Resolve the member with [the member endpoint](https://docs.subscriby.net/api/v1/reference/members) using `data.subscriber_id`.
- A lead who buys later raises `subscription.activated` (a paid checkout) or `subscription.created` (an access code or a cardless trial) with the same `subscriber_id`; a lead who leaves without buying raises nothing more.

### Related events

- `sequence.enrolled`: the lead sequences the arrival enrols the member in, with `trigger` `lead`.
- `subscription.activated`: the paid-checkout join signal.

## 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.lead_created', required: The event name, always `member.lead_created` 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: The member's project-scoped user id.
    - `project_id` string, uuid, required: Mirrors the envelope `project_id`.
    - `source` 'bot' | 'portal' | 'handshake', required: How the account that brought them was linked: a bot's first contact, a portal sign-in, or a handshake the portal opened.
    - `smart_link_id` string, uuid, nullable, required: The Smart Link credited with the member when one was, else `null`.
    - `created_at` string, date-time, required: When the row was written.

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