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

# Read saved Messenger history import status

> Use for the latest existing Messenger native history import receipt on a discovered matching channel. Counters distinguish scanned, published, deduplicated and failed messages; null means no receipt is available. This reader does not launch an import, fetch arbitrary provider history or backfill old evidence. New imports remain in the native dashboard flow. Requires a current business-admin-owned credential. Requires `channels:read`.



## OpenAPI

````yaml /openapi.json get /channels/{channelId}/messenger/history-import
openapi: 3.0.3
info:
  title: Visito M2M API
  version: 1.0.0
  description: >-
    Tenant-scoped server-to-server API for channels, conversations, commerce,
    custom AI tools, and WhatsApp templates. Send operations are asynchronous
    and return queued acknowledgements. Expansion adds conversation controls,
    knowledge, sales opportunities, delivery status, reporting, and signed
    webhooks.
servers:
  - url: https://platform-api.visitoai.com/m2m/v1
    description: Production
security:
  - bearerAuth: []
tags:
  - name: Channels
  - name: Conversations
  - name: Commerce
  - name: Custom tools
  - name: WhatsApp templates
  - name: Properties
  - name: Knowledge
  - name: Sales CRM
  - name: Delivery
  - name: Reporting
  - name: Webhooks
paths:
  /channels/{channelId}/messenger/history-import:
    get:
      tags:
        - Channels
      summary: Read saved Messenger history import status
      description: >-
        Use for the latest existing Messenger native history import receipt on a
        discovered matching channel. Counters distinguish scanned, published,
        deduplicated and failed messages; null means no receipt is available.
        This reader does not launch an import, fetch arbitrary provider history
        or backfill old evidence. New imports remain in the native dashboard
        flow. Requires a current business-admin-owned credential. Requires
        `channels:read`.
      operationId: get_messenger_channel_history_import
      parameters:
        - name: channelId
          in: path
          required: true
          description: >-
            Stored channel.id from list_channels or get_channel. Provider page,
            phone, account and WABA IDs are not this ID.
          schema:
            type: string
            pattern: ^[a-fA-F0-9]{24}$
      responses:
        '200':
          description: Read saved Messenger history import status
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ChannelHistoryImport'
        default:
          $ref: '#/components/responses/Error'
      security:
        - bearerAuth: []
components:
  schemas:
    ChannelHistoryImport:
      type: object
      properties:
        ok:
          type: boolean
        import:
          type: object
          properties:
            id:
              type: string
            status:
              type: string
            errorCode:
              type: string
            maxConversations:
              type: integer
            maxMessagesPerConversation:
              type: integer
            maxMessages:
              type: integer
            conversationsScanned:
              type: integer
            messagesDiscovered:
              type: integer
            messagesPublished:
              type: integer
            messagesDeduplicated:
              type: integer
            messagesFailed:
              type: integer
            truncated:
              type: boolean
            queuedAt:
              type: string
              format: date-time
            startedAt:
              type: string
              format: date-time
            completedAt:
              type: string
              format: date-time
          additionalProperties: false
          nullable: true
      additionalProperties: false
      required:
        - ok
        - import
    ErrorResponse:
      type: object
      required:
        - error
      properties:
        error:
          type: object
          required:
            - code
            - message
          properties:
            code:
              type: string
              example: M2M_AUTH_INSUFFICIENT_SCOPE
            message:
              type: string
            details:
              type: object
              additionalProperties: true
      example:
        error:
          code: M2M_AUTH_INSUFFICIENT_SCOPE
          message: M2M credential does not have required scope.
          details:
            requiredScopes:
              - conversations:write
            missingScopes:
              - conversations:write
  responses:
    Error:
      description: Structured error
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: Visito M2M API key
      description: Server-side tenant-scoped credential created from Build > API Keys.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.