---
title: "Receive Seen reports"
method: POST
path: "receive-messages-api-seen-reports"
tags: ["platform", "messages-api", "messages-api-status-reports"]
---

# Receive Seen reports

`POST receive-messages-api-seen-reports` (webhook)

Incoming Seen Reports will be forwarded to this endpoint. Please provide the endpoint’s URL to your Account Manager and they will set it up for you. Alternatively you can specify the endpoint per each message via the `webhooks > seen > url` parameter. Contact support@infobip.com if you require help.

## Payload

- 899caf445aab842b03fe1d74e4afd7097f0161dae66538ffa05bba2f153d708fMessagesApiSeenReport
  - `results` 899caf445aab842b03fe1d74e4afd7097f0161dae66538ffa05bba2f153d708fMessagesApiSeenResult[], required: Collection of reports, one per every message.
    - `event` string, required: Event type (seen report in this case).
    - `channel` 'RCS' | 'VIBER_BM' | 'VIBER_BOT' | 'WHATSAPP', required: Messaging channel used for sending an event.
    - `sender` string, required: The sender ID which can be alphanumeric or numeric (e.g., `CompanyName`).
    - `destination` string, required: Message destination address.
    - `sentAt` string, required: Tells when the message was sent. Has the following format: `yyyy-MM-dd'T'HH:mm:ss.SSSZ`.
    - `seenAt` string, required: Tells when the message was seen. Has the following format: `yyyy-MM-dd'T'HH:mm:ss.SSSZ`.
    - `bulkId` string, required: The ID that uniquely identifies the request.
    - `messageId` string, required: The ID that uniquely identifies the received message.
    - `callbackData` string: Value of the `callbackData` field from the MT message (if exists) or from the MO Action setup (if exists).
    - `platform` 899caf445aab842b03fe1d74e4afd7097f0161dae66538ffa05bba2f153d708fPlatform: Platform options. For more details, see [documentation](https://www.infobip.com/docs/cpaas-x/application-and-entity-management).
      - `entityId` string: Used when specifying an entity in outbound send requests. It is also returned in notification events. For detailed usage, refer to the [documentation](https://www.infobip.com/docs/cpaas-x/application-and-entity-management).
      - `applicationId` string: Used when specifying an application in outbound send requests. It is also returned in notification events. For detailed usage, refer to the [documentation](https://www.infobip.com/docs/cpaas-x/application-and-entity-management).
    - `campaignReferenceId` string: ID of a campaign that was sent in the message.
    - `contact` 899caf445aab842b03fe1d74e4afd7097f0161dae66538ffa05bba2f153d708fMessagesApiContact: Contact information of the end user.
      - `name` string: Contact's display name.
      - `phoneNumber` string: Contact's phone number. For WhatsApp, it may be omitted after username launch if the user has adopted a username.
      - `userId` string: User ID. For WhatsApp, this value is Business-Scoped User ID (BSUID) and is always present once available.
      - `parentUserId` string: Parent user ID. For WhatsApp, this field is present for linked business portfolios.
      - `username` string: Username. For WhatsApp, this field is present if the end user has adopted a Meta username.

## Acknowledgement `200`

Your server returns this code if it accepts the callback.

---

[API](https://skmtc.dev/infobip/apis/infobip-openapi-specification.md) - [All operations](https://skmtc.dev/infobip/apis/infobip-openapi-specification/llms.txt) - [OpenAPI document](https://skmtc.dev/infobip/apis/infobip-openapi-specification/revisions/9dcbbaf902de?raw)