> This page is for Unified.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.merge.dev/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.merge.dev/_mcp/server.

# Merge Unified

Connect to our Unified API to start offering integrations in your product.

## Why teams choose Merge Unified

One Common Model schema covers every provider in a category, so the tenth integration costs roughly what the first one did, and a new provider ships as a configuration change rather than a code change. Across 8 categories, Merge documents 260+ integrations, and the catalog grows continuously.

* **Provider drift is absorbed.** Third-party APIs change schemas, auth, and rate limits continuously. Merge tracks those changes behind a stable interface, so application code stays put when a provider moves.
* **Per-customer credentials are handled.** Merge Link runs the OAuth or API-key flow with each end user, then Merge stores and refreshes the credential and surfaces re-auth through Issues when a provider revokes it.
* **Normalization is never a ceiling.** Passthrough requests reach the underlying provider API directly, Remote Data returns the raw third-party payload alongside the normalized record, and field mapping brings custom fields into the Common Model.
* **Writes are discoverable at runtime.** The `/meta` endpoint returns the required fields for any POST or PATCH per integration and Linked Account, so write support can be built programmatically instead of provider by provider.
* **Enterprise compliance is already in place.** SOC 2 Type II, ISO 27001, HIPAA, GDPR, and CCPA, with encryption in transit and at rest plus an additional layer of application encryption on PII. Data residency in the US, EU, or APAC, single-tenant deployment, and the option to land synced data in your own environment.

Integration counts are as of August 2026 and grow over time; the category pages below list every currently supported provider.

Against building in-house, the work Merge takes over is the ongoing part: tracking provider changes, running and retrying syncs, storing and refreshing per-customer credentials, and answering the security review each new provider would otherwise trigger.

## Get started

* [Concepts](https://docs.merge.dev/merge-unified/concepts): Understand how the Unified API, Common Models, Merge Link, and account tokens fit together
* [Quickstart](https://docs.merge.dev/merge-unified/quickstart): Make a real API call and pull back normalized data in under 10 minutes
* [Merge Link](https://docs.merge.dev/merge-unified/merge-link): Let your end users connect their own integrations through a drop-in frontend component

## Explore by category

* [HRIS](https://docs.merge.dev/merge-unified/hris/overview): HR, payroll, and directory integrations
* [ATS](https://docs.merge.dev/merge-unified/ats/overview): Applicant tracking integrations
* [Accounting](https://docs.merge.dev/merge-unified/accounting/overview): Accounting platform integrations
* [Ticketing](https://docs.merge.dev/merge-unified/ticketing/overview): Ticketing and project management integrations
* [CRM](https://docs.merge.dev/merge-unified/crm/overview): CRM platform integrations
* [File Storage](https://docs.merge.dev/merge-unified/filestorage/overview): File storage integrations
* [Knowledge Base](https://docs.merge.dev/merge-unified/knowledge-base/overview): Knowledge base integrations
* [Chat](https://docs.merge.dev/merge-unified/chat/overview): Chat platform integrations