Contractors

contractorOps.encryption.status

Read how contractor tax numbers and payment details are encrypted here: whether the encryption key and the previous key are set and usable (never their values), how many values the scheduled run still has to encrypt or re-encrypt, how many can't be read with the keys set now, recorded failures by error code, when a value was last tried, whether the previous key is safe to remove (only once nothing in any organization uses it), whether the organization's fingerprint key can be read (fingerprintKey) and can be reset (canResetFingerprintKey), and warnings. Counts only.

GETPOST/api/v1/accounting/contractorOps.encryption.status

Permissions

accounting:read

Who can call it

admin

Retries

Safe to retry: it only reads

MCP

accounting_contractor_ops_encryption_status

Fields

No input fields. Send an empty object, {}.

Example

curl https://app.getoatmilk.com/api/v1/accounting/contractorOps.encryption.status \
  -H "Authorization: Bearer $OATMILK_API_KEY"
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/contractorOps.encryption.status
curl https://app.getoatmilk.com/api/v1/accounting/contractorOps.encryption.status \
  -H "Authorization: Bearer $OATMILK_API_KEY"

More in Contractors.