Get started

Toku API reference

The Toku API: every action in Toku's employment, contractor, stablecoin payroll, token grant and HR products, as an HTTP endpoint.

The Toku API is the API the Toku app itself runs on. Each operation is one action in Toku, such as listing your people, submitting an invoice or approving a payroll run, and it behaves exactly as the same action does in the app: the same checks, the same permissions and the same results.

This reference is generated from the API's contracts every time this site is published, so each page shows the operation's current request and response.

This is the current API. The earlier token API at app.toku.com/api/tokuApi/v1 is still documented as API v1 (legacy).

Base URL#

https://api.toku.com

Paths have no version prefix. For example, listing the people in your organization is:

curl https://api.toku.com/hris/get-hris-people \
  -H "Authorization: Bearer toku_sk_..."

How the reference is organized#

Each product's tab lists its own operations, under API, grouped by area:

  • Employment: payslips and compensation, payroll run approvals, employment records, benefits, tax profiles and terminations.
  • Contractor: self-serve contractor payments, invoices and invoice payments, payment batches and payout wallets.
  • Stablecoin Payroll: stablecoin and token payroll, payments and settlement, custody and payroll integrations.
  • Token Grants Administration: grants, vesting, distributions, investors, wallets and custody providers.
  • Toku HR: people, onboarding, documents, time off, time tracking, expenses, reports and your account.

This tab lists the rest under More operations: accounting, cards and prop trading, notifications, token and network settings, and shared tools.

Each page lists the operation's parameters, request body and responses, with cURL, JavaScript and Python examples.

Requests and responses#

  • Requests and responses are JSON. Send Content-Type: application/json with a request body.
  • GET operations take their inputs as query parameters, and POST operations take a JSON body.
  • Every call acts in one organization. An API key carries its organization. With a sign-in, name it with the x-toku-org-id header when you have seats in more than one.

Status codes#

Each operation's page lists the statuses it can answer. The common ones:

StatusMeaning
200The operation succeeded.
400The request did not match the operation's parameters or body.
401No credential, or one the API does not accept. See Authentication.
403The caller's seat, or the API key's permissions, may not do this in this organization.
404The record does not exist, or the caller cannot see it.
409The record's current state does not allow the change.
429Too many requests. Wait and retry.

Next steps#

Was this page helpful? Suggest edits