---
title: "List the read receipts for a conversation item"
method: GET
path: "/conversationItems/{conversationItemId}/readReceipts"
tags: ["Conversation Item"]
---

# List the read receipts for a conversation item

`GET /conversationItems/{conversationItemId}/readReceipts`

## Request

- Base URL: `https://api.sprucehealth.com/v1`
- URL: `https://api.sprucehealth.com/v1/conversationItems/{conversationItemId}/readReceipts`
- Auth: HTTP bearer

Lists everyone who has read a specific conversation item, and when they first read it.

A read receipt records that someone opened the item in Spruce.

Teammates produce a read receipt for any item they open, whatever channel it was sent or received over. A teammate who opens an SMS, email, or fax message is recorded exactly like one who opens a secure message, because either way they read it in Spruce.

Contacts are different. A contact produces a read receipt only when they read the item over secure messaging, where Spruce can tell that they opened it. SMS, email, and fax give no way to know whether the recipient read the message, so the recipient never appears here - even though the teammates who read that same message do.

An empty list therefore means nobody has opened the item in Spruce. It does not mean the item is unread, and a contact's absence from the list does not mean they have not seen it.

For internal notes, only teammates appear, since internal notes are never visible to contacts. Receipts are ordered oldest first, and each identified reader appears at most once, at the time they first read the item.

## Path parameters

- `conversationItemId` string, required

## Response `200`

Expected response to a valid request

- object
  - `readReceipts` ConversationItemReadReceipt[], required: The read receipts for the conversation item, ordered oldest first.
    - `displayName` string, required: The name of the teammate or contact who read the conversation item.
    - `id` string: The id of the teammate or contact who read the conversation item. Unlike the author of a conversation item, a reader is always a known Spruce entity rather than an endpoint such as a phone number, so this id is stable and can be used to look the reader up. It is omitted when the reader cannot be identified, in which case `displayName` is `Unknown`. That happens when the reader's record could no longer be resolved, and in a conversation shared with another organization where a read from that organization has nobody on your side to attribute it to. The read still counts - somebody opened the item at the time given.
    - `object` string, required: String representing the object's type
    - `viewedAt` string, date-time, required: The date time the conversation item was first read by this teammate or contact.

## Other responses

- `400`: bad request
- `404`: not found
- `500`: unexpected error

## Changes

- **2026-11-03** `06e7a37de1ce`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/sprucehealth/apis/spruce-health-api/changes/conversationItems/:conversationItemId/readReceipts/get.md)

---

[API](https://skmtc.dev/sprucehealth/apis/spruce-health-api.md) - [All operations](https://skmtc.dev/sprucehealth/apis/spruce-health-api/llms.txt) - [OpenAPI document](https://skmtc.dev/sprucehealth/apis/spruce-health-api/revisions/06e7a37de1ce?raw)
