Kombo
AI NativeLeading global unified API for HR, ATS, LMS and Payroll integrations
Leading global unified API for HR, ATS, LMS and Payroll integrations
Published Oct 11, 2026
Kombo documentation includes a deprecation notice for a previous API variant (AI Apply: Unified API), indicating those endpoints are no longer actively supported and recommending migration to the standard AI Apply API. This demonstrates that API variants may be sunsetted and migration paths should be confirmed.
Kombo changelog indicates ongoing product development and maturity, including the stated General Availability of the LMS API on March 1, 2026.
Kombo’s site presents uptime and adoption claims. Verify uptime numbers against a public status page history and contractual SLA terms; obtain historical incident reports and SLA credits language where relevant.
Where competitors may have advantages: pricing transparency and broader category coverage are areas where alternatives may be preferable depending on buyer requirements.
Traditional B2B review sites (G2, TrustRadius, Gartner Peer Insights) did not return clear product listings in searches performed. This reduces available independent review evidence and is common for developer-focused infrastructure products.
Search results for "Kombo reviews" can include irrelevant matches (other companies named Kombo); exercise caution when assessing third-party listings.
Kombo’s website includes vendor-published testimonials that emphasize speed of implementation and responsiveness of support. Examples provided on the vendor site include short-form statements attributed to customers. These are useful for understanding how the vendor positions its value, but they are vendor-sourced and were not independently verified in the review.
Independent negative reviews were not identified on standard review platforms. The most concrete criticisms originated from competitor-authored content and low-signal automated scoring sites. Examples include competitor content asserting limited observability (e.g., limited API log retention) and limited custom field support. Treat competitor-authored critiques as potential indicators to validate during a proof of concept (PoC) rather than as independent confirmation.
Commonly stated reasons for selecting Kombo include:
Potential reasons customers might leave, based on competitor critiques and common unified-API pitfalls:
Kombo references customer case studies including TestGorilla (assessment integrations), Apploi (employee creation across HRIS), and CV-Library (candidate application impact). These case studies are vendor-published and should be validated by requesting underlying metrics, methodologies, and samples where possible.
A stated vendor metric reports an average engineering time-savings claim for integrations. Treat headline metrics as vendor-published until the methodology, sample size, and inclusion criteria are documented.
Request during diligence:
Good fits tend to be:
Get a comprehensive analysis of Kombo including market position, competitive landscape, adoption trends, and peer benchmarks.
Download full report →Organizations that require integrations primarily outside workforce systems (e.g., CRM, accounting, support desk, marketing automation) should evaluate broader unified API providers or iPaaS vendors.
Organizations that require extensive public third-party proof (large volumes of G2/TrustRadius/Gartner reviews, detailed public incident histories, or widely published SLAs) before procurement should note that Kombo has limited accessible third-party reviews.
Organizations that require rigorous observability and audit features (long log retention, detailed activity trails, enterprise SIEM integration) should verify these capabilities in a PoC and contractual terms prior to purchase.
Organizations with constrained budgets and a large number of low-usage customers should validate pricing models and total cost impact during procurement, as per-connection or usage-based pricing can be costly for long-tail usage patterns.
Organizations that require full control over integration schemas as core product IP may prefer a self-built approach or platforms designed to enable custom connector frameworks.
(Note: this section summarizes vendor-documented differentiators in neutral language.)
Where competitors may have advantages: pricing transparency and broader category coverage are areas where alternatives may be preferable depending on buyer requirements.
Kombo is a B2B unified API platform focused on the workforce software ecosystem. It allows software companies to integrate once with Kombo and then expose multiple vendor integrations to their customers across:
Kombo’s primary capability is to abstract and normalize disparate vendor schemas and authentication flows into a standardized set of models and endpoints, and to provide operational tooling (dashboard, logs, scopes, coverage grid) to manage integrations.
Kombo primarily targets:
Vendor positioning emphasizes being an integration layer for people data and interoperability across workforce systems, with a stated focus on delivering comprehensive read/write capabilities for HR and talent-acquisition categories and providing enterprise-oriented security/compliance and operational support (Slack/Teams support model).