Transactions

reimbursements.approve

Approve up to 100 submitted reimbursement claims in one atomic review, recording receipt validity and whether the claimant was an employee or officer at purchase for GST/HST treatment.

POST/api/v1/accounting/reimbursements.approve

Permissions

accounting:readaccounting:write

Who can call it

admin, finance

Retries

Idempotency key required

MCP

accounting_reimbursements_approve

Fields

  • claimsarray of objectsRequired

    1–100 items

  • reasonstringRequired

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

    3–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/reimbursements.approve \
  -H "Authorization: Bearer $OATMILK_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "claims": [
    {
      "id": "9a8b7c6d-5e4f-4a3b-8c2d-1e0f9a8b7c6d",
      "expectedRevision": 3,
      "receiptValid": true,
      "employeeAtPurchase": true
    }
  ],
  "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/reimbursements.approve
curl https://app.getoatmilk.com/api/v1/accounting/reimbursements.approve \
  -H "Authorization: Bearer $OATMILK_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "claims": [
    {
      "id": "9a8b7c6d-5e4f-4a3b-8c2d-1e0f9a8b7c6d",
      "expectedRevision": 3,
      "receiptValid": true,
      "employeeAtPurchase": true
    }
  ],
  "reason": "Synthetic example from the docs"
}'

More in Transactions.