GET

List a project's sequences

/v1/projects/{project}/sequences in the Win-back Sequences API.

curl "https://api.subscriby.net/v1/projects/7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13/sequences?active=true&per_page=25" \  -H "Authorization: Bearer sbt_..."

Pages the project's sequences, newest first, each with its steps in order and how it has done: every member ever enrolled, the members still receiving steps, the members who received every step, and the members a payment brought back while they were enrolled. active keeps the running or the paused ones; trigger keeps one trigger; sort_by takes created_at, name or updated_at.

Requires ability

project-sequence:view-any

The token must hold this ability, or the call is refused with 403.

MCP tool

Runs the same action from an agent, behind the same ability.

Authorization

bearerToken

AuthorizationBearer <token>

A personal access token minted on the dashboard under Settings, then Tokens, sent as Authorization: Bearer sbt_live_…. The token carries the abilities each endpoint lists under Requires ability and is frozen to one team.

In: header

Path Parameters

project*string

The project, resolved by the route binder.

Formatuuid

Query Parameters

active?string

Keep only running sequences (true) or only paused ones (false). Omit for both.

Value in

"true"
"false"
"1"
"0"

trigger?SequenceTrigger

Keep only the sequences on one trigger: churned today; lead, stalled_checkout and trial_ending are reserved.

Value in

"churned"
"lead"
"stalled_checkout"
"trial_ending"

page?integer

The 1-based page to return. A page past the last answers an empty data array with meta.total still filled, so a loop can stop without guessing.

Range1 <= value

Default1

per_page?integer

Rows per page, 1 to 100. A higher value clamps to the cap silently. Defaults to 25.

Range1 <= value <= 100

Default25

sort_by?string

The column to order by. Defaults to created_at; a column the endpoint does not offer falls back to the default rather than failing.

Default"created_at"

sort_direction?string

asc or desc. Defaults to desc.

Default"desc"

Value in

"asc"
"desc"

limit?integer

Legacy alias of per_page, kept for clients that predate it. per_page wins when both are sent.

Range1 <= value <= 100

Responses

200OKapplication/json

The page of sequences, newest first, each with its steps and its counts.

401UnauthorizedAUTHENTICATION_REQUIREDapplication/json

The request carries no bearer token, or one that is revoked, malformed, or minted for another environment (an sbt_test_ token on production).

403ForbiddenTOKEN_MISSING_ABILITYapplication/json

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.

404Not foundRESOURCE_NOT_FOUNDapplication/json

An id in the path names nothing the token can see. TENANT_MISMATCH: the project sits outside the token's scope:project: allow-list, or the token carries no team scope. Both answer 404 rather than 403 so that existence outside the token's scope cannot be inferred.

422Validation failedVALIDATION_FAILEDapplication/json

The payload broke a rule, and error.fields maps each offending key to its messages. A refusal from the domain, such as a plan that cannot go on sale or a member who cannot be removed, uses the same code with error.message saying why and no fields.

429Too many requestsRATE_LIMITEDapplication/json

The token has spent its 300 requests a minute or 10,000 an hour; Retry-After says when the next one is accepted.

Call it from your code

A sample request in your language, the body each status answers with, and the types to hold them.

curl -X GET "https://example.com/v1/projects/497f6eca-6276-4993-bfeb-53cbbbba6f08/sequences"

{  "data": [    {      "id": "9d2f4b6a-1c3e-4f58-8a7b-6e5d4c3b2a19",      "project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13",      "name": "Win-back after churn",      "trigger": "churned",      "active": true,      "steps": [        {          "id": "4e8a2c6d-7b1f-4d93-a5c0-8f2e1b7d6c54",          "position": 1,          "delay_days": 3,          "body": "Hi {name}, your place in {project} is still here whenever you want it back: {link}",          "coupon": null        }      ],      "counts": {        "enrolled": "string",        "open": "string",        "completed": "string",        "won_back": "string"      },      "created_at": "2026-10-01T09:00:00+00:00",      "updated_at": "2026-10-10T08:00:00+00:00",      "deleted_at": null    }  ],  "links": {    "first": "string",    "last": "string",    "prev": "string",    "next": "string"  },  "meta": {    "current_page": 1,    "from": 1,    "last_page": 1,    "links": [      {        "url": "string",        "label": "string",        "active": true      }    ],    "path": "string",    "per_page": 0,    "to": 1,    "total": 0  }}

Type definitions

The shapes above as types, ready to paste into your client.

export interface Response {  data: SequenceResource[];  links: Links;  meta: Meta;}export interface SequenceResource {  id: string;  project_id: string;  name: string;  trigger: string;  active: boolean;  steps?: SequenceStepResource[];  counts: Counts;  created_at: string | null;  updated_at: string | null;  deleted_at: string | null;}export interface SequenceStepResource {  id: string;  position: number;  delay_days: number;  body: string;  coupon?: Coupon | null;}export interface Coupon {  id: string;  code: string;}export interface Counts {  enrolled: string;  open: string;  completed: string;  won_back: string;}export interface Links {  first: string | null;  last: string | null;  prev: string | null;  next: string | null;}export interface Meta {  current_page: number;  from: number | null;  last_page: number;  links: Link[];  path: string | null;  per_page: number;  to: number | null;  total: number;}export interface Link {  url: string | null;  label: string;  active: boolean;}

How is this guide?

Last updated on October 12, 2026 at 17:03 UTC

Win-back Sequences API

A win-back sequence is the ordered set of messages a member who leaves receives on the days the creator chose: each step waits a number of days after the one before (the first after the trigger), says what the creator wrote with {name}, {project}, {coupon}, {discount} and {link} filled per member, carries the way back as a button and, optionally, a coupon.

Create a sequence

/v1/projects/{project}/sequences in the Win-back Sequences API.