HiBob

HiBob is a modern human resources information system (HRIS) that provides comprehensive employee lifecycle management, including onboarding, performance tracking, payroll integration, and workforce analytics, helping organizations build engaged teams and streamline HR operations.

Power end-to-end data operations for your HiBob API with Nexla. Our bi-directional HiBob connector is purpose-built for HiBob, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to HiBob or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your HiBob workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating a HiBob credential, you need to obtain a Service User ID and Service User Token from your HiBob account. The Service User ID and Service User Token are required for Basic authentication with the HiBob API.

To obtain your Service User ID and Service User Token, you need to have a HiBob account with admin access. Once you have access to your account, you can create and manage Service Users in your HiBob account settings. Service Users are special API users that are designed for programmatic access to the HiBob API. The Service User ID is used as the username, and the Service User Token is used as the password in Basic authentication for all API requests to the HiBob API. For detailed information about Service Users and authentication setup, refer to the HiBob API Service Users documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
Service User ID	Yes	No	Enter your HiBob API Service User ID. Check out https://apidocs.hibob.com/docs/api-service-users for details about Service Users
Service User Token	Yes	Yes	Enter your HiBob API Service User Token. Check out https://apidocs.hibob.com/docs/api-service-users for details about Service Users

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – HiBob

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter your HiBob Service User ID in the Service User ID field. This is the Service User ID you obtained from your HiBob account settings. The Service User ID is used as the username in Basic authentication for all API requests to the HiBob API.

   Your HiBob Service User ID can be found in your HiBob account settings where you manage Service Users. Service Users are special API users designed for programmatic access to the HiBob API. The Service User ID is used as the username in Basic authentication for all API requests to the HiBob API. For detailed information about creating and managing Service Users, see the HiBob API Service Users documentation.

4. Enter your HiBob Service User Token in the Service User Token field. This is the Service User Token you obtained from your HiBob account settings. The Service User Token is used as the password in Basic authentication for all API requests to the HiBob API.

   Keep your Service User Token secure and do not share it publicly. The Service User Token provides access to your HiBob account data and should be treated as sensitive information. Your HiBob Service User Token can be found in your HiBob account settings where you manage Service Users. The Service User Token is used as the password in Basic authentication for all API requests to the HiBob API. For detailed information about creating and managing Service Users, see the HiBob API Service Users documentation.

5. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the HiBob connector tile, then select the credential that will be used to connect to the HiBob account, and click Next; or, create a new HiBob credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common HiBob endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

Fetch all Employees

Fetch a list of all active employees. The data is filtered based on the access level of the logged-in user. Only viewable categories are returned.

• This endpoint automatically retrieves all active employees from your HiBob account. No additional configuration is required beyond selecting this endpoint template.
• The endpoint uses GET requests to https://api.hibob.com/v1/people. The endpoint URL is automatically constructed based on the HiBob API base URL.
• The endpoint does not use pagination (iteration.type: static.url) and returns a single response. The response data path is $.employees[*], which extracts all items from the employees array in the API response.
• The data returned is filtered based on the access level of the Service User used for authentication. Only viewable categories are returned, ensuring that sensitive information is not exposed based on the Service User's permissions.

This endpoint retrieves all active employees from your HiBob account. The data is filtered based on the access level of the Service User used for authentication, so only viewable categories are returned. This ensures that sensitive information is not exposed based on the Service User's permissions. The endpoint returns employee information including personal details, employment information, and other relevant data based on the Service User's access level. For detailed information about the API response format and available fields, see the HiBob API documentation.

Fetch Work History of All Employees

Returns a list of work history entries for all active employees.

• This endpoint automatically retrieves work history entries for all active employees from your HiBob account using a multi-step process. No additional configuration is required beyond selecting this endpoint template.
• The endpoint first retrieves all active employees using GET requests to https://api.hibob.com/v1/people. The response data path is $.employees[*], which extracts all items from the employees array.
• For each employee retrieved in the first step, the endpoint then retrieves their work history using GET requests to https://api.hibob.com/v1/people/{employee_id}/work where {employee_id} is the ID of each employee from the first step. The response data path is $.values[*], which extracts all items from the values array in the API response.
• The endpoint processes all employees and their work history entries, creating a comprehensive dataset of work history information for all active employees.

This endpoint retrieves work history entries for all active employees from your HiBob account. The endpoint uses a multi-step process: first retrieving all active employees, then fetching work history for each employee. This ensures that you get a complete view of work history across all employees. The data is filtered based on the access level of the Service User used for authentication, so only viewable information is returned. For detailed information about the API response format and available fields, see the HiBob API documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

HiBob data sources can also be manually configured to ingest data from any valid HiBob API endpoint, including endpoints not covered by the pre-built templates or when custom API configurations are required. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

HiBob API endpoints typically follow the pattern https://api.hibob.com/v1/{endpoint_path} and return data in JSON format. The endpoint requires Basic authentication via the Authorization header, where the Service User ID is sent as the username and the Service User Token is sent as the password, which is handled automatically by your credential configuration. For detailed information about HiBob API endpoints and available APIs, see the HiBob API documentation.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new HiBob data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination

Click the + icon on the Nexset that will be sent to the HiBob destination, and select the Send to Destination option from the menu. Select the HiBob connector from the list of available destination connectors, then select the credential that will be used to connect to the HiBob organization, and click Next; or, create a new HiBob credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common HiBob endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

Create Employees from Nexset Records

Create employees from records in Nexset. Please check API documentation link for all required properties in Nexset record.

• This endpoint automatically creates new employees in your HiBob account using data from your Nexset. No additional configuration is required beyond selecting this endpoint template.
• The endpoint uses POST requests to https://api.hibob.com/v1/people. The endpoint URL is automatically constructed based on the HiBob API base URL.
• The endpoint sends data from your Nexset as the request body in JSON format. The request body is automatically formatted according to the schema fields and data mapping you configure. Each record in your Nexset will be sent as a JSON object containing the employee data to create.
• Batch mode is disabled by default for this endpoint. Each record in your Nexset will be sent as a separate API request to create an employee. If you need to create multiple employees, you can send multiple records, but each will be processed as a separate request.
• This endpoint does not automatically create a data source to track the responses received from the HiBob API after each call.

The request body must be properly formatted JSON that matches the HiBob API specification for creating employees. The endpoint requires Basic authentication via the Authorization header, where the Service User ID is sent as the username and the Service User Token is sent as the password, which is handled automatically by your credential configuration. The Content-Type: application/json header is automatically included in requests. Please check the API documentation link for all required properties that must be included in your Nexset records. Batch mode is disabled by default (batch.mode: false), so each record will be sent as a separate request. For detailed information about creating employees, including required fields, field names, and request formats, see the HiBob API documentation.

Manual configuration

HiBob destinations can also be manually configured to send data to any valid HiBob API endpoint, including endpoints not covered by the pre-built templates or when custom API configurations are required. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

HiBob API endpoints typically follow the pattern https://api.hibob.com/v1/{endpoint_path} and expect JSON format for request bodies. The endpoint requires Basic authentication via the Authorization header, where the Service User ID is sent as the username and the Service User Token is sent as the password, which is handled automatically by your credential configuration. For detailed information about HiBob API endpoints and available APIs, see the HiBob API documentation.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured HiBob endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the HiBob endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.