Gusto Employee Sync

Toku keeps its employee roster in sync with Gusto so stablecoin elections always map to the right person. Sync is read-only and runs automatically after every connection and on a rolling schedule.

Endpoint

Toku reads employees through Gusto’s company-scoped employees resource:

curl "https://api.gusto.com/v1/companies/<company_id>/employees" \
  -H "Authorization: Bearer <access_token>"

A trimmed example response:

[
  {
    "uuid": "9779767c-6044-48e0-bf68-aeb370b9a2e7",
    "first_name": "Ada",
    "last_name": "Lovelace",
    "email": "[email protected]",
    "company_uuid": "1b224dcb-4386-4b3e-b81f-9e6c18e0bcd3",
    "terminated": false,
    "onboarded": true,
    "jobs": [
      {
        "title": "Senior Engineer",
        "payment_unit": "Year",
        "rate": "180000.00"
      }
    ]
  }
]

See Gusto’s reference for the full schema: Get employees of a company.

What Toku Reads

Field	Purpose
`uuid`	Stable identifier used to match the employee across systems
`first_name`, `last_name`, `email`	Roster display and employee-portal invitations
`terminated`	Marks departed employees inactive in Toku
`jobs[].rate`, `payment_unit`	Validates election limits against compensation

Sync Behavior

New employees appear in Toku automatically after they finish Gusto onboarding.
Updates (name, email, compensation) flow through on the next sync.
Terminated employees are marked inactive and stop receiving stablecoin payments.
A manual sync can be triggered anytime from Settings → Payroll Integrations in Toku.

Employee sync never writes to Gusto. Toku does not modify employee records, compensation, or onboarding state.

Payroll Sync

How Toku tracks pay periods and payroll status

The Toku Deduction

How the deduction is applied via the Gusto API

⌘I

​Endpoint

​What Toku Reads

​Sync Behavior

​Next

Payroll Sync

The Toku Deduction

Endpoint

What Toku Reads

Sync Behavior

Next