Assign Needs-Attention Entries
PUT/api/ledger/entries/needs-attention/assignments
Give Needs Attention entries an owner and a due date, in bulk. The owner gets the entries in their daily Sync Problems Assigned to You email and under Mine in the inbox.
accounting:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Authentication: Requires Bearer token. Scope: accounting (write). The user must hold the Sync permission (accounting.sync).
Body fields:
entry_ids(array of integers, required, 1–1000, distinct) — the journal entries to update. Any id that does not exist fails the whole request with 422 onentry_ids; nothing is changed.assignee_user_id(integer or null, optional) — the owner. Must be an active user of this account, else 422.nullremoves the owner. Leave the key out to keep each entry's current owner.due_on(dateYYYY-MM-DDor null, optional) — the due date.nullremoves it. Leave the key out to keep each entry's current due date.
Sending only due_on sets a due date without changing anyone's owner. An owner stays on an entry after it syncs, so it is back on the same person's list if it fails again.
Response: data.updated — how many entries were written, with a message such as 2 entries updated.
Request
Responses
- 200
- 401
- 403
- 422
- 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.
Unprocessable Content
Response Headers
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.