For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Logo
Resources
Log inGet a demo
Get startedAPI referenceImplementation
Get startedAPI referenceImplementation
  • Merge Link
    • Overview
    • Embedded Link
    • Magic Link
    • Single integration
  • Reading data
    • Syncing best practices
  • Supplemental data
    • Overview
    • Remote Data
    • Custom objects
  • Writing data
    • Overview
  • Platform and account metadata
    • Integration metadata
    • Linked Accounts
  • Testing
    • Testing Merge's Unified API via Postman
  • Specifications
    • Schema properties
    • Model Context Protocol (MCP)

Get started

  • Overview
  • Introduction
  • Unified API
  • Linked Account
  • Merge Link
  • Use cases

Implementation

  • Sandboxes
  • SDKs
  • API access
  • Syncing data
  • Writing data
  • Data minimization
  • Supplemental data
  • Errors
  • Integration metadata

API reference

  • ATS
  • HRIS
  • Accounting
  • Ticketing
  • CRM
  • File Storage
  • Knowledge Base
  • Chat

Resources

  • Help Center
  • Merge.dev
  • Changelog
© Merge 2026Terms of usePrivacy policy
UnifiedAgent HandlerGateway
UnifiedAgent HandlerGateway
Resources
Log inGet a demo
On this page
  • Delivery methods
  • Customization
  • How each method works
Merge Link

Merge Link options

Merge Link is the UI component your end users interact with to connect their integrations. Here are the ways you can deliver it.

Delivery methods

Embedded Merge Link

Drop-in UI component for React, Vue, or vanilla JS. Your end user picks an integration and authorizes access without leaving your app. Recommended for most integrations.

Magic Link

Send your end user a secure URL to authorize integrations — no frontend code required. Ideal when you cannot embed a component or need to onboard users via email.


Customization

Single Integration

Pass a parameter to limit Merge Link to a specific provider instead of showing the full integration picker. Useful when your product only supports one integration or you want to control which platform the user connects.


How each method works

Embedded Merge Link uses a three-step token exchange: your backend creates a link_token, your frontend opens Merge Link with that token, and when the end user finishes, you receive a public_token that your backend swaps for a permanent account_token. For a full walkthrough with code in five backend languages and three frontend frameworks, see the Embedded Merge Link guide.

Magic Link does not use the public_token / account_token swap. Instead, your backend creates a link_token with should_create_magic_link_url=true, receives a magic_link_url in the response, and sends that URL to the end user. After the user authorizes, you retrieve the account token from the Dashboard or via a webhook. See the Magic Link guide for details.

Was this page helpful?
Next

Merge Link