Fresh 2026

Merge Link options

Comparison of Merge Link delivery methods, embedded component (React/Vue/JS), Magic Link (no frontend code), and single-integration mode.

---

Delivery methods

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.

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

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.