> 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.

# Quickstart

> Step-by-step guide to make your first Merge API call. Covers API key setup, test Linked Account creation, and a sample GET request.

---

## Prerequisites

* A Merge account. If you do not have one, [sign up](https://app.merge.dev/signup). Signing up is free, and the [pricing page](https://www.merge.dev/pricing/unified) has the plans.
* Your **API key** from [app.merge.dev/keys](https://app.merge.dev/keys).

---

#### Dashboard – Create a test Linked Account

A test Linked Account lets you simulate an end user's connection to a third-party platform without affecting production data.

1. Go to [Test Linked Accounts](https://app.merge.dev/linked-accounts/test-accounts) in your Merge Dashboard.
2. Press **Create test Linked Account**.
3. Select an integration (for example, **BambooHR** under HRIS).

#### Need a third-party account?

To test with real data, create a free account with one of the platforms below. Once you have an account, select that platform when creating your test Linked Account.

| Category           | Platform                                                                |
| ------------------ | ----------------------------------------------------------------------- |
| **HRIS**           | [BambooHR](https://www.bamboohr.com/signup/h2)                          |
| **ATS**            | [Teamtailor](https://www.teamtailor.com/en-us/)                         |
| **Accounting**     | [QuickBooks](https://quickbooks.intuit.com/)                            |
| **Ticketing**      | [Jira](https://www.atlassian.com/software/jira)                         |
| **CRM**            | [HubSpot](https://www.hubspot.com/)                                     |
| **File Storage**   | [Google Drive](https://workspace.google.com/intl/en-US/products/drive/) |
| **Knowledge Base** | [Confluence](https://www.atlassian.com/software/confluence)             |

4. Follow the prompts to complete the setup.

Once created, your test Linked Account will automatically start syncing data from the third-party platform. Copy the **Account Token** shown at the bottom of the Linked Account detail page — you will need it in the next step.

#### Make your first API call

Try the interactive API tester below to see how a request to the Merge Unified API works. This uses mock data for illustrative purposes.

##### Postman

Visit our **Postman Collections** to test our Unified API

Run in Postman

##### SDKs

Use our [SDKs](/merge-unified/hris/merge-api-basics/sdks) to integrate with our Unified API even faster

Each object in `results` is a **Common Model** — a normalized shape that looks the same regardless of whether the source is BambooHR, Workday, ADP, or any other HRIS provider. Fields like `first_name`, `work_email`, and `employment_status` are standardized across all integrations.

> **Note**
>
> If the response contains an empty `results` array, your test Linked Account may still be syncing. Wait a minute and try again, or check the sync status in your [Dashboard](https://app.merge.dev/linked-accounts/test-accounts).

---

## You just completed the entire loop

Here is what happened:

1. You created a test **Linked Account** in the Dashboard (in production, your end users create these through **Merge Link**).
2. You called the **Unified API** with your API key and the account token.
3. Merge returned **Common Model** data from the test integration.

That is the core of every Merge integration. The only difference in production is that Merge Link, not the Dashboard, creates Linked Accounts for your real end users.

---

Next: Set up Merge Link

Or skip ahead to the [Architecture reference](/merge-unified/architecture-reference) to understand how everything fits together.