Attention Items

Send a reply to an attention item

Send the user's plain-text reply (`body`) into the item's thread from the mailbox that holds it, to the sender of `message_id` (a message `id` from the thread endpoint), then mark the item done. **Req

POST /v2/attention-items/{attentionItemId}/reply

Parameters

Path parameters

attentionItemId

string (uuid) required

Header parameters

Idempotency-Key

string required

Required. UUID per logical operation, reused on every retry. See apps/rest-api/src/shared/idempotency.ts for the full contract. Missing → 400 BadRequest; same key + different body → 409 Conflict.

Request body

Content-Type: application/json

body

string required

message_id

string required

Example

{
  "body": "string",
  "message_id": "string"
}

Responses

200 — Successful response

Content-Type: application/json

data

object required

data.attentionItem

object required

data.attentionItem.id

string (uuid) required

data.attentionItem.user_id

string

data.attentionItem.contact_id

string (uuid) | null

data.attentionItem.source

string

data.attentionItem.source_provider_id

string

data.attentionItem.title

string

data.attentionItem.body

string | null

data.attentionItem.item_link

string | null

data.attentionItem.sender_name

string | null

data.attentionItem.sender_email

string | null

data.attentionItem.resolved_at

string (date-time)

data.attentionItem.created_at

string (date-time)

data.attentionItem.updated_at

string (date-time)

data.attentionItem.next_cursor

string

data.attentionItem.contacts

object | null

Example

{
  "data": {
    "attentionItem": {
      "id": "00000000-0000-0000-0000-000000000000"
    }
  }
}

400 — Request body failed validation.

Content-Type: application/json

(body)

any

401 — Missing or invalid API key.

Content-Type: application/json

(body)

any

403 — Valid key, insufficient permission.

Content-Type: application/json

(body)

any

404 — Resource does not exist.

Content-Type: application/json

(body)

any

409 — Request conflicts with the current state of the resource.

Content-Type: application/json

(body)

any

429 — Rate limit exceeded.

Content-Type: application/json

(body)

any

500 — Unexpected server error.

Content-Type: application/json

(body)

any

Code samples

curl https://api.prod.getdex.com/v2/attention-items/00000000-0000-0000-0000-000000000000/reply \
  --request POST \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --header 'Content-Type: application/json' \
  --data '{
  "body": "string",
  "message_id": "string"
}'

fetch('https://api.prod.getdex.com/v2/attention-items/00000000-0000-0000-0000-000000000000/reply', {
  method: 'POST',
  headers: {
    Authorization: 'Bearer YOUR_API_KEY',
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({
    body: 'string',
    message_id: 'string'
  })
})

requests.post(
    "https://api.prod.getdex.com/v2/attention-items/00000000-0000-0000-0000-000000000000/reply",
    headers={
      "Authorization": "Bearer YOUR_API_KEY",
      "Content-Type": "application/json"
    },
    json={
      "body": "string",
      "message_id": "string"
    }
)

Read an attention item's thread

Read the email thread behind an attention item live from the user's mailbox, oldest message first: `{ data: { attentionItemThread: { subject, account_email, messages: [{ id, from, reply_to, subject, d

Mark an attention item done

Set `resolved_at` to mark the item done, or `null` to reopen it. **Requires an `Idempotency-Key` header**. Returns `{ data: { attentionItem: {...} } }` with the post-update row.