# reimbursements.claimPurchase

Create a personal expense claim for an active member from an existing unallocated receipt purchase, with its current revision, exact original evidence and explicit confirmation of who paid. Never creates or changes the expense.

`POST /api/v1/accounting/reimbursements.claimPurchase`

Permissions: `accounting:read`, `accounting:write` · Roles: admin, finance · Idempotency key required

MCP tool: `accounting_reimbursements_claim_purchase`

## Fields

| Field | Type | Required | Notes |
| --- | --- | --- | --- |
| `entryId` | string (ID) | Yes | The ID of an accounting entry, from entries.list or attention.mine. |
| `expectedEntryRevision` | integer | Yes | The related record's current revision, from the last time you read it. at most 9007199254740991; greater than 0. |
| `userId` | string | Yes | The ID of a person in your company. 1–200 characters. |
| `receiptEvidenceId` | string (ID) | Yes | The ID of the related record. |
| `personallyPaid` | true | Yes |  |
| `onBehalfConfirmed` | boolean |  |  |
| `reason` | string | Yes | A short note saying why, kept in the record's history. 10–1000 characters. |
| `idempotencyKey` | string | Yes | 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 request

```bash
curl https://app.getoatmilk.com/api/v1/accounting/reimbursements.claimPurchase \
  -H "Authorization: Bearer $OATMILK_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "entryId": "7f0f6c1e-1c1f-4b5e-9c8d-2f5e8e3c1a10",
  "expectedEntryRevision": 3,
  "userId": "example",
  "receiptEvidenceId": "1a2b3c4d-5e6f-4a7b-8c9d-0e1f2a3b4c5d",
  "personallyPaid": true,
  "reason": "Synthetic example from the docs"
}'
```

Reference page: https://app.getoatmilk.com/docs/api/reimbursements.claimPurchase
