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

# Mark inbox contact thread as read

> Mark one inbox contact thread as read.

Required parameters:
- contactId: contact ID path parameter.

Optional query parameters:
- senderIdentityId: target one sender-specific thread when the same contact appears under multiple sender identities
- archived: set to true to mark an archived thread as read instead of an active one. Defaults to false

Notes:
- The endpoint marks all visible conversations for that contact as read and clears unread message state.
- The endpoint is idempotent. If the thread is already read it still returns success with zero updated counts.

    > **Required scope:** `MESSAGING_WRITE`
    >
    > **Rate limit:** 30 requests per minute



## OpenAPI

````yaml https://openapi.enginy.ai/definitions.json post /v1/inboxes/:contactId/read
openapi: 3.1.0
info:
  title: Enginy API
  version: 1.0.0
  description: Public API for Enginy platform
servers:
  - url: https://openapi.enginy.ai
    description: Configured server
security: []
tags:
  - name: AI Variables
    description: >-
      Manage AI variables and discover the entity fields you can reference in
      prompts and entity requests.
  - name: Inbox
    description: >-
      Inbox endpoints for listing contact threads, reading thread messages,
      managing tags, and sending manual replies.
  - name: Workflows
    description: >-
      Build, validate, publish, run, and inspect advanced (graph) workflows,
      plus the block/condition catalog needed to author a workflow plan.
paths:
  /v1/inboxes/:contactId/read:
    post:
      tags:
        - Inbox
      summary: Mark inbox contact thread as read
      description: >-
        Mark one inbox contact thread as read.


        Required parameters:

        - contactId: contact ID path parameter.


        Optional query parameters:

        - senderIdentityId: target one sender-specific thread when the same
        contact appears under multiple sender identities

        - archived: set to true to mark an archived thread as read instead of an
        active one. Defaults to false


        Notes:

        - The endpoint marks all visible conversations for that contact as read
        and clears unread message state.

        - The endpoint is idempotent. If the thread is already read it still
        returns success with zero updated counts.

            > **Required scope:** `MESSAGING_WRITE`
            >
            > **Rate limit:** 30 requests per minute
      parameters:
        - schema:
            type: string
            description: Contact ID for the thread you want to inspect
            example: '123'
          required: true
          description: Contact ID for the thread you want to inspect
          name: contactId
          in: path
        - schema:
            type: integer
            exclusiveMinimum: 0
            description: Mark only the thread visible for one sender identity as read.
            example: 14
          required: false
          description: Mark only the thread visible for one sender identity as read.
          name: senderIdentityId
          in: query
        - schema:
            type: boolean
            description: >-
              Mark an archived thread as read instead of an active one. Defaults
              to false.
            example: false
          required: false
          description: >-
            Mark an archived thread as read instead of an active one. Defaults
            to false.
          name: archived
          in: query
      responses:
        '200':
          description: Inbox thread marked as read successfully
          content:
            application/json:
              schema:
                type: object
                properties:
                  status:
                    type: string
                    enum:
                      - success
                  message:
                    type: string
                  data:
                    type: object
                    properties:
                      contactId:
                        type: number
                        description: Contact ID
                      updatedConversationsCount:
                        type: number
                        description: >-
                          Number of conversations changed from unread to read.
                          Zero means they were already read.
                      updatedMessagesCount:
                        type: number
                        description: >-
                          Number of messages changed from unread to read. Zero
                          means they were already read.
                      success:
                        type: boolean
                        description: Whether the read-state mutation completed successfully
                    required:
                      - contactId
                      - updatedConversationsCount
                      - updatedMessagesCount
                      - success
                required:
                  - status
                  - message
                  - data
              examples:
                default:
                  summary: Mark one contact thread as read
                  value:
                    status: success
                    message: Inbox thread marked as read successfully
                    data:
                      contactId: 123
                      updatedConversationsCount: 1
                      updatedMessagesCount: 2
                      success: true
        '400':
          description: Invalid contact ID or query parameter
        '404':
          description: Contact, sender identity, or inbox thread not found
      security:
        - apiKey: []
components:
  securitySchemes:
    apiKey:
      type: apiKey
      in: header
      name: x-api-key

````