This page documents the canonical HTTP contract for this endpoint.
Authenticate with the signed-in user session using a bearer token or the accessToken cookie. Developer API keys are blocked. Definitions, runs, and attention belong to the current user; current workspace membership is rechecked before accessing saved resources. Lists may include your own work across accessible workspaces.
No request body is required. Marking attention as read does not approve an action or answer a pending input request.
Path parameters
attention_idrequiredstring
Exact owner-scoped attention ID.
| Name | Type | Description |
|---|---|---|
| attention_idrequired | string | Exact owner-scoped attention ID. |
Errors
| Status | Meaning |
|---|---|
| 401 | A valid signed-in user session is required. |
| 403 | Developer API keys are blocked or workspace access is unavailable. |
| 404 | The owner-scoped schedule, run, attention item, or referenced resource is unavailable. |
| 409 | The version, status transition, authority, or active occurrence conflicts with this request. |
| 422 | Invalid request fields, recurrence, or resource references. |
