Merge unified API profile
Multi-category unified APIs for HRIS, ATS, accounting, ticketing, CRM, file storage, knowledge base, and chat systems.
Research note: This neutral profile summarizes first-party material published by Merge. It was last checked . Capabilities can differ by connector, so verify the exact model, field, action, and refresh behavior required by your product.
Merge at a glance
- Focus
- A sync-first, multi-category platform built around category-specific Common Models and a managed linking experience.
- Good fit for
- B2B products that need a consistent connection, synchronization, and API operating model across several major SaaS categories.
- Categories
- HRIS, ATS, Accounting, Ticketing, CRM, File Storage, Knowledge Base, Chat
- Data delivery
- Recurring synchronization into Merge Common Models, with sync-status endpoints, webhooks, and incremental retrieval patterns.
- Extension path
- Remote data, authenticated passthrough, remote field classes, field mappings, and custom data supplement Common Models.
What is Merge?
Merge is a multi-category unified API platform. Each software category has shared Common Models and endpoints so a product can connect to multiple providers without maintaining a separate API contract for each one.
- The documented Unified API categories are HRIS, ATS, accounting, ticketing, CRM, file storage, knowledge base, and chat.
- Common Models standardize category-specific objects, such as employees in HRIS or candidates and jobs in ATS.
- Merge also documents write operations, data scopes, selective synchronization, supplemental data, and connector-specific metadata.
How does Merge Link work?
Merge Link is an embedded connection component. A backend creates a short-lived link token, the frontend receives a public token after authorization, and the backend exchanges it for a durable account token representing the Linked Account.
- Server requests include the Merge API key in the Authorization header and the end-user account token in X-Account-Token.
- The account token selects the user and integration whose data the request may access.
- The Merge Dashboard manages API keys, Linked Accounts, sync status, webhooks, and test connections.
How does Merge synchronize data?
Merge connects to third-party systems on a recurring schedule and normalizes their data into Common Models. Merge recommends combining synchronization webhooks, incremental pulls, periodic polling, and the sync-status endpoint.
- Linked Account and Common Model webhook events can notify an application about linking, sync completion, changed data, deleted data, and account issues.
- The synchronization guide recommends periodic reconciliation because webhook delivery or processing can fail.
- Products should model partial, failed, and in-progress sync states rather than treating a successful Link flow as complete data readiness.
How does Merge handle data outside Common Models?
Merge groups several extension mechanisms under Supplemental Data. These include original remote data, authenticated passthrough requests, remote field classes, field mappings, and custom data.
- Remote data returns the provider payload Merge received alongside the normalized model.
- Field mappings can add or override Common Model fields without requiring application-side transformation code.
- Passthrough requests use stored Linked Account credentials to call provider-native endpoints when the normalized surface is insufficient.
What developer capabilities are documented?
Merge provides quickstarts, category SDKs, test Linked Accounts, sandboxes, a dashboard, webhook tooling, API logs, integration metadata, and programmatic write metadata.
- The /meta pattern returns account-specific requirements for supported Common Model writes.
- Scopes and selective synchronization can limit which models, fields, or records are synchronized for a use case.
- The quickstart offers test providers across major categories so teams can exercise the complete linking and API loop before production.
What should buyers verify?
- Common Model presence does not guarantee identical field, relationship, filter, or write support for every connector.
- Because the default model is sync-first, applications should design explicitly for sync status, freshness, partial results, and reconciliation.
- Supplemental paths reduce abstraction gaps but reintroduce provider-specific behavior that the application must own and test.
For a cross-vendor evaluation framework, read the verified unified API buyer’s guide.
Frequently asked questions about Merge
Which categories does Merge support?
Merge documents Unified APIs for HRIS, ATS, accounting, ticketing, CRM, file storage, knowledge base, and chat.
Does Merge call the downstream API on every request?
Merge’s documented default is a recurring synchronization model: it normalizes connected data into Common Models that applications retrieve through the Unified API.
What is a Merge Common Model?
A Common Model is a standardized category-specific object that maps equivalent provider fields into one response shape.
Can Merge access fields outside its Common Models?
Yes. Merge documents remote data, authenticated passthrough, remote field classes, field mappings, and custom data as supplemental mechanisms.
Sources checked
- Merge Unified overview — documentation, checked
- How Merge works — documentation, checked
- Merge API authentication — documentation, checked
- Merge syncing best practices — documentation, checked
- Merge webhooks — documentation, checked
- Merge Supplemental Data — documentation, checked
- Merge remote fields — documentation, checked
- Merge Unified quickstart — documentation, checked
- Merge Common Models — official website, checked
- Merge Unified Writes introduction — blog, checked