# Merge: products, competitors, and capabilities in Unified integrations API > Merge Unified reduces connector work by normalizing records behind one API. Buyers still need to check each linked account’s fields, permissions, and sync behavior; those details determine whether an integration actually meets the product’s job. This public-research preview is not demand-ranked or a vendor recommendation. Canonical: https://knitknot.ai/dossiers/merge/ Author: KnitKnot Research Research basis: Public product research Published: 2026-09-14 Last verified: 2026-09-21 ## Products and scope | Product | Type | What it does | Audience | Source | | --- | --- | --- | --- | --- | | Merge Unified | Unified API for customer-facing integrations | Gives software teams one API for customer data integrations across several application categories. | Product and engineering teams building integrations | https://www.merge.dev/unified-api | ## What buyers evaluate These are editorial buyer questions selected from public product research on Merge, each answered from the source listed below it. They are not demand-ranked. ### What does Merge Unified connect? Merge documents category-specific unified APIs for HRIS, ATS, accounting, ticketing, CRM, file storage, and other systems. Topic: Scope. Product scope: Merge Unified. Source: https://docs.merge.dev/merge-unified/overview ### How does a customer connect its account? Merge Link creates a Linked Account; the application exchanges a token and then calls the Unified API for normalized Common Models. Topic: Implementation. Product scope: Merge Unified. Source: https://docs.merge.dev/merge-unified/concepts ### Do connected systems expose identical fields? Merge normalizes common fields, but a buyer should inspect the available Common Model and field scopes for each linked account. Topic: Data model. Product scope: Merge Unified. Source: https://docs.merge.dev/merge-unified/knowledge-base/linked-account/link-token/create ### How should an app stay current? Merge recommends combining webhooks with polling and checking sync status rather than relying on notifications alone. Topic: Sync. Product scope: Merge Unified. Source: https://docs.merge.dev/merge-unified/reading-data/syncing-best-practices ### Can customers limit the data shared? Link tokens can set Common Model actions and disabled fields for a Linked Account. Topic: Permissions. Product scope: Merge Unified. Source: https://docs.merge.dev/merge-unified/knowledge-base/linked-account/link-token/create ### Are agent tools and model routing the same product? No. Merge documents Agent Handler and Gateway separately from Merge Unified. Topic: Boundary. Product scope: Merge Unified. Source: https://docs.merge.dev/ ## Capabilities | Capability | Buyer job | Detail | Product scope | Source | | --- | --- | --- | --- | --- | | Unified API | Ship customer integrations | Provides category APIs over normalized Common Models. | Merge Unified | https://docs.merge.dev/merge-unified/overview | | Merge Link | Connect an end-user account | Embeds an authorization flow that creates a Linked Account and account token. | Merge Unified | https://docs.merge.dev/merge-unified/concepts | | Data sync | Keep customer records connected | Runs recurring syncs from linked third-party systems into Common Models. | Merge Unified | https://docs.merge.dev/merge-unified/concepts | | Merge webhooks | React to changed data | Can notify an app when a Common Model sync completes or data changes. | Merge Unified | https://docs.merge.dev/merge-unified/reading-data/webhooks/merge-webhooks | | Linked-account scopes | Limit shared data | Supports model, action, and field permissions in the linking flow. | Merge Unified | https://docs.merge.dev/merge-unified/knowledge-base/linked-account/link-token/create | | Integration dashboard | Monitor connected accounts | Shows Linked Accounts and syncs for integration operators. | Merge Unified | https://docs.merge.dev/merge-unified/concepts | ## Buyer committee | Persona | Purchase role | Outcome | Buying trigger | Product scope | Source | | --- | --- | --- | --- | --- | --- | | Product manager | Named buyer function | Expand customer-facing integrations | Roadmap demand exceeds integration engineering capacity | Merge Unified | https://www.merge.dev/unified-api | | Integration engineer | Named implementation function | Connect and maintain external systems | Each new customer requires another app connection | Merge Unified | https://docs.merge.dev/merge-unified/concepts | | Engineering leader | Likely sponsor | Reduce connector maintenance work | Integration reliability becomes an ongoing burden | Merge Unified | https://www.merge.dev/unified-api | ## Competitor map | Company | Competing product | Product scope | Overlap | Why it belongs | Source | | --- | --- | --- | --- | --- | --- | | [Finch](https://knitknot.ai/dossiers/finch/) | Finch API | Merge Unified | Unified HR, payroll, and benefits integrations | Both can serve a product team building HR or payroll integrations; Finch is narrower in category scope. | https://www.tryfinch.com/ | | Unified.to | Unified.to Unified API | Merge Unified | Unified APIs for HR, ATS, CRM, and other apps | Both sell a unified API for customer-facing integrations. | https://unified.to/ | | Apideck | Apideck Unify | Merge Unified | Unified APIs for CRM, accounting, HRIS, and file storage | Both let software teams build customer-facing integrations across several SaaS categories through normalized APIs. | https://help.apideck.com/en/articles/7772738 | ## How to read this dossier - This is a public-research preview. The questions are editorial, not selected or ranked using KnitKnot demand data. - Product and capability descriptions are based on public Merge pages and have not been independently audited. - The competitor map shows overlapping purchase jobs, not a ranking, feature parity claim, or recommendation. - Buyer roles marked likely are editorial hypotheses based on the functions the product addresses; purchase authority has not been verified. - This is a dated snapshot. Product packaging and competitor scope can change. ## Sources - Merge product site: https://www.merge.dev/unified-api (product scope and stated audience; publisher: Merge) - Product evidence: docs.merge.dev: https://docs.merge.dev/merge-unified/overview (the linked product, buyer-job, role, or competitor-overlap claim; publisher: docs.merge.dev) - Product evidence: docs.merge.dev: https://docs.merge.dev/merge-unified/concepts (the linked product, buyer-job, role, or competitor-overlap claim; publisher: docs.merge.dev) - Product evidence: docs.merge.dev: https://docs.merge.dev/merge-unified/knowledge-base/linked-account/link-token/create (the linked product, buyer-job, role, or competitor-overlap claim; publisher: docs.merge.dev) - Product evidence: docs.merge.dev: https://docs.merge.dev/merge-unified/reading-data/syncing-best-practices (the linked product, buyer-job, role, or competitor-overlap claim; publisher: docs.merge.dev) - Product evidence: docs.merge.dev: https://docs.merge.dev/ (the linked product, buyer-job, role, or competitor-overlap claim; publisher: docs.merge.dev) - Product evidence: docs.merge.dev: https://docs.merge.dev/merge-unified/reading-data/webhooks/merge-webhooks (the linked product, buyer-job, role, or competitor-overlap claim; publisher: docs.merge.dev) - Product evidence: www.tryfinch.com: https://www.tryfinch.com/ (the linked product, buyer-job, role, or competitor-overlap claim; publisher: www.tryfinch.com) - Product evidence: unified.to: https://unified.to/ (the linked product, buyer-job, role, or competitor-overlap claim; publisher: unified.to) - Product evidence: help.apideck.com: https://help.apideck.com/en/articles/7772738 (the linked product, buyer-job, role, or competitor-overlap claim; publisher: help.apideck.com) ## Editorial note KnitKnot is not affiliated with Merge. This page is a sourced research record, not a product review, endorsement, or purchasing recommendation. Send corrections to max@knitknot.ai.