---
title: "One step of a recovery sequence reached a member."
method: POST
path: "sequence.step_sent"
tags: ["sequence.* events"]
---

# One step of a recovery sequence reached a member.

`POST sequence.step_sent` (webhook)

### When this fires

The hourly sweep found the step due and the member's connected account took the message: the creator's text with the placeholders filled for this member, the way back to the project as a button, and the step's coupon code in the text where the creator placed it. The message goes out as an announcement, so the member's channel choices and opt-outs apply. A platform that refuses for the moment (a rate limit, a passing fault, a misconfigured installation) fires nothing and the step stays due for the next hour; one that refuses for good, or a member with no account to reach, fires nothing and ends the passage as `sequence.exited` with the reason `opted_out`. After the last step the passage completes quietly: no event marks completion.

### Related events

- `sequence.enrolled`: the passage this step belongs to.
- `sequence.converted`: the member paid again after reading it.
- `coupon.redeemed`: the step's coupon used at checkout.

## 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` 'sequence.step_sent', required: The event name, always `sequence.step_sent` 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.
    - `enrollment_id` string, uuid, required: The passage this step belongs to, as on `sequence.enrolled`.
    - `sequence_id` string, uuid, required: The sequence.
    - `step_id` string, uuid, required: The step that went out.
    - `position` integer, required: The step's place in the sequence at the time it went out.
    - `subscriber_id` string, uuid, required: The member's project-scoped user id.
    - `coupon_code` string, nullable, required: The code of the coupon the step carried, or `null` for a step without one.
    - `sent_at` string, date-time, required: When the message was delivered.

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