Every API request includes an x-role-type header that determines what the caller can do. Your API token must belong to a user with the specified role in the organization.There are three permission levels in the Toku API:
Level
Base Class
Who Can Call
Count
Any authenticated user
AuthorisedOperation
Any user with a valid token + org membership
36 endpoints (61%)
Admin only
AdminOperation
CLIENT_ORG_ADMIN or equivalent admin role
28 endpoints (38%)
Client Admin only
TokuClientAdminOperation
CLIENT_ORG_ADMIN specifically
4 endpoints
For 3rd party integrations, use CLIENT_ORG_ADMIN. It has access to all 68 public endpoints. Other roles have more limited scope.
Requires a valid API token and membership in the organization. Any role works — CLIENT_ORG_ADMIN, PAYROLL_ADMIN, FINANCE_ADMIN, INVESTOR, or RECIPIENT.
Requires CLIENT_ORG_ADMIN or another admin-level role (PAYROLL_ADMIN for some operations). The exact admin roles accepted vary by endpoint, but CLIENT_ORG_ADMIN always works.
For a complete 3rd party integration that manages grants, wallets, and employees, create your API token with CLIENT_ORG_ADMIN. This is the only role guaranteed to work with all 68 public endpoints.
Assistant
Responses are generated using AI and may contain mistakes.