Bellwork
Start free
OrgSequencesSequenceidEnrollmentsEnrollmentidMessages

One person's planned messages

The whole conversation-to-be, in the order the sequence will happen to this person. Written at enrollment; whatever is stored here is what each step sends verbatim when it comes due. The message currently parked in the review queue is flagged `is_pending` — send or skip it there.

GET
/org/sequences/{sequenceId}/enrollments/{enrollmentId}/messages

The whole conversation-to-be, in the order the sequence will happen to this person. Written at enrollment; whatever is stored here is what each step sends verbatim when it comes due. The message currently parked in the review queue is flagged is_pending — send or skip it there.

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
enrollmentId*string
Formatuuid

Response Body

application/json

application/json

application/json

application/json

curl -X GET "https://loading/api/v1/org/sequences/497f6eca-6276-4993-bfeb-53cbbbba6f08/enrollments/497f6eca-6276-4993-bfeb-53cbbbba6f08/messages"
{
  "data": [
    {
      "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
      "node_id": "6e0bdcac-9717-4a6f-972e-97489dffeb0c",
      "node_label": "string",
      "node_kind": "string",
      "subject": "string",
      "body": "string",
      "is_pending": true
    }
  ]
}
{
  "error": "string",
  "message": "string",
  "statusCode": -9007199254740991
}
{
  "error": "module_required",
  "module": "string",
  "message": "string",
  "contact": "string"
}
{
  "error": "string",
  "message": "string",
  "statusCode": -9007199254740991
}

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.

Edit a planned message PATCH

Replace the model's words with a person's. The runner consumes stored messages verbatim, so this edit IS what sends when the step comes due.