ADP Employee Sync - Toku Docs

Toku keeps its worker roster in sync with ADP Workforce Now 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 workers through ADP’s Workers v2 API, paginating with OData $top/$skip:

curl "https://api.adp.com/hr/v2/workers?\$top=100&\$skip=0" \
  --cert toku.crt --key toku.key \
  -H "Authorization: Bearer <access_token>"

Workforce Now returns at most 100 workers per page (default 50); Toku pages with $skip until the workers array comes back empty. Individual records are available at GET /hr/v2/workers/{aoid}, and $filter/$select are supported for narrowing results. The scope used is /hr/workerInformationManagement/workerManagement/workerProfileManagement/worker.read. A trimmed example response:

{
  "workers": [
    {
      "associateOID": "G3349PZGBADQY8H8",
      "workerID": { "idValue": "ADA001" },
      "person": {
        "legalName": { "formattedName": "Ada Lovelace" },
        "communication": {
          "emails": [{ "emailUri": "[email protected]" }]
        }
      },
      "workAssignments": [
        {
          "positionID": "ABC0010078765",
          "assignmentStatus": { "statusCode": { "codeValue": "A" } },
          "payrollGroupCode": "ABC",
          "payrollFileNumber": "078765",
          "baseRemuneration": {
            "annualRateAmount": { "amountValue": 180000, "currencyCode": "USD" }
          }
        }
      ]
    }
  ]
}

See ADP’s reference for the full schema: Workers v2 API Explorer.

What Toku Reads

Field	Purpose
`associateOID`	Stable identifier used to match the worker across systems and post deductions
`workAssignments[].positionID`	Together with the Associate ID, identifies the worker for pay data input
`person.legalName`, `emails[].emailUri`	Roster display and employee-portal invitations
`workAssignments[].assignmentStatus`	Marks departed or inactive workers inactive in Toku
`payrollGroupCode`, `payrollFileNumber`	Routes the deduction to the right payroll group and file
`baseRemuneration`	Validates election limits against compensation

Sync Behavior

New workers appear in Toku automatically after they’re added in ADP Workforce Now.
Updates (name, email, compensation, pay group) flow through on the next sync.
Inactive workers 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 ADP. Toku does not modify worker records, work assignments, or compensation.

Payroll Sync

How Toku tracks pay cycles and payroll output

The Toku Deduction

How the deduction is applied via the Pay Data Input API

​Endpoint

​What Toku Reads

​Sync Behavior

​Next

Payroll Sync

The Toku Deduction

Endpoint

What Toku Reads

Sync Behavior

Next