Workday
Integrate every HR & Payroll system with one API
Ship new integrations in days, not months. Read and write data to all major HR systems with our Unified API.
Trusted by the world's leading B2B companies
Why leading HR Tech players choose Kombo
One standardized model
Read and write data across any HRIS using the same set of endpoints. Whether it's Workday, SAP SuccessFactors, or UKG Pro, you work with the same data model.
Seamless authentication
Embed our white-labeled connection guide into your product to easily let your customers connect their systems.
Access any data
Map custom fields from any system to your own unified schema. Use remote data to access raw data when you need to access niche fields.
Full visibility
Track sync status, spot authentication issues, and debug problems from the dashboard. Get webhook notifications when things change or need attention.
One data model for every integration
Build to Kombo once and connect to any HRIS. Reading employees, employments, and absences and writing back time off requests, documents, and employee updates works the same whether you're connected to Paycor, Oracle HCM, Personio, or BambooHR - same endpoints, same fields, same format.
Same granularity as a direct integration
Our unified API covers most use cases, but every system has its quirks. Use custom fields to map tool-specific data to your schema. Access raw data from the source with remote data. Call the underlying API directly with passthrough for edge cases. All in real-time if needed.
Monitor all your integrations from one place
See sync status, authentication issues, and errors across every customer connection in the dashboard. Searchable logs show you exactly what happened with each API request. Set up webhooks to get notified when errors occur or credentials need attention, so your support team can resolve issues without always having to pull in engineering.
Featured Case Study
How EGYM WELLPASS increases customer adoption with Kombo’s HRIS integrations
Continue Reading
Especially for enterprise companies with thousands of employees and different sub-companies, it makes sales discussions way easier.
Dmytro Naida
Sr. Product Manager, EGYM WELLPASS
Data model library
Employees (HRIS)
The Employee object represents a person in the HRIS. It includes personal information, employment status, job title, work location, legal entity, and manager relationships. Use it to sync workforce data or create new employees using the form endpoints.
Learn more →
Employments (HRIS)
The Employment object represents the contractual details of an employee's position, including job title, pay rate, pay period, employment type, and effective date. Employees can have multiple employments to track changes over time.
Learn more →
Groups (HRIS)
The Group object represents organizational units like teams, departments, or cost centers. Employees can belong to multiple groups.
Learn more →
Work Locations (HRIS)
The WorkLocation object represents a physical or remote location where employees work. It includes the location name, address, and type (such as office or remote).
Learn more →
Legal Entities (HRIS)
The LegalEntity object represents a registered company or subsidiary that employs workers. It's typically used for payroll, compliance, and organizational structuring.
Learn more →
Absences (HRIS)
The Absence object represents a period of time off taken by an employee. Use it to read, create, or delete absences such as vacation, sick leave, or other leave types.
Learn more →
Absence Types (HRIS)
The AbsenceType object defines the categories of time off available in the organization, such as vacation or sick leave. It includes information on whether half-days and exact times are supported.
Learn more →
Time Off Balances (HRIS)
The TimeOffBalance object tracks an employee's remaining and used time off for a specific absence type.
Learn more →
Timesheets (HRIS)
The Timesheet object represents a time and attendance record for an employee, including clock-in/out times, breaks, payable hours, and approval status.
Learn more →
Documents (HRIS)
Use the Documents endpoint to upload files to an employee's record, such as employment contracts, identification documents, or certifications.
Learn more →
Employee Document Categories (HRIS)
The EmployeeDocumentCategory object defines the types of documents that can be uploaded to employee records, such as contracts or certifications.
Learn more →
Performance Reviews (HRIS)
The PerformanceReview object represents an evaluation of an employee's performance within a review cycle. It includes ratings, comments, and the relationship between reviewee and reviewer.
Learn more →
Performance Review Cycles (HRIS)
The PerformanceReviewCycle object represents a time-bound period during which performance reviews are conducted, such as an annual or quarterly review cycle.
Learn more →
Skills (HRIS)
The Skill object represents a competency or capability that can be assigned to employees and job positions. Use it to create, update, or delete skills and manage employee skill assignments.
Learn more →
Job positions (HRIS)
The JobPosition object represents a role within the organizational structure. It includes required skills, department, location, and reporting relationships.
Learn more →
Discover our HRIS integrations
Build and maintain all HRIS integrations with one data model. Employees, groups, performance, and timesheets all follow the same format - no need to transform data or map fields differently for each system.
Designed for enterprise data protection needs
Customer trust and data security are critical to us. Kombo provides comprehensive security controls and compliance frameworks specifically built for the regulatory requirements and data sensitivity of HR and TA tech integrations.
Reliability at scale
We power integrations for hundreds of companies, from seed-stage startups to Fortune 500 enterprises - all while maintaining 99.9% uptime. Our infrastructure is built to handle your growth without compromising performance.
Onboarding support
We work closely with your team via shared Slack or Teams channels. Your customers get detailed connection guides and transparent documentation on tool-specific limitations - so nothing catches them off guard.
Configurable data scoping
Collect only what you need. Define exactly which fields, information, or data points flow through each integration. Mark fields as required, optional, or disabled based on compliance requirements and use case needs.
