List Needs-Attention Groups
GET/api/ledger/entries/needs-attention
The needs-attention inbox feed: non-discarded entries whose display status needs a human (needs_attention, failed, conflict, removed_in_provider — capped at the latest 1000), grouped server-side by error cause so the UI can offer fix-once-retry-all.
Any valid API token can call this endpoint — no specific scope required. Manage tokens.
Authentication: Requires Bearer token.
Grouping: each group keys on the latest sync operation's error_class plus a normalized cause message (numeric IDs masked to # so per-record noise collapses into one cause, truncated to 160 chars). Entries with no operation error group under status:<display_status>. Groups are sorted by count descending.
Response shape (per group):
cause_key— stable grouping key (error_class[:md5-of-message] or status:<display_status>)label— human-readable cause (normalized message, headline-cased error class, or display-status label)error_class— retryable_transient | auth_connection | auto_remediable | user_action_required | terminal_internal | conflict, or nullcount— total entries in the groupentry_ids— up to 25 sample entry IDslatest_error_payload— the raw error payload of the group's latest operation, or null
Request
Responses
- 200
- 401
- 403
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.