> ## Documentation Index
> Fetch the complete documentation index at: https://docs.toku.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Deel People Sync

> How Toku syncs your worker roster from Deel

Toku keeps its worker roster in sync with Deel 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 Deel's organization-wide people resource (scopes `people:read` and `worker:read`):

```bash theme={null}
curl "https://api.letsdeel.com/rest/v2/people" \
  -H "Authorization: Bearer <access_token>" \
  -H "x-client-id: <toku_client_id>"
```

A trimmed example response:

```json theme={null}
{
  "data": [
    {
      "id": "9779767c-6044-48e0-bf68-aeb370b9a2e7",
      "full_name": "Ada Lovelace",
      "emails": [
        { "type": "work", "value": "ada@yourcompany.com" }
      ],
      "employments": [
        {
          "contract_id": "37nex2x",
          "state": "active",
          "hiring_type": "employee"
        }
      ]
    }
  ]
}
```

See Deel's reference for the full schema: [People](https://developer.deel.com/docs/people).

## What Toku Reads

| Field                       | Purpose                                                      |
| --------------------------- | ------------------------------------------------------------ |
| `id`                        | Stable identifier used to match the worker across systems    |
| `full_name`, `emails`       | Roster display and worker-portal invitations                 |
| `employments[].contract_id` | Ties each worker to the contract used for the Toku deduction |
| `employments[].state`       | Marks departed workers inactive in Toku                      |

<Note>
  In Deel, contracts are the central object for every engagement — each worker's active contract is what Toku targets when applying [the Toku deduction](/integrations/deel/deduction).
</Note>

## Sync Behavior

* **New workers** appear in Toku automatically once their Deel contract is active.
* **Updates** (name, email, contract changes) flow through on the next sync.
* **Departed workers** are marked inactive and stop receiving stablecoin payments.
* A manual sync can be triggered anytime from **Settings → Payroll Integrations** in Toku.

<Note>
  People sync never writes to Deel. Toku does not modify worker records, contracts, or onboarding state.
</Note>

## Next

<CardGroup cols={2}>
  <Card title="Payroll Sync" icon="calendar" href="/integrations/deel/payroll-sync">
    How Toku tracks payroll cycles and payslips
  </Card>

  <Card title="The Toku Deduction" icon="money-bill-transfer" href="/integrations/deel/deduction">
    How the deduction is applied via the Deel API
  </Card>
</CardGroup>