contractors.recipients.bind
Confirm that a Wise recipient (profileId, recipientId) is this contractor, with a reason and the contractor's expectedContractorRevision, so transfers to it are attributed to them. A recipient can belong to one contractor.
/api/v1/accounting/contractors.recipients.bindPermissions
Who can call it
Retries
MCP
accounting_contractors_recipients_bindFields
contractorIdstring (ID)RequiredThe ID of a contractor, from contractors.list.
profileIdstringRequiredMatches ^\d{1,30}$
recipientIdstringRequiredThe ID of one signer on a document.
Matches ^\d{1,30}$
expectedContractorRevisionintegerRequiredThe related record's current revision, from the last time you read it.
at most 9007199254740991 · greater than 0
reasonstringRequiredA short note saying why, kept in the record's history.
10–1000 characters
idempotencyKeystringRequiredAny 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–150 characters
Example
curl https://app.getoatmilk.com/api/v1/accounting/contractors.recipients.bind \
-H "Authorization: Bearer $OATMILK_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: $(uuidgen)" \
-d '{
"contractorId": "4d5e6f7a-8b9c-4d0e-8f1a-2b3c4d5e6f7a",
"profileId": "1250",
"recipientId": "1250",
"expectedContractorRevision": 3,
"reason": "Synthetic example from the docs"
}'{
"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.
curl https://app.getoatmilk.com/api/v1/accounting/contractors.recipients.bind \
-H "Authorization: Bearer $OATMILK_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: $(uuidgen)" \
-d '{
"contractorId": "4d5e6f7a-8b9c-4d0e-8f1a-2b3c4d5e6f7a",
"profileId": "1250",
"recipientId": "1250",
"expectedContractorRevision": 3,
"reason": "Synthetic example from the docs"
}'More in Contractors.