---
title: "What is on you right now: answers you owe, then what landed"
method: GET
path: "/inbox/attention"
tags: ["Inbox"]
---

# What is on you right now: answers you owe, then what landed

`GET /inbox/attention`

## Request

- Base URL: `https://api.ziggsai.com`
- URL: `https://api.ziggsai.com/inbox/attention`
- Auth: HTTP bearer

The home page's attention block, merged here so every surface that shows it shows the same list. Two writers, one order: the pending decisions from `GET /decisions` first (somebody is blocked on those, and each carries the same resolved `decideVia` path), then your unseen mail, newest first.

A window onto the party mailboxes, not a second log, so three things are true of it. Chat messages never appear: a room renders conversation and reports its own unread, and this window neither lists nor counts them. Workspace scoped, like `GET /decisions`: what is on you IN the workspace this credential is acting in. And it marks nothing: pass the returned `seenTo` to `POST /inbox/seen` when the person has actually seen the block, and it covers exactly the rows this response carried, never the ones past the cap.

The web app stops at this window. The unfiltered party-scoped record, all kinds and every workspace, stays on `GET /inbox/feed` for a human surface that is not the web app.

## Response `200`

- InboxAttentionFeedSchema
  - `asOf` string, required
  - `items` object[], required
  - `truncated` boolean, required
  - `hasMore` boolean, required
  - `seenTo` string, nullable, required

---

[API](https://skmtc.dev/ziggsai/apis/ziggs-developer-api.md) · [All operations](https://skmtc.dev/ziggsai/apis/ziggs-developer-api/llms.txt) · [OpenAPI document](https://skmtc.dev/ziggsai/apis/ziggs-developer-api/revisions/eda79030e072?raw)