Capabilities
Lifecycle
Endpoints
List employees
Page, filter, sort, and restrict employee collections.
Create an employee
Validate placement and create an account.
Get an employee
Retrieve one employee by opaque ID.
Update an employee
Patch supported fields, division assignment, and blocking state.
Key rules
- Store the JobHandy employee ID after match or create.
- Use a stable customer identifier such as
employeeNumberwhere uniqueness is guaranteed. - Do not use email as the only long-term key unless the customer guarantees immutability.
- Omit patch fields that should remain unchanged.
- Use
nullonly for nullable fields that should be cleared. - Do not use a dry-run preview ID in later requests.
Employee synchronization guide
Implement identity matching, checkpoints, dry runs, partial updates, and timeout reconciliation.
