Skip to navigation
API ReferenceApproval Policies

Validate policy approvers

Beta

Validates that the proposed approver set can satisfy the minimum approval threshold across all locations in the policy scope. Call before create/update to surface missing-approver warnings. One scope field is required.

Authentication

AuthorizationBearer
OAuth2 authentication flows. Auth server URLs will vary by environment

Headers

X-Api-KeystringRequired
API key for authentication
X-API-VersionstringOptional

API version to use (optional, defaults to latest). Supported values: 1.0.0, 1.1.0.

Idempotency-KeystringOptionalformat: "^[A-Za-z0-9._\-+=/]{1,128}$"<=128 characters

Client-generated unique key (UUID/ULID recommended). JSON requests: the first 2xx response is cached for 24h and replayed on a same-key retry with a matching body; a different body returns 422. Non-JSON requests (e.g. file uploads): the key is single-use — any same-key retry returns 422 regardless of body. See Idempotency for full details.

Request

Validation payload
minimum_approversintegerOptional

Required approver count (default 1)

use_buyer_approverbooleanOptional

Treat buyer as implicit approver (default false)

ottimate_location_idintegerOptional
Validate for a single location
ottimate_company_idintegerOptional
Validate for all locations in company
groupstringOptional
Validate for all locations in group
accountstringOptional
Validate for all locations in account
userslist of integersOptional
User IDs to validate
roleslist of stringsOptional
Role IDs to validate

Response

Validation ran; valid reports whether the proposed approver set covers every location in scope. Always 200 — a validation result, even a negative one, is not an error condition.

Errors

400
Bad Request Error
401
Unauthorized Error
403
Forbidden Error
422
Unprocessable Entity Error