Welcome to the HiBob Marketplace

Connect payroll, finance, IT, and HR systems while keeping your people data aligned, secure, and scalable inside Bob.

Merge

Merge integration: Merge lets B2B software companies offer a HiBob integration to their customers without building or maintaining it themselves. The problem: a software vendor whose product needs employee data has to build a separate integration for every HRIS its customers use, then maintain each one through API changes, auth migrations, and edge cases forever. That is months of engineering time per integration, and it blocks deals when a prospect runs an HRIS the vendor does not support. With Merge, a vendor builds once to a single unified API and gets HiBob plus 70+ other HR, payroll, and directory platforms. HiBob data arrives already normalized into standard models, so the vendor's product works the same whether their customer is on Bob or anything else. Merge handles authentication, syncing, error handling, logging, and ongoing maintenance. For the joint customer, this means their vendors can support Bob quickly instead of putting it on a roadmap, and end users connect their Bob account through a one-click OAuth flow with scoped, least-privilege permissions.

Merge lets B2B software companies offer a HiBob integration to their customers without building or maintaining it themselves. The problem: a software vendor whose product needs employee data has to build a separate integration for every HRIS its customers use, then maintain each one through API changes, auth migrations, and edge cases forever. That is months of engineering time per integration, and it blocks deals when a prospect runs an HRIS the vendor does not support. With Merge, a vendor builds once to a single unified API and gets HiBob plus 70+ other HR, payroll, and directory platforms. HiBob data arrives already normalized into standard models, so the vendor's product works the same whether their customer is on Bob or anything else. Merge handles authentication, syncing, error handling, logging, and ongoing maintenance. For the joint customer, this means their vendors can support Bob quickly instead of putting it on a roadmap, and end users connect their Bob account through a one-click OAuth flow with scoped, least-privilege permissions.

Built by
Merge
Website
https://www.merge.dev/integrations/hibob?utm_source=hibob&utm_medium=marketplace&utm_campaign=hibob_marketplace_listing
Region
Global

Value statement

Merge lets B2B software companies offer a HiBob integration to their customers without building or maintaining it themselves.

The problem: a software vendor whose product needs employee data has to build a separate integration for every HRIS its customers use, then maintain each one through API changes, auth migrations, and edge cases forever. That is months of engineering time per integration, and it blocks deals when a prospect runs an HRIS the vendor does not support.

With Merge, a vendor builds once to a single unified API and gets HiBob plus 70+ other HR, payroll, and directory platforms. HiBob data arrives already normalized into standard models, so the vendor’s product works the same whether their customer is on Bob or anything else. Merge handles authentication, syncing, error handling, logging, and ongoing maintenance.

For the joint customer, this means their vendors can support Bob quickly instead of putting it on a roadmap, and end users connect their Bob account through a one-click OAuth flow with scoped, least-privilege permissions.

Functionality and how the integration works

Direction: Merge only supports one-way by default, but offers the ability to expand your integration to two way should you need it. Typically, data flows from HiBob into the partner’s product. Merge reads from Bob and by default does not write back. HRIS write support however is an option for those that need it.

How it connects: the ISV registers its own OAuth app in the HiBob Developer Portal, points the redirect URI at Merge’s OAuth callback, and enters the client ID, client secret, and app ID into Merge. Their end user then authorizes the connection through Merge Link, a drop-in one-click flow. Merge stores and refreshes the tokens.

Scopes requested:

  • employee_data:read
  • employee_data.sensitive:read
  • timeoff:read

Bob modules and APIs used:

  • People / employee data: POST /people/search for employee records, employment history, teams, groups, locations, company, and bank information. GET /people/{employee_id}/variable for payroll run and earnings data.
  • Time Off: GET /timeoff/employees/{employee_id}/balance for balances, and GET /timeoff/requests/changes for time off requests and changes.

Data made available to the partner, normalized into Merge Common Models: Employee, Employment, Company, Team, Group, Location, BankInfo, EmployeePayrollRun, TimeOff, and TimeOffBalance. Partners can also reach non-standard Bob fields through Field Mapping, Remote Data, and Authenticated Passthrough Requests.

Sync frequency is configurable from manual through hourly depending on the partner’s plan, with force-resync and webhook options for near real-time needs.

Merge also offers a HiBob MCP server through Merge Agent Handler (currently in beta) for partners building AI agents that need Bob as a tool.

Short company description and USP

Merge is a leading provider of customer-facing integrations and agent tools, used by frontier AI labs, Fortune 500 organizations, and B2B SaaS companies. Founded in 2020 and headquartered in San Francisco with offices in New York and Berlin, Merge is backed by Accel, NEA, and Addition.

The unique selling proposition is one build, hundreds of integrations. Instead of writing and maintaining a separate integration for every platform a customer uses, companies integrate once with Merge’s unified API and immediately support HiBob alongside 70+ other HR and payroll systems, and hundreds more across ATS, CRM, ticketing, accounting, and file storage. Merge owns the entire lifecycle, including authentication, normalization, syncing, monitoring, and maintenance, so partners ship in days rather than quarters and their engineers stay on core product.

SCHEDULE A DEMO

Key features

<p><strong>Key features:</strong></p> <ul> <li><strong>Merge Unified:</strong> One API for hundreds of customer-facing integrations across HRIS and payroll, ATS, CRM, ticketing, accounting, and file storage, with normalized Common Models so one build works across every provider.</li> <li><strong>Merge Link:</strong> A drop-in, white-labelable authorization component. End users connect their Bob account in a few clicks, with scoped permissions and no engineering work on their side.</li> <li><strong>Integration Observability:</strong> Fully searchable logs, automated issue detection, and configurable alerts so customer success teams resolve integration problems without engineering.</li> <li><strong>Merge Agent Handler:</strong> Secure, governed access to thousands of third-party tools for AI agents, including a HiBob MCP server.</li> <li><strong>Customization and supplemental data:</strong> Field Mapping, Remote Data, and Authenticated Passthrough Requests to reach any non-standard field or endpoint in Bob.</li> <li><strong>Enterprise-grade security:</strong> SOC 2 Type II, ISO 27001, HIPAA, and GDPR, with regional data hosting in the US, EU, and APAC.</li> </ul>