HR platform from HiBob People & leave REST API & webhooks

Custom Bob HR integration development

Appfront builds custom integrations with Bob, the HR platform from HiBob. Using the official REST API and webhooks, we synchronise employees, leave, compensation and documents between Bob and your payroll, identity provider, planning software or in-house application. Your HR team keeps Bob as the source of truth, while data flows automatically and securely to the right systems, with no double entry.

What is a Bob HR integration?

Bob is the HR platform from vendor HiBob: an HRIS aimed at mid-market and fast-growing tech and scale-up organisations. The platform brings people management, leave, compensation, onboarding and documents together in a single system, often for international teams. In practice, the names Bob and HiBob are used interchangeably: HiBob is the company, Bob is the product.

In practice, a custom integration means: reading employee data from Bob and passing it on to payroll or an identity provider, sending leave and absence data to planning software, exposing compensation and payroll fields for finance, automating documents and onboarding steps, and using webhooks to react in real time to events such as a new employee or an approved leave request. Authentication runs via a Service User with scoped permissions.

Appfront builds in line with HiBob's official Bob API documentation and the OWASP ASVS security standard. We tailor the fields to be integrated, the synchronisation logic and the error handling to your actual HR processes, so the integration grows with your organisation and keeps running reliably, even as teams grow or expand internationally.

Bob as the source of truth

Your HR team manages employees, leave and compensation in one place in Bob. The integration ensures that connected systems pick up that data, so you never enter anything twice and personnel data is consistent everywhere.

Real-time events via webhooks

Bob sends events such as a new employee or an approved leave request straight to your systems. This means onboarding and provisioning happen automatically, without periodic manual checks or delays.

Secure with a Service User

The integration authenticates via a Service User with exactly the permissions it needs. It isn't tied to an individual, so the integration doesn't stop working when someone leaves the company, and the data flow stays limited to what is truly necessary.

Our development process for Bob HR integrations

We follow a proven approach that removes uncertainty early and delivers a stable integration. From an initial analysis of your HR processes, the Bob fields you need and the surrounding systems through to go-live and ongoing maintenance, every step is aimed at an integration your team can understand and trust.

1
Analysis & scope

We map which employee, leave, payroll and document fields you want to integrate, which systems Bob needs to talk to, and which events should come through in real time via webhooks.

2
Architecture

We design the integration architecture, set up a Service User with least-privilege permissions and define an error-handling and retry strategy.

3
Development

Implementation with automated tests, structured logging and monitoring. You see working builds along the way.

4
Go-live & maintenance

A controlled go-live with data validation and a safety net, followed by ongoing maintenance and further development.

What a Bob HR integration delivers in practice

Every Bob HR integration is configured specifically for your HR processes, the fields to be synchronised and the surrounding systems. Below are the features we deliver most often for organisations that use Bob as their central HR platform.

REST API & Service User token

The integration talks to the Bob REST API through a Service User that authenticates with basic authentication and a token. We assign permissions on a scoped basis, so each integration can only access the fields and endpoints it genuinely needs.

Employees & people sync

Synchronise employee profiles from Bob to payroll, an identity provider or your own systems, including standard and custom fields. New and changed employees flow through automatically, so the same personnel data appears everywhere.

Leave & absence

Retrieve leave requests, balances and absence from the Time off API and pass them on to planning, payroll or a shared calendar. Teams see at a glance who is away, and leave records stay in sync everywhere.

+

Payroll & compensation

Expose compensation and payroll data, such as salary history and bank details, to your payroll or finance system. Changes from Bob flow through in a controlled way, with tight permissions because the data is sensitive.

Webhooks & events

Subscribe to Bob events such as a new employee, or a leave request being submitted, approved or cancelled. Bob calls your listener with a payload, so surrounding systems respond immediately and automatically.

Documents & onboarding

Link documents and onboarding information from Bob to your DMS or accounts. As soon as a new employee appears in Bob, accounts, documents and access can be set up automatically for a smooth first day.

Typical use cases in practice

A Bob HR integration looks very different from one organisation to the next. We see a number of patterns come up often, and for each of them we have a working setup that pays attention to the right fields, permissions and real-time events.

CRM

Tech and scale-up organisations

Fast-growing tech and scale-up companies that use Bob as their HRIS and want to automate their stack. Synchronise employees with an identity provider, provision accounts on joining and deactivate them on leaving. See also our API integrations.

Mid-market organisations

Organisations with a few hundred employees that use Bob as their central HR platform and want to integrate with payroll and finance. Employee and compensation data flows to payroll in a controlled way, with a documented and auditable data flow. Take a look at our middleware.

International teams

Companies with employees in several countries who manage leave, absence and local arrangements centrally in Bob. Leave data flows to planning and payroll per region, so teams across time zones can see who is available and the records are correct everywhere.

Professional services

Consultancies, IT service providers and agencies that link personnel data from Bob to resource and project planning. Availability and leave flow into the planning, so consultants are scheduled based on up-to-date HR data from Bob.

Technology we use

We build Bob HR integrations using HiBob's official REST API and webhooks, combined with the backend stack that suits you. The exact choice depends on the systems Bob needs to talk to, so that your own team can manage or further develop the integration.

If you want to exchange vacancies and new employees between Ubeeo and your HR software, read more about our Ubeeo integration.

Bob REST API Bob webhooks Service User & token (basic auth) People & employee fields API Time off API Payroll & compensation data Documents API Node.js / Python / PHP / .NET / Ruby / Go Identity providers (SSO / SCIM) Payroll integrations Planning & resource management Middleware & message queues Secrets management & vaults Webhook signature validation Retry & dead-letter queues GitHub Actions

Why Appfront for your Bob HR integration?

Appfront has extensive experience building API integrations for a wide range of organisations in the Netherlands. We always start with a thorough analysis of your existing systems and processes, because an integration must not only be technically sound but also add practical value to the way you work.

For every integration we write clear documentation and make sure your own team, or a future supplier, can understand and manage the integration. No black box, but transparent code and clear agreements on monitoring, alerting and maintenance.

You work with a dedicated point of contact who understands both the technical and the functional side. That keeps communication lines short, prevents miscommunication and speeds up decisions when choices have to be made during the build.

Also take a look at our broader services around API integrations, middleware, custom software and web app development, or see all the integrations we build.

  • Experience with the Bob REST API and its people, time off and payroll endpoints
  • Secure by default: Service User with scoped permissions, token rotation and webhook validation
  • Familiar with integrations to payroll, identity providers and planning software
  • Clear documentation that your HR and IT teams can read and manage themselves

Security and privacy in Bob HR integrations

A Bob HR integration inherently processes personal data, and often sensitive PII such as salary, bank details and leave. Appfront builds in line with OWASP ASVS. Among other things, that means: the Service User token stored in secure vaults, webhook signature validation, scoped permissions following least privilege, and regular audits of the data flows between Bob and your systems.

Because this involves employee and PII data, we limit the data flow to the fields the integration genuinely needs and grant the Service User only the permissions that go with them. We document every data flow between Bob and your systems so that your record of processing activities is complete and you can demonstrably comply with the GDPR. We agree up front which party acts as processor or controller.

More about our approach to security: information security policy and CVD policy.

  • GDPR-compliant data processing and minimisation
  • Encryption in transit (TLS 1.2+) and at rest
  • Role-based access and least-privilege principles
  • Audit logs with traceable data flows
  • Token rotation and webhook signature validation
  • Monitoring and alerting for anomalies
  • Secrets management following best practices
  • Documentation for your record of processing activities

Frequently asked questions about Bob HR integrations

Answers to the questions we get asked most often about Bob HR integrations.

A Bob HR integration is a technical link between Bob, the HR platform from HiBob, and another system, such as your payroll tool, identity provider, planning software or your own application. Bob's REST API is used to read and update employee data, leave, compensation and documents programmatically. Webhooks push real-time events, such as a new employee or an approved leave request. An integration can range from simple (synchronising employees in one direction) to extensive (leave, payroll, onboarding and events combined in a continuous flow).

HiBob is the vendor; Bob is the name of the HR platform they make. In everyday speech the two are often used interchangeably. Bob is an HRIS aimed at mid-market and tech/scale-up organisations, with modules for people management, leave, compensation, onboarding and documents. When we talk about a Bob HR integration, we mean an integration with this HiBob platform via the official public API.

Access to the Bob API goes through a Service User: a special account that is not linked to a real employee and only authenticates API requests. You create a service user with an ID and token and grant it exactly the permissions the integration needs. Authentication uses basic access authentication with that ID and token. Because a service user stays active regardless of the status of the person who created it, you avoid an integration breaking when an employee leaves the company. We set up the permissions as narrowly as possible, following least privilege.

Via the Bob API you can read or update, among other things, employee data (people), leave and absence (time off), compensation and payroll data, documents and onboarding information. Which fields are available depends on the permissions you grant the service user; the data the API returns reflects what is visible in the Bob interface under comparable rights. Together with you, we determine which fields the integration needs and deliberately keep the data flow to a minimum.

A simple integration, such as one-way synchronisation of employees to another system, can go live within a few weeks. More extensive scenarios involving leave, payroll, documents, onboarding flows and real-time webhook events usually take longer. After an intake meeting in which we map out the data flows and systems, we will give you a realistic estimate.

Yes. Employee data is personal data by definition, and often sensitive PII such as salary and leave. Appfront builds in line with OWASP ASVS: service user tokens in secure vaults, webhook validation, scoped permissions and least privilege per integration. We limit the data flow to the fields the integration genuinely needs and document every flow, so your processing register stays complete and you can demonstrably comply with the GDPR. We settle up front which party acts as processor or controller.

Yes. Appfront regularly takes over existing integrations, even if they were originally set up by another party. We review the service user permissions, the endpoints used, the webhook configuration and the error handling, document the current setup and draw up improvement proposals. After that, we can handle changes, extensions and monitoring, including timely token rotation.

Bob is a good fit for mid-market and fast-growing tech and scale-up organisations, often with international teams and a modern approach to HR. Typical use cases for an integration: synchronising employees with an identity provider or payroll tool, sending leave data to planning software, exposing compensation data to finance, and automating onboarding by preparing documents and accounts as soon as a new employee appears in Bob.

Ready to build your Bob HR integration?

Tell us which data you want to extract from Bob and which systems (payroll, identity, planning or your own application) it needs to connect to. We're happy to help think through the service user, the required fields and the webhook events. A no-obligation first conversation via contact will quickly give you a clear picture of what's possible.

Edit content