Glossary
What is a unified API?
A unified API is a single API that normalises many similar third-party systems, such as dozens of HRIS platforms, into one common data model.
A unified API is one API that sits in front of many systems in the same category, for example HRIS, ATS, CRM or accounting, and maps them to a common data model. A SaaS product integrates once with the unified API and gains basic coverage of all supported systems. Examples include Merge, Finch and Apideck.
How does it work?
- The provider maintains connectors to each underlying system.
- It translates each system’s objects into a common model, for example a standard “Employee”.
- Your product reads and writes through one API and one authentication flow.
- The provider handles API changes in the underlying systems.
Unified APIs work best when your product needs the same few objects from many platforms. When one large customer needs deep, platform-specific behaviour, a native integration usually follows.
Where it shows up in integrations
- HRIS coverage A product needs basic employee data from many HR systems without building each connector.
- Early-stage integrations A startup covers the long tail of platforms before demand justifies native connectors.
- Read-heavy use cases Directory sync and reporting work well with a common model.
Common pitfalls
- The common model is a lowest common denominator: custom fields and platform-specific objects are often missing or harder to reach.
- Write-back support varies by platform and object.
- Data passes through a third party, which affects security reviews and data residency.
- Sync frequency and latency are set by the provider, not by you.