Administration

accountant.changes.request

Accountants with corrections access only: ask the company to attach an existing receipt to a bank record (attach_receipt with entryId and receiptEntryId), match a receipt to a same-currency bank payment (settle_match with entryId and transactionId), or check which contractor a payment belongs to (contractor_attribution with contractorId and transactionId), with a reason and idempotency key. Nothing changes until a company administrator approves it; payouts, agreements and settings are never offered.

POST/api/v1/accounting/accountant.changes.request

Permissions

accounting:readaccounting:write

Who can call it

Retries

Idempotency key required

MCP

Not offered over MCP: Accountants' corrections grant isn't offered over MCP yet: phase 1 is read and comment only.

Fields

Shape 1: kind: "attach_receipt"

  • kind"attach_receipt"Required

    Which kind of record or job this is.

  • entryIdstring (ID)Required

    The ID of an accounting entry, from entries.list or attention.mine.

  • receiptEntryIdstring (ID)Required

    The ID of the related record.

  • reasonstringRequired

    A short note saying why, kept in the record's history.

    10–1000 characters

  • idempotencyKeystringRequired

    Any 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

Shape 2: kind: "settle_match"

  • kind"settle_match"Required

    Which kind of record or job this is.

  • entryIdstring (ID)Required

    The ID of an accounting entry, from entries.list or attention.mine.

  • transactionIdstring (ID)Required

    The ID of a bank or card transaction, from transactions.list.

  • reasonstringRequired

    A short note saying why, kept in the record's history.

    10–1000 characters

  • idempotencyKeystringRequired

    Any 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

Shape 3: kind: "contractor_attribution"

  • kind"contractor_attribution"Required

    Which kind of record or job this is.

  • contractorIdstringRequired

    The ID of a contractor, from contractors.list.

    1–200 characters

  • transactionIdstring (ID)Required

    The ID of a bank or card transaction, from transactions.list.

  • reasonstringRequired

    A short note saying why, kept in the record's history.

    10–1000 characters

  • idempotencyKeystringRequired

    Any 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

Example

curl https://app.getoatmilk.com/api/v1/accounting/accountant.changes.request \
  -H "Authorization: Bearer $OATMILK_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "kind": "attach_receipt",
  "entryId": "7f0f6c1e-1c1f-4b5e-9c8d-2f5e8e3c1a10",
  "receiptEntryId": "7f0f6c1e-1c1f-4b5e-9c8d-2f5e8e3c1a10",
  "reason": "Synthetic example from the docs"
}'
Response
{
  "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.

POST/api/v1/accounting/accountant.changes.request
curl https://app.getoatmilk.com/api/v1/accounting/accountant.changes.request \
  -H "Authorization: Bearer $OATMILK_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "kind": "attach_receipt",
  "entryId": "7f0f6c1e-1c1f-4b5e-9c8d-2f5e8e3c1a10",
  "receiptEntryId": "7f0f6c1e-1c1f-4b5e-9c8d-2f5e8e3c1a10",
  "reason": "Synthetic example from the docs"
}'

More in Administration.