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
  • Overview
  • Request all Merge integrations
  • Request my organization’s enabled integrations
  • Response
Platform and account metadata

Integration Metadata

Use Merge's Integration Metadata endpoint to programmatically fetch information about the integrations Merge offers.
Was this page helpful?
Previous

Writes warnings and errors reference

Next

Linked Accounts


Overview

Use the Integration Metadata endpoint to fetch integration names, identifiers, images, brand colors, and more.

You can use this data to create an integrations menu or applications marketplace for your product.

Build your own app marketplace

Request all Merge integrations

GET /api/integrations

Request my organization’s enabled integrations

GET /api/organizations/integrations

This organization-specific endpoint differs in that:

  • Only integrations enabled in Configuration are returned
  • It requires API key authentication (never store this in your frontend)
  • The response is paginated

Response

Example Integration Metadata response
1[
2 {
3 "name": "ADP Workforce Now",
4 "slug": "adp-workforce-now",
5 "image": "https://merge-api-public.s3.amazonaws.com/media/ADP_Logo.png",
6 "square_image": "https://merge-api-public.s3.amazonaws.com/media/ADP_Square_Logo_KUmu62r.jpg",
7 "color": "#D0271D",
8 "categories": [
9 "hris"
10 ]
11 },
12 {
13 "name": "ApplicantStack",
14 "slug": "applicantstack",
15 "image": "https://merge-api-public.s3.amazonaws.com/media/Applicant_Stack_Logo.png",
16 "square_image": "https://merge-api-public.s3.amazonaws.com/media/ApplicantStack_Square_Logo_wBHYVRL.jpg",
17 "color": "#67BAEA",
18 "categories": [
19 "ats"
20 ]
21 },
22 {
23 "name": "Quickbooks Online",
24 "slug": "quickbooks-online",
25 "image": "https://merge-api-public.s3.amazonaws.com/media/Quickbooks_Logo.png",
26 "square_image": "https://merge-api-public.s3.amazonaws.com/media/QuickBooks_Square_Logo.png",
27 "color": "#0FD46C",
28 "categories": [
29 "accounting"
30 ]
31 }
32]