DOCSEARCHbyAlgolia
Submit Docs

Merge

website·Indexed 40 days ago

https://docs.merge.dev/

A unified API platform that allows teams to build once and connect to every API, tool, and LLM, enabling the shipment of products and agents to production without owning the integration stack.

Tokens
1K
Snippets
3
Records
10
Agent score
69%

What's inside Merge

  1. Overview of Merge Unified API Categories

    Merge provides a Unified API that standardizes data across multiple third-party categories. Supported categories include:

    • HRIS: HR, payroll, and directory data
    • ATS: Recruiting and applicant tracking data
    • CRM: Sales and customer relationship data
    • Accounting: Invoices, payments, and financial reporting
    • Ticketing: Tickets, comments, and project management
    • File Storage: Files, folders, and drives
    • Knowledge Base: Articles and knowledge content

  2. Overview of Merge Product Suite

    Merge provides a suite of tools to handle third-party integrations, LLM routing, and AI agent tool access:

    • Unified API: Used for reading and writing structured business data (e.g., employees, candidates, contacts, invoices, tickets, files) across multiple providers using a Common Model schema.
    • Agent Handler: Provides AI agents with secure, per-user OAuth access to third-party tools via MCP, including security guardrails and audit trails.
    • Gateway: A routing layer for LLM requests across multiple providers (OpenAI, Anthropic, Google, etc.) with built-in failover, cost management, and security filters.
    • Merge for Workforce: A governed path for an organization's own employees to access these tools and models.

  3. Route and govern LLM requests with Merge Gateway

    Merge Gateway acts as a proxy for LLM requests, providing the following capabilities:

    • Routing Policies: Route requests across providers based on cost, performance, or reliability.
    • Tool Calling: Enable models to call functions within your application.
    • Cost Governance: Implement budgets, spend caps, and cost optimization strategies.

  4. Govern employee AI access with Merge for Workforce

    Merge for Workforce allows organizations to control which models, company systems, and skills employees' AI can access. Key features include:

    • Identity & Access: Connect SCIM and map Groups to specific tool and model access.
    • Security: Scan tool call payloads for sensitive data to flag or block matches.
    • Model Management: Control which models are reachable and how requests are routed.
    • Insights: Access nightly regenerated reports on organizational AI usage.

  5. Provide AI agents secure tool access via Agent Handler

    Agent Handler allows AI agents to securely access third-party tools using the Model Context Protocol (MCP). It manages registered users, connectors, tools, and tool packs to facilitate secure tool calls.

  6. Discover required fields for POST requests via /meta

    Because required fields vary by the specific integration and the Linked Account, you must call the /meta endpoint before making POST requests to determine which fields are mandatory for that specific context.

  7. Implement data syncing and pagination in Merge Unified API

    When working with the Unified API, use the following patterns for efficient data retrieval:

    • Incremental Syncing: Use the modified_after query parameter to fetch only records changed since a specific time, avoiding full re-fetches.
    • Pagination: Merge uses cursor-based pagination. To retrieve the next page of results, follow the next cursor provided in the API response.

  8. Authenticate requests to Merge APIs

    All requests to Merge APIs require two specific headers for authentication: a Bearer token for the API key and an account-specific token.
    Authorization: Bearer <API_KEY>
X-Account-Token: <ACCOUNT_TOKEN>

  9. Access Merge OpenAPI Specifications

    Merge provides OpenAPI specs for all its products and categories. All APIs are indexed at https://docs.merge.dev/openapi.json.
    HRIS: https://docs.merge.dev/openapi/hris.json
ATS: https://docs.merge.dev/openapi/ats.json
CRM: https://docs.merge.dev/openapi/crm.json
Accounting: https://docs.merge.dev/openapi/accounting.json
Ticketing: https://docs.merge.dev/openapi/ticketing.json
File Storage: https://docs.merge.dev/openapi/file-storage.json
Knowledge Base: https://docs.merge.dev/openapi/knowledge-base.json
Chat: https://docs.merge.dev/openapi/chat.json
Agent Handler: https://docs.merge.dev/openapi/agent-handler.json
Gateway: https://docs.merge.dev/openapi/api-overview.json
Gateway Embedded Routing: https://docs.merge.dev/openapi/embedded-routing-stack.json
Gateway Management API: https://docs.merge.dev/openapi/management-api.json

  10. Set up a Merge Gateway account via CLI

    If you need to create a Gateway account without the user present, you can use the merge-gateway CLI to initiate the signup process and generate a claim link for the user.
    pipx install merge-gateway
mgw agent signup