Overview
Employer of Record (EOR) lets your platform offer employment services in jurisdictions where you lack a legal entity. Toku acts as the legal employer: handling compliance, payroll, and local labor law obligations while you manage the employment relationship through the API.EOR operations require your API token to be scoped to a user with the
PAYROLL_ADMIN or CLIENT_ORG_ADMIN role. Pass the appropriate role in the x-role-type header on every request.Role Mapping
Employee Onboarding Flow
When you add a new EOR employee, Toku creates a structured onboarding checklist. The employee completes the required steps (personal details, bank account, tax forms, etc.) through your platform’s co-branded onboarding UI. Once all steps are done, Toku activates the employment relationship.1
Create person record
Call The response includes
POST /createHrisPerson with employmentType: EMPLOYEE and employmentServiceType: EOR. Supply the employee’s name, email, country, start date, title, and compensation.roleInOrgID — store this to reference the employee in all subsequent calls.2
Monitor onboarding progress
Poll
POST /getOnboardingProgress with the employee’s roleInOrgId to track each step. The response lists every required step with its completion status.3
Employee completes onboarding steps
Direct the employee to your platform’s co-branded onboarding UI. Toku renders white-labelled onboarding forms within your product so employees stay in your experience. Steps typically include personal information, address, bank account, and tax declarations.
4
Employee activated
When all required steps are complete, the employee’s status transitions to
ACTIVE. Query POST /getHrisPerson to confirm the current status before processing payroll.Listing and Looking Up People
Get all people
GET /getHrisPeople returns your organisation’s full people directory — EOR employees, contractors, and any other person records. Use this for building org charts, dashboards, or payroll runs.
Each record includes id, fullName, email, type, status, title, and department.
Get a single person
POST /getHrisPerson takes a roleInOrgID and returns the full person object including employment details and current status.
Profile Management
Basic field updates
POST /updateHrisPerson applies lightweight updates such as name corrections, title changes, manager reassignments, or phone number updates. Changes take effect immediately and do not create a change request.
Updatable fields: givenName, familyName, title, department, phoneNumber, managerEmail.
Profile-level updates
PUT /updateHrisEmployeeProfile handles changes that may affect employment terms (e.g., compensation, role changes). These updates trigger a change request workflow inside Toku for compliance review. The response includes a changeRequestId that you can use to track approval status.
Onboarding Overview
GET /getOnboardingOverview returns aggregate onboarding status across all employees — useful for building an admin dashboard that surfaces who is pending, in-progress, or fully onboarded.
Co-Branded Experience
Toku’s onboarding UI renders within your platform via an embedded flow. Employees see your branding throughout the onboarding process. No redirect to a Toku-hosted domain is required.Contact Toku to configure your brand assets (logo, colors, domain) for the co-branded onboarding experience.
Next Steps
Create HRIS Person
Create an EOR employee or contractor record
Get Onboarding Progress
Track step-by-step onboarding completion
Get HRIS People
List all people in your organisation
Update HRIS Employee Profile
Submit profile changes for compliance review