Post: 7 APIs Every HRIS-L&D Integration Needs to Call
Seven API categories form the foundation of every working HRIS-L&D integration. Skip any one and the integration fails on a known edge case within the first 90 days.
The minimum-viable API surface
Most integration failures trace to a missing API call in one of these seven categories. The HRIS + L&D API Integration — Complete 2026 Guide covers the architecture context for these endpoints.
- Employee read/list API (HRIS). Reads employee records by employee ID, by email, by active status. The foundation of identity sync.
- Employee event webhook (HRIS). Pushes change events — new hire, role change, manager change, termination — to the integration layer within seconds of the change in HRIS.
- Learner upsert API (L&D). Creates or updates a learner record on the L&D side, keyed on employee ID. The receiver of identity sync.
- Enrollment API (L&D). Enrolls a learner in a course or path. Bulk enrollment endpoint is the operational variant.
- Completion event webhook (L&D). Pushes completion events — course completed, assessment passed, credential earned — to the integration layer for write-back to HRIS.
- Learning history write API (HRIS). Writes a completion record to an employee’s learning history on the HRIS side. The receiver of completion write-back.
- Audit query API (both sides). Reads counts and details of records on each side for the daily reconciliation job. The diagnostic backbone of the integration.
What to ask vendors before signing
Before signing either HRIS or L&D contract, confirm in writing that all seven endpoints exist with the rate limits and authentication patterns required. Endpoints that exist with severe rate limits (under 10 requests per minute, for example) are operationally equivalent to endpoints that do not exist for any organization above 500 employees. The Make.com HR analytics scenario guide details the Make.com scenarios that consume these endpoints.
Expert Take — the audit endpoint is the unsung hero
Engineering teams focus on endpoints 1 through 6 and treat endpoint 7 (audit query) as nice-to-have. That is backwards. The audit endpoints are what let the integration prove correctness to compliance reviewers and what lets the operations team troubleshoot in production. An integration without audit endpoints is an integration that runs blind once it ships.
FAQ
What rate limits make an endpoint operationally unusable?
For organizations above 1,000 employees, rate limits below 60 requests per minute on the read endpoints and below 30 requests per minute on the write endpoints produce sustained backlog under daily reconciliation load. Below 10 requests per minute, the integration cannot function at routine scale.
Are webhook payloads enough or are polled reads also required?
Webhook payloads handle real-time changes but cannot replace polled reads for reconciliation. The integration needs both — webhooks for low-latency state changes, polled reads for nightly drift detection.
Do all HRIS vendors expose all seven endpoints?
No. The market split as of 2026 is roughly 70 percent of major HRIS vendors expose all seven, 20 percent expose four to six, and 10 percent expose three or fewer. Confirm before contract signature. See the 10 integration patterns guide for what to do when endpoints are missing.
RELATED POST
