wise.paymentEvidence
Read bounded Wise 2026Q4 Activity evidence for one current invoice revision and an exact resource UUID from trusted payment evidence. Supply invoiceId, expectedRevision, targetResourceId, since and until as canonical UTC instants covering at most 31 days. The server uses the current company's configured profile and existing read connection, checking unfiltered activities, acquiring payments and payment requests. Returns only safe metadata for exact resource matches, actual observed HTTP statuses, per-check coverage and explicit limits or failures. Found means the requested resource was observed in that profile, not that it paid this invoice. invoiceAssociationVerified, financialPostingSupported and settlementVerified remain false. No invoice, bank, settings, matching or journal writes and no model calls. Ordinary API request telemetry still applies. Provider reads have a 15-second budget; required fresh context checks may finish later. Formatted provider amounts are never accounting amounts; Activity completion never verifies settlement. Access refusals, authentication challenges and unknown outcomes stop all further reads without retries or version fallback.
/api/v1/accounting/wise.paymentEvidencePermissions
Who can call it
Retries
MCP
accounting_wise_payment_evidenceReaches outside Oatmilk
Fields
invoiceIdstring (ID)RequiredThe ID of the related record.
expectedRevisioninteger or stringRequiredThe record's current revision, from the last time you read it. If someone changed the record since, the request is refused with a conflict so you can reload and check before trying again.
targetResourceIdstring (ID)RequiredThe ID of the related record.
sincestringRequiredMatches ^\d{4}-\d\d-\d\dT\d\d:\d\d:\d\d\.\d{3}Z$
untilstringRequiredMatches ^\d{4}-\d\d-\d\dT\d\d:\d\d:\d\d\.\d{3}Z$
Example
curl -G https://app.getoatmilk.com/api/v1/accounting/wise.paymentEvidence \
-H "Authorization: Bearer $OATMILK_API_KEY" \
--data-urlencode 'invoiceId=4d5e6f7a-8b9c-4d0e-8f1a-2b3c4d5e6f7a' \
--data-urlencode 'expectedRevision=3' \
--data-urlencode 'targetResourceId=1a2b3c4d-5e6f-4a7b-8c9d-0e1f2a3b4c5d' \
--data-urlencode 'since=1111-11-11T11:11:11.111Z' \
--data-urlencode 'until=1111-11-11T11:11:11.111Z'{
"data": { … }
}This action checks your data too, so replace the example values with your own before sending it.
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.
curl -G https://app.getoatmilk.com/api/v1/accounting/wise.paymentEvidence \
-H "Authorization: Bearer $OATMILK_API_KEY" \
--data-urlencode 'invoiceId=4d5e6f7a-8b9c-4d0e-8f1a-2b3c4d5e6f7a' \
--data-urlencode 'expectedRevision=3' \
--data-urlencode 'targetResourceId=1a2b3c4d-5e6f-4a7b-8c9d-0e1f2a3b4c5d' \
--data-urlencode 'since=1111-11-11T11:11:11.111Z' \
--data-urlencode 'until=1111-11-11T11:11:11.111Z'More in Connectors and webhooks.