Transactions

reconciliation.createEntry

Create an entry from an imported bank transaction with an explicit type and optional category. Reuses existing entries on retry.

POST/api/v1/accounting/reconciliation.createEntry

Permissions

accounting:readaccounting:write

Who can call it

admin, finance

Retries

Idempotency key required

MCP

accounting_create_bank_record

Fields

  • transactionIdstring (ID)Required

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

  • categoryIdstring (ID)

    The ID of a category, from categories.list.

  • typeenum
    expenseincomeincome_refundrefundtransferfee
  • 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/reconciliation.createEntry \
  -H "Authorization: Bearer $OATMILK_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "transactionId": "7f0f6c1e-1c1f-4b5e-9c8d-2f5e8e3c1a10"
}'
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/reconciliation.createEntry
curl https://app.getoatmilk.com/api/v1/accounting/reconciliation.createEntry \
  -H "Authorization: Bearer $OATMILK_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "transactionId": "7f0f6c1e-1c1f-4b5e-9c8d-2f5e8e3c1a10"
}'

More in Transactions.