Documents and signing

documents.records.get

Read one record's details as labelled values to put into a document, such as a contractor's or customer's legal name, email, phone and address, a merchant's website, a teammate's name and role, or the company's legal name, address and business number. Pass type and id from documents.records.search (id is "company" for the company).

GETPOST/api/v1/accounting/documents.records.get

Permissions

accounting:read

Who can call it

admin, finance

Retries

Safe to retry: it only reads

MCP

accounting_documents_records_get

Fields

  • typeenumRequired
    contractorpartymerchantmembercompany
  • idstringRequired

    The record's ID.

    1–200 characters

Example

curl -G https://app.getoatmilk.com/api/v1/accounting/documents.records.get \
  -H "Authorization: Bearer $OATMILK_API_KEY" \
  --data-urlencode 'type=contractor' \
  --data-urlencode 'id=example'
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.

GET/api/v1/accounting/documents.records.get
curl -G https://app.getoatmilk.com/api/v1/accounting/documents.records.get \
  -H "Authorization: Bearer $OATMILK_API_KEY" \
  --data-urlencode 'type=contractor' \
  --data-urlencode 'id=example'

More in Documents and signing.