Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

Merge HRIS (BYOK) — connector documentation

  • MCP endpoint: https://byok-merge-hris.connectorbay.com/mcp
  • REST API: POST https://byok-merge-hris.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-merge-hris.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Merge HRIS Merge production access key, sent in the X-Upstream-Key header and the linked account token (X-Account-Token) of the customer HR account to read in X-Upstream-Key-2 of every request (never stored, logged or cached)
  • Health: https://byok-merge-hris.connectorbay.com/health · Tool schemas: https://byok-merge-hris.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-merge-hris · agent@connectorbay.com

What Merge HRIS (BYOK) is for

Merge HRIS (BYOK) lets an AI assistant read your own Merge HRIS data through the Merge HRIS API with a key you supply (Merge production access key). Read-only: 11 tools (get_account_details, list_employees, get_employee, list_employments, list_groups, list_work_locations, list_companies, list_time_off, list_time_off_balances, list_timesheet_entries, list_sync_status). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.merge.dev, api-eu.merge.dev, api-ap.merge.dev. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Merge HRIS. Merge HRIS and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which HR system is linked to this Merge account token and is it healthy?"
  • "Which employees are active in our HR system?"
  • "Show Merge employee e1"
  • "What job titles do our employees hold?"
  • "What teams and departments exist in our HR system?"
  • "Which offices does our company have?"

What it does

  • get_account_details: Show the linked HR account this token reads: integration name, category, status and when linking completed.
  • list_employees: List employees from the linked HR system with employee number, name, work email, company, team, manager, work location, employment status and hire, start and termination dates. Sensitive fields (SSN, birth date, gender, home address, personal contact) are never requested.
  • get_employee: Get one employee by Merge id with employee number, name, work email, company, team, manager, work location, status and dates (no sensitive personal fields).
  • list_employments: List employment records (job title, employment type, effective date) per employee. Pay rate and pay period are not returned.
  • list_groups: List groups (teams, departments, cost centers) with name, type, parent group and whether it is used as a team.
  • list_work_locations: List company work locations (office addresses and phone) from the HR system. Home addresses are never requested.
  • list_companies: List the legal entities (companies) in the HR system with legal and display names.
  • list_time_off: List time off requests with employee, approver, status, type, unit, amount and start and end time. Free-text employee notes are not returned.
  • list_time_off_balances: List time off balances per employee and policy type: remaining and used hours.
  • list_timesheet_entries: List logged work time per employee: hours worked and start and end time.
  • list_sync_status: Show per model (employees, time off ...) when Merge last synced the linked HR system, the result and the next sync.

BYOK key

You bring your own Merge HRIS Merge production access key (https://docs.merge.dev/get-started/authentication). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.merge.dev, api-eu.merge.dev, api-ap.merge.dev over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Merge HRIS API (api.merge.dev, api-eu.merge.dev, api-ap.merge.dev) with a BYOK key; documentation: https://docs.merge.dev/merge-unified/hris/overview. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Merge HRIS. Merge HRIS and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Merge HRIS account.

Built for: Worldwide. Languages: English.