Inbox and uploads

mail.review.answer

Answer the one question Oatmilk's review asked about an email, with id, reviewId, choiceId (a, b or c) and idempotencyKey. The choice's effect comes from the stored question: leave the draft, fix it, fix it and add it to the books through the same checks as mail.approve, or archive the email. Choices that change date, currency, total or tax only update the draft; a separate full draft review is required before booking.

POST/api/v1/accounting/mail.review.answer

Permissions

mail:readmail:writeaccounting:readaccounting:write

Who can call it

admin, finance

Retries

Idempotency key required

MCP

accounting_mail_review_answer

Fields

  • idstring (ID)Required

    The record's ID.

  • reviewIdstring (ID)Required

    The ID of the related record.

  • choiceIdenumRequired
    abc
  • 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–160 characters

Example

curl https://app.getoatmilk.com/api/v1/accounting/mail.review.answer \
  -H "Authorization: Bearer $OATMILK_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "id": "9a8b7c6d-5e4f-4a3b-8c2d-1e0f9a8b7c6d",
  "reviewId": "9a8b7c6d-5e4f-4a3b-8c2d-1e0f9a8b7c6d",
  "choiceId": "a"
}'
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/mail.review.answer
curl https://app.getoatmilk.com/api/v1/accounting/mail.review.answer \
  -H "Authorization: Bearer $OATMILK_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "id": "9a8b7c6d-5e4f-4a3b-8c2d-1e0f9a8b7c6d",
  "reviewId": "9a8b7c6d-5e4f-4a3b-8c2d-1e0f9a8b7c6d",
  "choiceId": "a"
}'

More in Inbox and uploads.