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

# Mark Conversation Status

> Mark a subscriber's conversation as resolved, reopened, archived, unarchived, blocked, or unblocked via the ChatSyncs API. Use when a developer asks how to close out or reopen a conversation programmatically, e.g. from a CRM or support-ticket workflow.

Marks a subscriber's conversation with one of six statuses — mirrors the same actions available
manually from the [Shared Inbox](https://help.chatsyncs.com/docs/inbox-labels-views-search) conversation menu.

`action` is **case-sensitive** — `resolved`, `reopen`, `archived`, `unarchived`, `blocked` or `unblocked`; `Resolved`
is rejected with `The selected action is invalid.` Each change also adds a system note to the conversation, for example
`Conversation was Reopened by …`.

## The `action_status` encoding

ChatSyncs stores a conversation's status as a number, called `action_status`. None of the endpoints in this reference
returns it, but you may see it in the dashboard or an export:

| `action_status` | Meaning |
| - | - |
| `0` | Open — after `reopen`, `unarchived`, or `unblocked` |
| `1` | Resolved |
| `2` | Archived |
| `3` | Blocked |

<Tip>
  **Where to find `phone_number_id`:** open **Chatbot Manager**, select your bot, and the phone
  number is shown at the top. See
  [Finding Your IDs & API Token](/developer-api/finding-ids#phone-number-id-phone_number_id) for a
  screenshot.
</Tip>


## OpenAPI

````yaml POST /whatsapp/subscriber/chat/mark-conversation
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/mark-conversation:
    post:
      tags:
        - Subscriber API
      summary: Mark Conversation Status
      description: >-
        `action` is case-sensitive: `resolved`, `reopen`, `archived`,
        `unarchived`, `blocked` or `unblocked`. Each one adds a note to the
        conversation.
      operationId: markConversationStatus
      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
                action:
                  type: string
                  enum:
                    - resolved
                    - reopen
                    - archived
                    - unarchived
                    - blocked
                    - unblocked
                  description: The status to set on this subscriber conversation.
                  example: resolved
              required:
                - apiToken
                - phone_number_id
                - phone_number
                - action
      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: Conversation marked as resolved 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 action field is required.
                notFound:
                  summary: Unknown contact
                  value:
                    status: '0'
                    message: Subscriber not found
                badAction:
                  summary: action is not one of the six (case-sensitive)
                  value:
                    status: '0'
                    message: The selected action is invalid.
        '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.