Contractors

contractorOps.terms.read

Have the agreement reader agent read a signed agreement already on file for a contractor (envelopeId) and propose its terms as a draft to confirm: role, rate, pay schedule, hour limits, dates, notice, where the work is done and notable clauses, each with the words it came from. Nothing takes effect until a person confirms it.

POST/api/v1/accounting/contractorOps.terms.read

Permissions

accounting:readaccounting:write

Who can call it

admin, finance

Retries

Idempotency key required

MCP

accounting_contractor_ops_terms_read

Fields

  • contractorIdstring (ID)Required

    The ID of a contractor, from contractors.list.

  • envelopeIdstring (ID)Required

    The ID of a document sent for signature, from signing.envelopes.list.

  • 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/contractorOps.terms.read \
  -H "Authorization: Bearer $OATMILK_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "contractorId": "4d5e6f7a-8b9c-4d0e-8f1a-2b3c4d5e6f7a",
  "envelopeId": "9a8b7c6d-5e4f-4a3b-8c2d-1e0f9a8b7c6d"
}'
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/contractorOps.terms.read
curl https://app.getoatmilk.com/api/v1/accounting/contractorOps.terms.read \
  -H "Authorization: Bearer $OATMILK_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "contractorId": "4d5e6f7a-8b9c-4d0e-8f1a-2b3c4d5e6f7a",
  "envelopeId": "9a8b7c6d-5e4f-4a3b-8c2d-1e0f9a8b7c6d"
}'

More in Contractors.