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

# Mark conversation as read

> Reset the thread's `unreadCount` to zero. Marks the thread read in your own inbox only: it does not send a read receipt to the contact.



## OpenAPI

````yaml /openapi.json post /v1/conversations/{conversationId}/read
openapi: 3.0.3
info:
  title: Zavu Unified Messaging Layer API
  version: 0.2.0
  description: >
    Unified multi-channel messaging API for Zavu.


    Supported channels:

    - **SMS**: Simple text messages

    - **WhatsApp**: Rich messaging with media, buttons, lists, CTA URL buttons,
    location requests, and templates

    - **Telegram**: Bot messaging with text, media, and interactive elements

    - **Email**: Transactional emails via Amazon SES


    Design goals:

    - Simple `send()` entrypoint for developers

    - Project-level authentication via Bearer token

    - Support for all WhatsApp message types (text, image, video, audio,
    document, sticker, location, contact, buttons, list, cta_url,
    location_request, reaction, template)

    - If a non-text message type is sent, WhatsApp channel is used automatically

    - 24-hour WhatsApp conversation window enforcement

    - Universal `to` field accepts phone numbers (E.164), email addresses, or
    numeric chat IDs (Telegram/Instagram/Messenger)
servers:
  - url: https://api.zavu.dev
security:
  - bearerAuth: []
paths:
  /v1/conversations/{conversationId}/read:
    post:
      tags:
        - Conversations
      summary: Mark conversation as read
      description: >-
        Reset the thread's `unreadCount` to zero. Marks the thread read in your
        own inbox only: it does not send a read receipt to the contact.
      operationId: markConversationRead
      parameters:
        - $ref: '#/components/parameters/ConversationIdParam'
      responses:
        '200':
          description: Conversation marked as read.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ConversationResponse'
        '401':
          description: Unauthorized.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '404':
          description: Conversation not found.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
      security:
        - bearerAuth: []
components:
  parameters:
    ConversationIdParam:
      name: conversationId
      in: path
      required: true
      schema:
        type: string
  schemas:
    ConversationResponse:
      type: object
      required:
        - conversation
      properties:
        conversation:
          $ref: '#/components/schemas/Conversation'
    Error:
      type: object
      required:
        - code
        - message
      properties:
        code:
          type: string
          example: invalid_request
        message:
          type: string
          example: Phone number is invalid
        details:
          type: object
          additionalProperties: true
    Conversation:
      type: object
      description: >-
        An inbox thread with one contact. A conversation groups every message
        exchanged with that contact across channels, so a contact who writes on
        WhatsApp and later by email stays in one thread.
      required:
        - id
        - contactIdentifier
        - channels
        - lastMessage
        - messageCount
        - unreadCount
        - createdAt
        - updatedAt
      properties:
        id:
          type: string
          example: js723987cyghwqxxaxcf590qd18axd95
        contactId:
          type: string
          description: >-
            ID of the contact this thread belongs to. Absent on group threads
            and on threads whose contact has not been resolved yet.
        contactIdentifier:
          type: string
          description: >-
            The key this thread is filed under: a phone number in E.164, a
            WhatsApp business-scoped user ID (BSUID), a numeric chat ID
            (Telegram/Instagram/Messenger), or a group JID. It is not always a
            phone number, so do not parse it as one.
          example: '+56912345678'
        email:
          type: string
          description: Email address of the thread, when the contact was reached by email.
        channels:
          type: array
          items:
            type: string
          description: Every channel this thread has carried messages on.
          example:
            - whatsapp
            - sms
        lastMessage:
          type: object
          description: >-
            Denormalized preview of the most recent message, so a thread list
            needs no extra fetch.
          required:
            - id
            - text
            - channel
            - direction
            - at
          properties:
            id:
              type: string
            text:
              type: string
              description: >-
                Text or caption. Empty when the last message carried no text
                (e.g. media).
            channel:
              $ref: '#/components/schemas/Channel'
            direction:
              type: string
              enum:
                - inbound
                - outbound
            at:
              type: string
              format: date-time
        senderId:
          type: string
          description: >-
            Sender that last handled this thread. Use it as the `Zavu-Sender`
            header when replying so the answer leaves from the same number the
            contact knows.
        messageCount:
          type: integer
        unreadCount:
          type: integer
          description: >-
            Inbound messages not yet marked read. Reset with POST
            /v1/conversations/{conversationId}/read.
        whatsapp:
          type: object
          description: WhatsApp identity, present when the contact adopted a username.
          properties:
            bsuid:
              type: string
              description: Business-scoped user ID. Can be used as `to` when sending.
            username:
              type: string
        group:
          type: object
          description: >-
            Present when the thread is a group chat rather than a one-to-one
            conversation.
          required:
            - id
          properties:
            id:
              type: string
            subject:
              type: string
            participantCount:
              type: integer
        createdAt:
          type: string
          format: date-time
        updatedAt:
          type: string
          format: date-time
    Channel:
      type: string
      description: Delivery channel. Use 'auto' for intelligent routing.
      enum:
        - auto
        - sms
        - sms_oneway
        - whatsapp
        - telegram
        - email
        - instagram
        - messenger
        - voice
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT

````