Bellwork
Start free
OrgSequencesSequenceidEnrollments

Who is in this sequence

Everyone enrolled, newest first, with where each of them has got to and when they are next due. `status` distinguishes the three parked states — `active` waits for the send window, `waiting` sits on a wait step, `throttled` has hit the account's daily cap — from the three finished ones.

GET
/org/sequences/{sequenceId}/enrollments

Everyone enrolled, newest first, with where each of them has got to and when they are next due. status distinguishes the three parked states — active waits for the send window, waiting sits on a wait step, throttled has hit the account's daily cap — from the three finished ones.

Authorization

AuthorizationBearer <token>

API key (sk_live_... prefix). Generate keys in the UI under Settings > API Keys, then send it as Authorization: Bearer sk_live_...

In: header

Path Parameters

sequenceId*string
Formatuuid

Response Body

application/json

application/json

application/json

curl -X GET "https://loading/api/v1/org/sequences/497f6eca-6276-4993-bfeb-53cbbbba6f08/enrollments"
{
  "data": [
    {
      "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
      "orgContactId": "f254015d-44cc-4ee5-9cea-2b17f50d6399",
      "contactId": "b5ec5d98-4bee-4da1-ad24-dde86346cb1d",
      "name": "string",
      "title": "string",
      "hasEmail": true,
      "hasLinkedin": true,
      "districtId": "dcfc5a80-c117-43e5-9945-b0823e3dd8ce",
      "districtName": "string",
      "status": "active",
      "exitReason": "string",
      "sendsCount": -9007199254740991,
      "nextRunAt": "string",
      "enrolledAt": "string",
      "currentStepKind": "string",
      "currentStepLabel": "string",
      "pendingDraftId": "91e3975a-bd4a-448b-8c22-b585b32f9b33"
    }
  ]
}
{
  "error": "string",
  "message": "string",
  "statusCode": -9007199254740991
}
{
  "error": "module_required",
  "module": "string",
  "message": "string",
  "contact": "string"
}

Stop people mid-sequence DELETE

The off switch. Clears `next_run_at`, which is what actually takes the row out of the runner's sight, and records a manual exit rather than deleting the row — so the timeline still says why the outreach stopped. People who had already finished are left alone.

Put people into a sequence POST

Enrolls contacts at the sequence's first step — and WRITES their messages: every step's email or LinkedIn note is written per person at enrollment (entries inline, the rest within minutes), stored per step, editable via the messages endpoints before anything is live. A draft or paused sequence enrolls fine; its first messages park in the review queue and nothing sends until it is turned on. **Sending uses the caller's own connected mailbox** — `enrolled_by` comes from the session, never a colleague's. Idempotent: somebody already moving through the sequence is left exactly where they are; somebody who finished is put back at the start; somebody unreachable on every channel is skipped and named in the response.