> ## Documentation Index
> Fetch the complete documentation index at: https://developer.chatsyncs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Subscriber Assign Sequences

> Enroll a subscriber into one or more Sequences via the ChatSyncs API, using comma-separated sequence IDs. Use when a developer asks how to start an onboarding/drip campaign programmatically.

Enrolls a subscriber into one or more [Sequences](https://help.chatsyncs.com/docs/whatsapp-follow-up-sequences).

<Tip>
  **Where to find a sequence's ID:** call [Sequence List](/developer-api/subscriber/list-sequences), or open
  **Chatbot Manager → Automation → Follow-up Sequences** — it's the **ID** column shown next to each sequence. See
  [Finding Your IDs & API Token](/developer-api/finding-ids#sequence-id-sequence_id) for a
  screenshot.
</Tip>

<Warning>
  **Sequence ids aren't checked.** An id that doesn't exist still returns success, and nothing is enrolled. Enrolling a
  real sequence starts its scheduled messages, so get the id from [Sequence List](/developer-api/subscriber/list-sequences).
</Warning>


## OpenAPI

````yaml POST /whatsapp/subscriber/chat/assign-sequence
openapi: 3.1.0
info:
  title: ChatSyncs Developer API
  version: 1.0.0
  description: >-
    REST API for sending WhatsApp messages and managing subscribers through
    ChatSyncs.


    **Authentication.** Send your key as the `apiToken` parameter, or as
    `Authorization: Bearer <key>` — both work on every endpoint **except Custom
    Fields List**, which only accepts the `apiToken` parameter (a Bearer header
    alone is answered with *The api token field is required.*). A wrong key
    returns HTTP 401 `{"status":"0","message":"Unauthenticated."}`; no key at
    all redirects to the login page.


    **Methods.** Every endpoint accepts both GET and POST with the same
    parameters, except Upload Media, which is POST-only. Use POST for anything
    that changes data.


    **Errors.** Failures usually come back as HTTP 200 with `"status":"0"` and
    the reason in `message`, so always check `status`. `status` is the string
    `"1"` or `"0"` on most endpoints and a boolean on a few.


    **Lists.** Endpoints that return rows put them in `message` as a list; there
    is no `data` field (Custom Fields List is the exception and uses `data`).
servers:
  - url: https://platform.chatsyncs.com/api/v1
security: []
paths:
  /whatsapp/subscriber/chat/assign-sequence:
    post:
      tags:
        - Subscriber API
      summary: Assign Sequences
      description: >-
        Sequence ids are not checked: an id that does not exist still returns
        success. Get valid ids from Sequence List. Enrolling starts the
        sequence's scheduled messages.
      operationId: assignSequence
      requestBody:
        required: true
        content:
          application/x-www-form-urlencoded:
            schema:
              type: object
              properties:
                apiToken:
                  type: string
                  description: >-
                    Your ChatSyncs API key (not a WhatsApp/Meta access token).
                    [Where to find
                    it](/developer-api/finding-ids#api-token-apitoken).
                  example: API-KEY
                phone_number_id:
                  type: string
                  description: >-
                    The WhatsApp account's phone number ID. [Where to find
                    it](/developer-api/finding-ids#phone-number-id-phone_number_id).
                  example: PHONE-NUMBER-ID
                phone_number:
                  type: string
                  description: >-
                    The subscriber's phone number, with country code, digits
                    only.
                  example: PHONE-NUMBER
                sequence_ids:
                  type: string
                  description: >-
                    Comma-separated sequence IDs, e.g. 1,4,5. [Where to find
                    it](/developer-api/finding-ids#sequence-id-sequence_id).
                  example: 1,4,5
              required:
                - apiToken
                - phone_number_id
                - phone_number
                - sequence_ids
      responses:
        '200':
          description: >-
            Standard ChatSyncs response. `status` is `"1"` on success and `"0"`
            on failure.
          content:
            application/json:
              schema:
                type: object
                properties:
                  status:
                    type: string
                    description: '`"1"` = success, `"0"` = failure.'
                  message:
                    type: string
                    description: Human-readable result message.
              examples:
                success:
                  summary: Success
                  value:
                    status: '1'
                    message: Sequences have been assigned successfully
                error:
                  summary: A required field is missing
                  value:
                    status: '0'
                    message: >-
                      The phone number id field is required., The phone number
                      field is required., The sequence ids field is required.
        '401':
          description: >-
            `apiToken` is wrong. (With no token at all the API redirects to the
            login page with HTTP 302 instead of returning JSON.)
          content:
            application/json:
              schema:
                type: object
                properties:
                  status:
                    type: string
                  message:
                    type: string
              examples:
                unauthenticated:
                  summary: Wrong apiToken
                  value:
                    status: '0'
                    message: Unauthenticated.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.