Retire an approval threshold
Take a threshold out of use. Flagged inactive rather than deleted, so "what control was in force in March" stays answerable.
Take a threshold out of use.
Flagged inactive rather than deleted, so "what control was in force in March" stays answerable.
Authorization
OAuth2PasswordBearer In: header
Path Parameters
uuidCookie Parameters
Response Body
application/json
application/json
curl -X DELETE "https://example.com/api/b/v1/approval-policies/497f6eca-6276-4993-bfeb-53cbbbba6f08"{ "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "subject_type": "payout", "min_amount_minor": 0, "currency": "string", "required_approvals": 0, "levels": [ { "position": 0, "role": "finance", "required_approvals": 0 } ], "is_active": true}Add an approval threshold POST
Add a threshold. It applies to movements raised after this call. Anything already waiting keeps the rule it was raised under - an approver who has already agreed should not find their approval silently no longer counted.
Movements awaiting a signature GET
Everything waiting on a decision, newest first. Defaults to `pending` because that is the working queue; the decided ones are an archive somebody goes looking for, and defaulting to all of them would bury today's three payouts under last quarter's four hundred.