compliance.items.update
Update a compliance item's status (upcoming, in_progress, done or skipped), notes, owner (assigneeUserId of an active administrator or finance member) or snoozedUntil date. Requires id, expectedRevision and idempotencyKey. Automatic refreshes never overwrite these human decisions.
/api/v1/accounting/compliance.items.updatePermissions
Who can call it
Retries
MCP
accounting_compliance_items_updateFields
idstring (ID)RequiredThe record's ID.
expectedRevisionintegerRequiredThe record's current revision, from the last time you read it. If someone changed the record since, the request is refused with a conflict so you can reload and check before trying again.
at most 9007199254740991 · greater than 0
idempotencyKeystringRequiredAny unique text you generate once per intended change, so a retried request only happens once. Send it as the Idempotency-Key header instead if you prefer; if you send both they must match.
8–200 characters
statusenumOnly include records with this status.
upcomingin_progressdoneskippednotesstringNotes kept with the record.
at most 4000 characters
assigneeUserIdstring or nullsnoozedUntilstring or nullnotifyOnResumeboolean
Example
curl https://app.getoatmilk.com/api/v1/accounting/compliance.items.update \
-H "Authorization: Bearer $OATMILK_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: $(uuidgen)" \
-d '{
"id": "9a8b7c6d-5e4f-4a3b-8c2d-1e0f9a8b7c6d",
"expectedRevision": 3,
"status": "upcoming"
}'{
"data": { … }
}Try it
Try it
Checks your input with this action’s real schema and answers like the API, with synthetic data. No key needed, and nothing changes.
curl https://app.getoatmilk.com/api/v1/accounting/compliance.items.update \
-H "Authorization: Bearer $OATMILK_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: $(uuidgen)" \
-d '{
"id": "9a8b7c6d-5e4f-4a3b-8c2d-1e0f9a8b7c6d",
"expectedRevision": 3,
"status": "upcoming"
}'More in Compliance.