Share
HiBob (Edge) Setup Guide

HiBob (Bob) is a human resources platform that organizations use to manage employee records, compensation, time off, positions, and onboarding and offboarding tasks.

Hevo uses the HiBob API to replicate the employees, employment and compensation history, time off, positions, tasks, and company settings of your HiBob account to the Destination of your choice. Hevo connects to HiBob using a service user, which is an API-only user that HiBob provides for integrations. To ingest data, you must provide Hevo with the ID and token of a service user that has access to the data you want to replicate.


Supported Features

Feature Name Supported
Capture deletes Yes, for the objects that Hevo ingests in full in each run
History mode No
Custom data (user-configured tables & fields) Yes, custom employee fields and the definitions of custom tables
Data blocking (skip objects and fields) Yes
Resync (objects and Pipelines) Yes
API configurable Yes

Handling of Deletes

HiBob does not mark deleted records in its API responses. Hevo captures deletes as follows:

  • Company Field, Company List, Company Position, Company Position Budget, Company Position Opening, Custom Table, Employee, Employee Equity Grant, Employee Life Cycle History, Employee Salary History, Employee Training, Employee Variable Payment, Employee Work History, Employment History, and Task objects and their child objects: Hevo ingests all the records of these objects in each run. If a record that exists in the Destination is not returned by HiBob, Hevo marks it as deleted by setting the value of the metadata column, __hevo__marked_deleted, to True. For example, if you archive a custom field in HiBob, Hevo marks it as deleted in the Company Field object.

  • Employee Out Of Office and Employee Out Of Office Detail objects and their child objects: Hevo does not capture deletes for these objects, so records deleted in HiBob remain in the Destination.


Source Considerations

  • HiBob returns only the data that the permission groups of the service user allow. If you remove a permission from the group, HiBob does not return the corresponding fields or records in the subsequent runs. For the objects that Hevo ingests in full in each run, Hevo marks the records that are no longer returned as deleted. If the service user loses access to an object entirely, Hevo marks the object as inaccessible and stops ingesting it.

  • Hevo ingests the definitions of the custom tables and their columns, but not the entries of the custom tables.

  • The Employee Out Of Office Detail object does not contain the status of a time off request. A canceled request and a pending request both have the value False in the approved column, so you cannot tell them apart.

  • The ID columns that link objects can have different data types in the parent and child objects. For example, the id column of the Employee object is of type VARCHAR, while the employee_id column of the Employee Salary History object is of type BIGINT. Cast the columns to the same data type when you join these objects in your Destination.

  • Hevo creates a table in the Destination only for the objects that have data. For example, if your account does not use positions, the Company Position table is not created.


Last updated on Nov 12, 2026

Tell us what went wrong

Skip to the section