Merge Docs

Appearance

Merge DocsBuild once. Connect to every API, tool, and LLM.

SOP reference for Merge: the Unified API, Agent Handler, and Gateway. Ship products and agents to production without owning the integration stack.

Get Started
Unified API
Ask the Docs
🔌

Unified API

One normalized API to read and write structured data across HRIS, ATS, CRM, Accounting, Ticketing, File Storage, and Knowledge Base.

🤖

Agent Handler

Give AI agents secure, governed access to hundreds of third-party tools over MCP, with per-user auth, scoping, and an audit log.

🧭

Gateway

Route LLM requests across providers for cost, performance, and reliability, with routing policies and cost governance.

🚀

Quickstart

Make your first Merge API call in under 10 minutes, from API key to a normalized response.

🧩

API Categories

Every category, the platforms it unifies, the Common Models it exposes, and its OpenAPI spec id.

💡

Use Cases

Forty-plus build-ready patterns across HR, recruiting, sales, finance, and AI training.

📐

Workflows

End-to-end flow diagrams for auth, syncing, writes, agent tool calls, and Gateway routing.

📋

SOPs

Step-by-step procedures distilled from the docs, from first call to setting up Agent Handler.

⚡

Quick Reference

Fast lookups for endpoints, models, connectors, rate limits, and troubleshooting.

What is Merge? ​

Merge is a single integration platform with three products. The Unified API reads and writes data across integrations through one normalized interface. Agent Handler gives AI agents secure access to third-party tools over MCP. Gateway routes LLM requests across providers.

This is an internal SOP reference site. Content is summarized from the public Merge documentation and organized for fast lookup, with an AI chat assistant grounded in these pages. Use the Ask the Docs button in the corner to ask anything.

Core concepts at a glance ​

  • Linked Account: an end user's connection to a third-party platform, created through Merge Link.
  • Account token: identifies which Linked Account a request reads or writes (X-Account-Token).
  • Common Model: Merge's normalized schema for an object (Employee, Candidate, Contact, Invoice, Ticket, File).
  • /meta: discover the exact fields a write needs for a given integration before you POST.
  • modified_after: pull only changed records for cheap, near real-time syncing.

Unofficial documentation reference. Built for internal use.

Content summarized from the public Merge documentation.