> ## 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.

# Account Connect

> Connect a WhatsApp Business Account to ChatSyncs via the API, using a WhatsApp Business Account ID and Meta access token. Use when a developer asks how to programmatically connect a WABA instead of doing it through the dashboard.

Connects a WhatsApp Business Account (WABA) to ChatSyncs programmatically — a POST request
since it creates/updates a connection, and because `access_token` is sensitive and shouldn't be
sent as a GET query parameter.

<Tip>
  **Where to find `user_id`:** call [Get My Info](/developer-api/user/get-my-info) first — copy
  the `user_id` value from its response and use that here.
</Tip>

<Tip>
  **Where to find `whatsapp_business_account_id` and `access_token`:** for a **first-time**
  connection, both come from **Meta**, not ChatSyncs — see
  [Meta Developer Account Setup](/meta-api/concepts/meta-developer-account-setup). If the WABA is
  **already connected**, `whatsapp_business_account_id` is also shown right on the same
  **WhatsApp → Connect Account** card as `phone_number_id` — see
  [Finding Your IDs & API Token](/developer-api/finding-ids#business-account-id-whatsapp_business_account_id)
  for a screenshot.
</Tip>


## OpenAPI

````yaml POST /whatsapp/account/connect
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.
servers:
  - url: https://platform.chatsyncs.com/api/v1
security: []
paths:
  /whatsapp/account/connect:
    post:
      tags:
        - WhatsApp API
      summary: Account Connect
      description: ' Prefer POST for this endpoint -- access_token is sensitive and sending it via GET risks it being logged by servers/proxies/browser history. GET is provided for quick manual testing only.'
      operationId: accountConnect
      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
                user_id:
                  type: integer
                  description: >-
                    The ChatSyncs user ID of the account owner. Get this from
                    [Get My Info](/developer-api/user/get-my-info).
                  example: 123
                whatsapp_business_account_id:
                  type: string
                  description: >-
                    The WhatsApp Business Account ID from Meta. [Where to find
                    it](/developer-api/finding-ids#business-account-id-whatsapp_business_account_id).
                  example: WHATSAPP-BUSINESS-ACCOUNT-ID
                access_token:
                  type: string
                  description: >-
                    A Meta access token for the WhatsApp Business Account. See
                    [Meta Developer Account
                    Setup](/meta-api/concepts/meta-developer-account-setup).
                  example: ACCESS-TOKEN
              required:
                - apiToken
                - user_id
                - whatsapp_business_account_id
                - access_token
      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: Success.
                error:
                  summary: Error
                  value:
                    status: '0'
                    message: Invalid request.

````