Overview

API Overview

Build on the Toku platform with our REST API. Manage grants, wallets, employees, invoices, and more.

This is the v1 (legacy) token API. The current Toku API is documented in the API reference.

Introduction#

The Toku API lets you programmatically manage token grants, wallets, employees and invoices. Available operations depend on the API endpoint, your organization’s enabled products and your role. Use the endpoint reference to confirm what an integration can do.

What the API covers#

With an API token you can call the operations in this reference: token grants, wallets and wallet verification, employee seats, tokens and networks, organization wallet settings and invoice payments. Every operation the API accepts has a page here.

Payroll, EOR and HRIS people, payslips, webhooks, stablecoin payroll, custody and token distributions aren't available through this API. You manage them in the Toku app, and the product guides explain how.

Contractor and Agent of Record integrations#

The Toku API covers contractors in full: invoices, approval, contractor setup, payments and wallets, listed under Contractor › API.

For contractor invoice integrations, the existing API supports:

Invoice submission creates invoice records. It does not approve, fund or release a bank transfer. Recording an invoice as paid updates its accounting status and does not verify that funds reached the contractor.

Creating a contractor role does not itself execute an Agent of Record agreement or confirm that identity checks, tax details, banking and country-specific compliance are complete. Confirm the applicable AOR onboarding and payment workflow with Toku before integrating.

A demo account lets you explore seeded platform data. Production API access is arranged separately with Toku.

Base URL#

All API requests are made to:

https://app.toku.com/api/tokuApi/v1/{operationName}

Request Format#

  • GET requests pass parameters as query strings
  • POST / PUT / DELETE requests send JSON in the request body
  • All responses return JSON
# GET request example
curl "https://app.toku.com/api/tokuApi/v1/getEmployeeGrants?externalEmployeeID=EMP-001" \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "x-role-type: CLIENT_ORG_ADMIN"

# POST request example
curl -X POST https://app.toku.com/api/tokuApi/v1/terminateGrant \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "x-role-type: CLIENT_ORG_ADMIN" \
  -H "Content-Type: application/json" \
  -d '{"grantID": "550e8400-e29b-41d4-a716-446655440000", "terminationDate": "2026-06-30T00:00:00.000Z"}'

A successful call returns 200 with the result in data:

{
  "data": { "grantID": "550e8400-e29b-41d4-a716-446655440000" },
  "error": null
}

A failed call returns an error instead. See Errors.

Required Headers#

Every authenticated request must include:

HeaderDescription
AuthorizationBearer YOUR_API_TOKEN — your personal API token
x-role-typeThe role to act as. Use CLIENT_ORG_ADMIN for most operations, including the contractor operations above.
Content-Typeapplication/json (for POST/PUT/DELETE requests)

API Domains#

Rate Limits#

By default each token's seat can make 300 requests a minute and each IP address 600 requests a minute. Over the limit you get 429 Too Many Requests with a Retry-After header. See Errors & Rate Limits.

Versioning#

The current API version is v1. All endpoints are prefixed with /api/tokuApi/v1/.

Was this page helpful? Suggest edits