# GET /api/v1/attention/{item_id}

> Get single attention item

- **Tag:** attention
- **Operation ID:** `get_attention_item_api_v1_attention__item_id__get`

## Description

Fetch a single attention item (inbox or live) by its prefixed ID. Optionally marks it read/dismissed.

## Authentication

Bearer token in `Authorization` header.
Required header: `x-business-id: <business uuid>`.

## Parameters

- `item_id` (path, string, required)
- `auto_mark_read` (query, boolean, optional)
- `client_view` (query, boolean, optional)

## Responses

### 200 — Successful Response

Schema: `AttentionItem`

- `id` (string · required) — Opaque identifier. Format: ``inbox:<uuid>`` for persistent messages or ``live:<alert_id>`` for computed signals.
- `source` (AttentionSource · required) → `AttentionSource`
- `category` (AttentionCategory · required) → `AttentionCategory`
- `priority` (AttentionPriority · required) → `AttentionPriority`
- `title` (string · required)
- `body` (string) — Optional longer description of the item.
- `icon` (string) — Icon hint for the frontend (CSS icon name).
- `action_required` (boolean) — Whether resolving this item requires user action. Items with ``action_required=True`` appear in the Action Items dashboard card; all items appear in the notification bell.
- `action_url` (string) — In-app deep link the user should follow to resolve.
- `action_label` (string) — Short label for the action button (e.g. 'Review').
- `entity_type` (string) — Related entity kind, e.g. ``invoices``, ``bills``.
- `entity_id` (string) — Related entity ID if applicable.
- `created_at` (string · date-time · required)
- `read` (boolean) — True if the item is read (inbox) or has been dismissed by the user (live).
- `starred` (boolean) — Inbox-only star state.
- `dismissible` (boolean) — Whether the user can mark this read/dismiss. Always true for inbox; live items are dismissible per-user via user.props.
- `metadata` (object) — Optional source-specific extra data.

### 401 — Unauthorized - Authentication required

### 404 — Not Found - Resource does not exist

### 422 — Validation Error

Schema: `HTTPValidationError`

- `detail` (array · ValidationError) → `ValidationError`
  - `loc` (array · string | integer · required)
  - `msg` (string · required)
  - `type` (string · required)
  - `input` (object)
  - `ctx` (object)

## Code samples

### cURL

```bash
curl -X GET 'https://api.ondayzero.com/api/v1/attention/{item_id}' \
  -H 'Authorization: Bearer dz_your_token' \
  -H 'x-business-id: YOUR_BUSINESS_ID'
```

### JavaScript

```javascript
const response = await fetch('https://api.ondayzero.com/api/v1/attention/{item_id}', {
  method: 'GET',
  headers: {
    Authorization: 'Bearer dz_your_token',
    'x-business-id': 'YOUR_BUSINESS_ID',
  },
});
const data = await response.json();
```

### Python

```python
import httpx

headers = {
    "Authorization": "Bearer dz_your_token",
    "x-business-id": "YOUR_BUSINESS_ID",
}

response = httpx.get("https://api.ondayzero.com/api/v1/attention/{item_id}", headers=headers)
data = response.json()
```

## See also

- HTML version: https://www.ondayzero.com/docs/reference/attention/get-attention-item
- OpenAPI slice: https://www.ondayzero.com/docs/reference/attention/get-attention-item/openapi.json
- Other endpoints in **attention**: https://www.ondayzero.com/docs/reference/attention