# Who wrote last on each record

The reply marks of a record page: for every record with an email or text thread you may read, who wrote last — `direction` `inbound` (their message is the newest, so it is unanswered) or `outbound` (ours is, and they have not answered yet) — with the `medium` (email, sms or imessage), `from` (the contact, or the workspace member who sent ours), the email's `subject`, a one-line `preview`, `at`, the thread's `conversationId` and `count` (how many in a row from that side). Workspace-wide: a reply from anyone in the workspace makes a record outbound. A private thread counts only for the seats that may read it; calls and voicemail are not counted; records nobody has written to are absent. With nothing else it is every mark on the page at once, for drawing a board. It takes the rows route's narrowing — `?q=`, `?filter[<column label or id>]=<value>` repeated (`$messages` and its bound included), `?group=<groupId>`, `?rowId=<id>` repeated — and `?limit=` / `?offset=` (`page.total` says how many answer), so "who hasn't answered in 4 days" is ONE read: `?filter[$messages]=sent&filter[$messages]=<2026-10-15` (today minus four days, from the clock) names each of them with the `conversationId` to follow up on and the message they did not answer. ONLY THE NEWEST MESSAGE PER THREAD: an earlier reply that was since answered does not show here, so "no replies" is the wrong reading of an outbound mark. To see every reply, read the threads with their messages — `get_comms_conversations` with `definitionKey` (and `rowId` repeated, or none for the whole page) and `messages=N` — and look at the inbound ones (2026-10-07: Josh saw replies Neo said were not there). A date column takes bounds in its filter too (`filter[<its id>]=>=2026-09-20`), as on the rows read. `?view=<tab>` reads one of the page's tabs (a band of its status — Underwriting on deals — or one status), as the rows read does; a status filter valued by a tab's name means that tab. `dealRowId=<deal row id>` keeps the rows linked to that deal on a page that links to Deals (one deal-link column), as on `get_definitions_key_rows`.

Access class: `def:read`.

## Endpoint

`GET /v1/definitions/{key}/replies`

## Parameters

| Name | In | Type | Required |
| --- | --- | --- | --- |
| key | path | string | Yes |
| dealRowId | query | string | No |
| filter | query | object | No |

- **filter:** one entry per column: {"<column label or id>": "<value>"}, or a list to match any of several — sent as filter[<key>]=<value> in the query string. The key is a column's label (any case) or its id — a label two columns share is refused, send the id; the value may be a select's option label, a person's name or email, or the stored value, in any case; a value opening with ~ keeps the cells CONTAINING the text after it, any case ("~phoenix"; a literal leading ~ is sent as \~). The reserved key $messages takes replied (their email or text is the newest on the record, unanswered) or sent (ours is, no answer yet), and a date bound on when that last word was written beside it: ["sent", "<2026-10-15"] is no answer since before the 15th
| group | query | string | No |
| limit | query | integer | No |
| offset | query | integer | No |
| q | query | string | No |
| rowId | query | string | No |
| view | query | string | No |

## Responses

### 200

the action's answer

Content type: `application/json`.

```json
{
  "data": [
    "string"
  ],
  "page": {
    "limit": 1.5,
    "offset": 1.5,
    "total": 1.5
  }
}
```

### default

a refusal: `{"error": "<what a person needs to read>"}`. 401 no credential, 402 the plan does not include this, 403 the seat does not, 404 the thing does not exist or is not yours to see.

Content type: `application/json`.

```json
{
  "error": "string"
}
```
