Expenses
Upsert Expense Approval Tier
Creates or updates an org approval tier with amount range, approver role and contributor type.
POSThttps://api.toku.com/hris/upsert-expense-approval-tier
Not available to API keys yet. It will need expenses:write.
curl --request POST \
--url 'https://api.toku.com/hris/upsert-expense-approval-tier' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
"tierID": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"tierOrder": 0,
"minAmount": "string",
"maxAmount": "string",
"approverRole": "TOKU_ADMIN",
"contributorType": "EMPLOYEE"
}'200 response
{
"tierID": "3fa85f64-5717-4562-b3fc-2c963f66afa6"
}Authorizations
AuthorizationstringheaderrequiredBearer authentication header of the form Bearer <token>, where <token> is an access token from a Toku sign-in. See Authentication in the API reference.
Body
application/json
tierIDstring<uuid>tierOrderintegerrequiredAllowed: 1 to 20
minAmountstring | any | numberNOTE(ck): z.instanceof(Decimal) has no contract form; TGA still checks it
maxAmountstring | any | numberNOTE(ck): z.instanceof(Decimal) has no contract form; TGA still checks it
approverRolestringrequiredAvailable options: TOKU_ADMIN, CLIENT_ORG_ADMIN, CLIENT_ORG_APPROVER, FINANCE_ADMIN, USER, INVESTOR, SUB_INVESTOR, SUB_RECIPIENT
contributorTypestring | nullAvailable options: EMPLOYEE, CONTRACTOR, null
Response
200Successful response
tierIDstring<uuid>required400Bad request
401Unauthorized
403Forbidden
404Not found
409Conflict
429Response 429
Was this page helpful? Suggest edits