Demo HR (Sandbox)
Demo HR system with realistic test data for development.
Data
- Employees Supported
firstName, lastName, displayName, workEmail, personalEmail, mobilePhone, employmentStatus, startDate, terminationDate, jobTitle, managerId, teamIds, locationId, remoteCreatedAt, remoteUpdatedAt
- Teams Supported
name, type, parentId
- Locations Supported
name, type, street, city, postalCode, country
- Employments & compensation Supported
employeeId, jobTitle, employmentType, startDate, endDate, isCurrent, payRate, payCurrency, payPeriod
- Time off Supported
time_off_types.name, time_off_types.unit, time_off_types.category, time_off_requests.employeeId, time_off_requests.typeId, time_off_requests.status, time_off_requests.startDate, time_off_requests.endDate, time_off_requests.startHalfDay, time_off_requests.endHalfDay, time_off_requests.amount, time_off_requests.unit, time_off_balances.employeeId, time_off_balances.typeId, time_off_balances.balance, time_off_balances.used, time_off_balances.unit, time_off_balances.asOf
Writes
Through POST and PATCH /v1/hris/employees, with your client's
separate consent.
Create: firstName, lastName, workEmail, personalEmail, mobilePhone, jobTitle, startDate, managerId, teamIds, locationId
Update: firstName, lastName, workEmail, personalEmail, mobilePhone, jobTitle, startDate, managerId, teamIds, locationId, terminationDate
What your client needs
Your client's admin creates API credentials in their HR system; no partnership with the vendor is needed.
Sign-in method: API key
Freshness and storage
- Updates
- Scheduled sync every 6 hours
- Storage
- A normalized copy of the consented data is stored for fast reads and change detection.
- Vendor API terms reviewed
- Not yet reviewed