Leapsome – What data does the integration support?
Updated today
Our Leapsome integration reads employee, organization, compensation, time off, timesheet and payroll cycle data from an employer's Leapsome account and returns it through Bindbee's unified HRIS API, in the same format as every other HRIS we support. The integration is read-only.
Your customer connects their Leapsome account once with a Leapsome API secret; see Leapsome – How do I connect my account? for the steps. Production connectors sync every 24 hours by default, and you can trigger a resync whenever you need fresher data.
What we can read depends on the access role assigned to the Leapsome API key. Time off, timesheets and payroll runs each need their own Leapsome permission. Assigning the Super Admin role to the key covers all of them. If a permission is missing, only that model reports a permission issue and everything else keeps syncing.
Supported models
Employee
Employment
Compensation
Company
Group (teams, departments, business units, cost centers, divisions)
Location (work locations)
Payroll Run (Leapsome payroll cycles)
Time Off
Timesheet Entry (one entry per employee per timesheet period)
Not supported yet
Writing data back to Leapsome: the integration is read-only.
Dependents and bank info
Benefits: benefit enrollments, employer benefit plans, dependent benefits and benefit coverage
Payroll details: employee payroll runs (earnings, deductions and taxes), payroll codes and pay groups
Time off balances
If you need a Leapsome model that isn't listed here, tell us at [email protected]. To compare Leapsome with the other HRIS systems we support, see the Model Availability Matrix.