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

# Bot Flow List

> List the chatbot flows configured on a WhatsApp number via the ChatSyncs API, with each flow's unique_id. Use when a developer needs the bot_flow_unique_id that Trigger Bot Flow asks for.

Lists the chatbot flows on a WhatsApp number. The **`unique_id`** of a flow is the `bot_flow_unique_id` that
[Trigger Bot Flow](/developer-api/whatsapp/trigger-bot-flow) needs, so you no longer have to copy it out of the dashboard.

## Example Request

```bash theme={null}
curl --request GET \
  --url 'https://platform.chatsyncs.com/api/v1/whatsapp/get/bot-flow-list?apiToken=API-KEY&phone_number_id=PHONE-NUMBER-ID'
```

Each flow has an `id`, a `name`, a `unique_id` and a `status` (`"1"` active, `"0"` inactive).


## OpenAPI

````yaml GET /whatsapp/get/bot-flow-list
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. 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/get/bot-flow-list:
    get:
      tags:
        - WhatsApp API
      summary: Bot Flow List
      description: >-
        Lists the chatbot flows configured on a WhatsApp number. Use a flow's
        `unique_id` as the `bot_flow_unique_id` in Trigger Bot Flow.
      operationId: listBotFlows
      parameters:
        - name: apiToken
          in: query
          required: true
          schema:
            type: string
            example: API-KEY
          description: >-
            Your ChatSyncs API key (not a WhatsApp/Meta access token). [Where to
            find it](/developer-api/finding-ids#api-token-apitoken).
        - name: phone_number_id
          in: query
          required: true
          schema:
            type: string
            example: PHONE-NUMBER-ID
          description: >-
            The WhatsApp account's phone number ID. [Where to find
            it](/developer-api/finding-ids#phone-number-id-phone_number_id).
      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: array
                    description: The rows.
              examples:
                success:
                  summary: Success
                  value:
                    status: '1'
                    message:
                      - id: 1552533
                        name: Appointment Flow
                        unique_id: abc123
                        status: '1'
                error:
                  summary: A required field is missing
                  value:
                    status: '0'
                    message: The phone number id 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.