Ellipse Gradient for Header

HiBob Integration Guide

Integrate HiBob workforce, employment, time-off, payroll-related, and organizational data with enterprise systems through REST APIs, selected webhook events, and Martini workflows.

HiBob integration options at a glance

HiBob’s primary integration mechanism is its REST API, which provides access to People, Employment, Work, Time off, Payroll, and Company structure data according to account configuration and service-user permissions. HiBob also supports webhook-style notifications for selected events, although coverage is not universal. Martini can consume these APIs, receive supported notifications through an inbound API endpoint, and orchestrate scheduled synchronization when events are unavailable. Service-user credentials and tokens can be stored securely in Martini environment configuration. Large transfers may require pagination, workflow-level batching, controlled concurrency, and rate-limit-aware retries.

Integration pointSupported by HiBob?Common use casesHow Martini supports it
REST APIsYesHiBob REST APIs provide the primary programmatic access method for People, Employment, Work, Time off, Payroll, and Company structure data, subject to account modules and permissions.Martini can consume HiBob REST endpoints from workflows, transform JSON responses, expose selected operations through Martini APIs, and coordinate multi-step synchronization.
WebhooksLimitedHiBob provides webhook-style notifications for selected events and integrations; coverage depends on the event type, product, and configuration.Martini can expose an inbound API endpoint, validate the notification, retrieve the current HiBob resource, and route the event. Scheduled reconciliation covers unsupported events.
AuthenticationYesAPI access generally uses a HiBob service-user ID and token through HTTP Basic Authentication, with permissions controlling accessible resources and operations.Martini can store credentials in environment configuration or secrets management and apply them to outbound API requests without embedding them in workflows.
Bulk or asynchronous APIsNot confirmedA general-purpose HiBob bulk or asynchronous API was not confirmed. Larger transfers may require paginated REST calls and workflow-level batching.Martini can batch requests, control concurrency, schedule workloads, and apply rate-limit-aware retry handling where the REST API permits it.
File and attachment APIsNot confirmedHiBob manages employee and HR-related documents, but a generally available public file or attachment API was not confirmed.Martini should use a confirmed HiBob endpoint or officially supported export mechanism rather than assuming documents are available through standard REST resources.
Database or analytics accessNoDirect customer database access was not confirmed and should not be used as an integration mechanism.Martini integrations should consume supported HiBob APIs or officially supported exports and avoid direct connections to the underlying application database.
Scheduled synchronizationYesScheduled REST synchronization is appropriate for lifecycle changes or resources without applicable webhook coverage.Martini scheduler-triggered workflows can retrieve pages, track synchronization state, transform data, and reconcile downstream systems.

How HiBob exposes data and business events

HiBob REST APIs

HiBob REST APIs are the primary documented integration mechanism for accessing People, Employment, Work, Time off, Payroll, and Company structure resources. The accessible fields and operations depend on account configuration, enabled modules, endpoint behavior, and service-user permissions.

Martini implementation pattern

Martini implementation pattern: A workflow authenticates with a securely stored service-user ID and token, calls the required HiBob endpoint, follows pagination, maps the JSON response into a canonical model, applies business rules, and writes to one or more target systems. Synchronization state is stored outside the transient payload so failed executions can resume safely.

Implementation sequence

Authenticate with the configured HiBob service user
Call the required HiBob REST resource
Retrieve all required pages or batches
Map the response into the target data model
Apply validation, ownership, and lifecycle rules
Upsert the target object using a stable HiBob identifier

HiBob Webhooks

HiBob supports webhook-style notifications for selected events and integrations. Webhook coverage is partial rather than universal, so the available event types and payload details must be confirmed for the relevant HiBob product and configuration.

Martini implementation pattern

Martini implementation pattern: Martini exposes an inbound API endpoint or webhook workflow, validates the notification, checks for duplicate delivery, and treats the event as a signal to retrieve the current People or Employment resource. Events without coverage are handled through scheduled REST reconciliation.

Implementation sequence

Receive the supported HiBob webhook notification
Validate the request and event type
Check the notification against the deduplication key
Retrieve the current HiBob resource
Apply lifecycle and routing rules
Write the result and record processing status

Scheduled HiBob Synchronization

Scheduled synchronization is useful when a resource or lifecycle event does not have applicable HiBob webhook coverage, or when periodic reconciliation is required to detect missed notifications and correct drift.

Martini implementation pattern

Martini implementation pattern: A scheduler-triggered workflow reads its last successful checkpoint, retrieves paginated HiBob resources, applies update-time or segmented filtering when supported, and synchronizes targets with controlled concurrency. The workflow records checkpoints only after successful target processing.

Implementation sequence

Start the workflow on a controlled schedule
Load the last successful synchronization checkpoint
Retrieve the relevant HiBob pages
Normalize and validate each resource
Upsert downstream data idempotently
Store the checkpoint after successful processing

Common HiBob integration patterns

Pattern 1: Provision workforce identities

When to use this pattern

Use this pattern when People or Employment changes in HiBob should create, update, suspend, or deprovision workforce identities. A supported webhook can provide a near-real-time signal; otherwise, scheduled REST synchronization can identify changes.

Integration direction
HiBob
Martini
Okta
Example Mapping
HiBob FieldCanonical FieldTarget Field
People.idperson.externalIdOkta.profile.employeeNumber
People.emailperson.emailOkta.profile.email
Employment.statusemployment.statusOkta.user.status
Work.departmentorganization.departmentOkta.profile.department
Martini implementation pattern

Martini receives a supported event or retrieves changed People and Employment resources, validates identity attributes, applies status-specific provisioning rules, and performs an idempotent Okta update. Duplicate notifications are suppressed using stable identifiers, while transient failures are retried and permission or validation failures are routed for investigation.

Martini capabilities used
  • workflows
  • API consumption
  • data mapping
  • business rules
  • error handling

Pattern 2: Synchronize workforce data

When to use this pattern

Use this pattern to maintain employee, organizational, and employment data in a reporting platform, data warehouse, or enterprise application. It is appropriate when multiple HiBob resources must be joined and periodic reconciliation is acceptable.

Integration direction
HiBob
Martini
Data warehouse
Example Mapping
HiBob FieldCanonical FieldTarget Field
People.idemployee_idemployee.employee_id
Employment.startDateemployment_start_dateemployee.start_date
Work.managermanager_idemployee.manager_id
Company structure.departmentdepartment_codedepartment.department_code
Martini implementation pattern

A scheduled Martini workflow retrieves paginated HiBob resources, joins related People, Employment, Work, and Company structure data, and writes normalized records to the target. It uses a high-water mark where supported, falls back to segmented or full synchronization when necessary, and isolates malformed rows without losing the overall checkpoint.

Martini capabilities used
  • scheduled workflows
  • API consumption
  • data mapping
  • data transformation
  • error handling

Pattern 3: Process time-off updates

When to use this pattern

Use this pattern when approved absences, balances, or time-off activities in HiBob must be reflected in payroll, workforce scheduling, project management, or finance processes.

Integration direction
HiBob
Martini
NetSuite
Example Mapping
HiBob FieldCanonical FieldTarget Field
Time off.requestIdabsence.externalIdabsence.external_id
Time off.employeeIdabsence.employee_idabsence.employee_id
Time off.startDateabsence.start_dateabsence.start_date
Time off.statusabsence.statusabsence.approval_status
Martini implementation pattern

Martini retrieves relevant Time off resources through the HiBob REST API, validates approval status and date semantics, normalizes date-only values and time zones, and upserts the target absence or finance object. Stable external IDs prevent duplicates, while invalid business states are routed for review rather than retried indefinitely.

Martini capabilities used
  • workflows
  • API consumption
  • data mapping
  • date and time transformation
  • validation
  • error handling

Pattern 4: Process employee lifecycle events

When to use this pattern

Use this pattern for onboarding, department changes, manager changes, leave of absence, or termination processes. It combines selected HiBob webhook events with REST retrieval and scheduled reconciliation for lifecycle changes without event coverage.

Integration direction
HiBob
Martini
ServiceNow
Example Mapping
HiBob FieldCanonical FieldTarget Field
Employment.statuslifecycle.statussys_user.active
People.idperson.external_idsys_user.employee_number
Work.managermanager.external_idsys_user.manager
Work.siteorganization.sitesys_user.location
Martini implementation pattern

Martini receives a supported notification, retrieves the current People or Employment resource, evaluates lifecycle rules, and invokes the ServiceNow API. The workflow records event IDs, tolerates repeated notifications, retries transient target errors with backoff, and uses scheduled reconciliation to detect missed or unsupported events.

Martini capabilities used
  • API exposure
  • webhook consumption
  • workflows
  • data mapping
  • business rules
  • deduplication
  • retry handling

Applications commonly integrated with HiBob

HiBob data can be orchestrated with adjacent enterprise applications for workforce lifecycle, identity, service management, finance, and collaboration processes. These patterns should be validated against each target application's API, permissions, and data ownership model.

Application Scenario Direction Martini Pattern
Workday Organizations may synchronize employee and organizational information during HR-platform coexistence, migration, or group-company operations. HiBob → Martini → Workday Martini retrieves HiBob People, Employment, Work, and Company structure data, applies ownership and field-mapping rules, and upserts approved changes into Workday while recording failures for review.
Salesforce Employee, manager, and organizational data can support ownership, approval, and internal operational processes in Salesforce. HiBob → Martini → Salesforce A scheduled or event-driven Martini workflow retrieves the current HiBob resource, normalizes employee and manager identifiers, applies selective-field rules, and updates Salesforce through its API.
ServiceNow HiBob lifecycle data can keep user, employee, and department information aligned for joiner, mover, and leaver processes. HiBob → Martini → ServiceNow Martini receives a supported HiBob event or runs a reconciliation schedule, maps People and Employment data to ServiceNow records, applies lifecycle rules, and retries transient target failures.
Okta Employment lifecycle information can drive workforce identity provisioning, updates, suspension, and deprovisioning. HiBob → Martini → Okta Martini consumes HiBob lifecycle data, validates employment status and required identity attributes, then invokes Okta APIs with idempotent upsert and deprovisioning safeguards.
Microsoft Entra ID Employee attributes and employment status can support onboarding, profile updates, and termination actions in Microsoft Entra ID. HiBob → Martini → Microsoft Entra ID A Martini workflow retrieves People and Employment resources, transforms names, departments, managers, and status values, then calls Microsoft Graph with controlled retries and audit logging.
NetSuite Employee, department, location, and payroll-relevant information can support finance and operational processes. HiBob → Martini → NetSuite Martini synchronizes approved HiBob objects to NetSuite using stable external identifiers, validates required finance fields, and routes permission or schema errors separately from transient failures.
Jira Employee and team information can support project ownership, access, and internal workflow data. HiBob → Martini → Jira Martini maps HiBob People, Work, and organizational attributes to Jira users or project-related data where supported by Jira APIs, with duplicate detection and exception routing.
Slack Workforce lifecycle data can support onboarding, profile updates, and deprovisioning workflows. HiBob → Martini → Slack Martini processes supported HiBob lifecycle signals or scheduled changes, applies identity and status rules, and invokes Slack APIs only after validating required attributes and target state.

How to build a HiBob integration in Martini

Objective

Establish controlled access to HiBob and the target application without embedding credentials in workflows or API definitions.

Instructions in Martini

  • Create a HiBob service user with only the permissions required by the integration
  • Store the service-user ID and token in Martini environment configuration or secrets management
  • Configure the target application's authentication separately
  • Confirm endpoint-specific permissions before processing sensitive HR data

Objective

Select the event or schedule that best matches the required timeliness and HiBob coverage.

Instructions in Martini

  • Use a supported HiBob webhook for selected event-driven processes
  • Use a scheduler trigger when webhook coverage is unavailable
  • Define a reconciliation schedule for missed or duplicated notifications
  • Set controlled concurrency and a suitable polling interval

Objective

Obtain the current HiBob resource rather than relying on incomplete notification payloads.

Instructions in Martini

  • Call the required HiBob REST endpoint
  • Follow the endpoint's pagination behavior
  • Retrieve People, Employment, Work, Time off, Payroll, or Company structure data as permitted
  • Track a high-water mark or checkpoint where supported

Objective

Coordinate retrieval, enrichment, routing, and target-system calls in a maintainable Martini workflow.

Instructions in Martini

  • Separate notification handling from resource retrieval
  • Join related HiBob objects when the target requires a composite model
  • Route lifecycle states and exceptions explicitly
  • Preserve processing state outside transient workflow payloads

Objective

Convert HiBob JSON and account-specific fields into a stable canonical or target schema.

Instructions in Martini

  • Map stable HiBob identifiers to external keys
  • Normalize dates, timestamps, time zones, statuses, and manager references
  • Treat optional and custom fields defensively
  • Limit sensitive fields to the business requirement

Objective

Ensure only valid and authorized changes are sent to downstream systems.

Instructions in Martini

  • Validate required identity and employment fields
  • Apply ownership rules for bidirectional or coexistence scenarios
  • Use upserts rather than blind creates where possible
  • Route permission, validation, and business-state failures separately

Common HiBob data objects used in integrations

ObjectTypical UseCommon target systemsMartini handling
PeopleEmployee and worker identity, contact, and organizational profile data used for workforce synchronization and provisioning.Okta, Microsoft Entra ID, ServiceNow, Salesforce, data warehousesMartini retrieves People through REST APIs, validates required fields, maps stable identifiers, and upserts downstream profiles.
EmploymentStart dates, employment status, employment terms, and lifecycle information used for onboarding, changes, and termination processes.Okta, Microsoft Entra ID, ServiceNow, NetSuite, payroll applicationsMartini combines Employment with People data, applies lifecycle rules, normalizes dates, and routes status changes to target APIs.
WorkJob title, department, manager, site, and other work-related organizational attributes.ServiceNow, Salesforce, Jira, Microsoft Entra ID, reporting platformsMartini maps Work fields to target organizational models and tolerates optional or account-specific fields through validation and transformation rules.
Time offTime-off policies, balances, requests, and related activities used for absence and workforce processes.Payroll applications, workforce scheduling, project management, finance systemsMartini retrieves relevant time-off data, converts date and status representations, prevents duplicate updates, and routes exceptions.
PayrollPayroll-related employee or compensation information where enabled and permitted by the HiBob account.Payroll applications, finance systems, reporting platformsMartini restricts fields to business need, protects sensitive payloads, applies permission-aware mappings, and separates authorization failures from transient errors.
Company structureDepartments, teams, sites, positions, and other organizational reference data.Workday, ServiceNow, Salesforce, NetSuite, data warehousesMartini synchronizes reference data before dependent employee flows, applies stable keys, and handles additions or structural changes through validation.

Authentication and security considerations

Service-user authentication

HiBob API access generally uses a service-user ID and service-user token through HTTP Basic Authentication. Exact requirements vary by API product and endpoint.

Least privilege

Assign only the People, Employment, Work, Time off, Payroll, or organizational permissions required by each workflow. Use separate service users for distinct integration responsibilities where practical.

Credential and data protection

  • Store HiBob credentials in Martini environment configuration or secrets management.
  • Do not embed tokens in workflows, API definitions, logs, or source-controlled mappings.
  • Minimize employee, compensation, payroll, and absence fields sent to downstream systems.
  • Restrict access to Martini APIs and protect sensitive payloads in operational logging.

Operational considerations for HiBob integrations

Pagination and rate limits

HiBob list endpoints may be paginated. Implement endpoint-specific page handling, controlled concurrency, and backoff for HTTP 429 responses.

State and idempotency

Store synchronization checkpoints outside transient workflow payloads. Use stable HiBob identifiers for upserts and tolerate duplicate webhook notifications.

Webhook reconciliation

Treat a webhook as a signal to retrieve the current resource rather than assuming its payload is complete. Use scheduled reconciliation for unsupported or missed events.

Schema and date handling

Account-specific fields and organizational structures can change. Validate required values, tolerate optional fields, and normalize timestamps, time zones, and date-only values explicitly.

Testing and error handling

Test with representative People, Employment, Work, Time off, and organizational data. Separate retryable transport and rate-limit errors from authorization, validation, and business-state failures.

Why use Martini instead of scripts or point-to-point integrations?

Orchestrate more than one API call

Martini coordinates HiBob retrieval, pagination, enrichment, transformation, business rules, and downstream writes in maintainable workflows rather than scattering logic across scripts.

Support event and scheduled models

Martini can receive selected HiBob webhook notifications while also providing scheduled REST synchronization and reconciliation for events without webhook coverage.

Centralize security and operations

Environment configuration, secrets management, validation, retries, checkpoints, and operational logging provide consistent controls for sensitive HR integrations.

Create reusable integration assets

Martini can expose controlled APIs and reusable workflows so multiple applications consume governed HiBob data without creating separate point-to-point implementations.

Frequently asked questions

How can HiBob be integrated with enterprise systems?

HiBob can be integrated primarily through its REST APIs, which expose People, Employment, Work, Time off, Payroll, and Company structure data subject to account configuration and permissions. HiBob also supports webhook-style notifications for selected events. Scheduled REST synchronization can cover changes without applicable webhook support.

Can Martini integrate with HiBob?

Yes. Martini can consume HiBob REST APIs, securely apply HiBob service-user authentication, receive supported webhook notifications through an inbound API, map HiBob data, and orchestrate workflows with downstream applications.

Do I need a connector to integrate HiBob with Martini?

No. A dedicated HiBob connector is not required. Martini can integrate with HiBob using its confirmed REST APIs, selected webhook notifications, service-user authentication, and scheduled workflows.

Is there any extra Lonti cost to integrate HiBob with Martini?

Lonti does not charge an additional per-connector or per-vendor fee to integrate HiBob. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from HiBob, cloud infrastructure, target applications, or other third-party services depending on subscriptions, usage, and deployment model.

Which HiBob integration methods should be used?

REST APIs are HiBob's primary documented integration method and should be used for People, Employment, Work, Time off, Payroll, and organizational data. Webhook-style notifications are useful for selected events, while scheduled REST synchronization is appropriate for unsupported or reconciliation scenarios. No official HiBob GraphQL or SOAP API was confirmed.

Can Martini receive HiBob events in real time?

Martini can receive HiBob webhook notifications for events supported by HiBob's webhook functionality. Coverage is event-specific rather than universal, so lifecycle changes without an applicable notification should be handled through scheduled REST reconciliation.

How does synchronization and data mapping work?

A Martini workflow retrieves the current HiBob resource, follows pagination, maps vendor fields into a canonical or target model, applies validation and business rules, and performs an idempotent upsert. Stable HiBob identifiers, checkpoints, and controlled retries help maintain consistency.

How are HiBob errors, retries, and duplicates handled?

Martini can separate authentication, authorization, validation, rate-limit, transient server, and business-state errors. Transient failures can be retried with backoff, while permission and schema errors can be routed for investigation. Stable identifiers and webhook event keys support duplicate-resistant processing. Martini can also expose a controlled API façade for downstream applications that need selected HiBob operations.

Related Martini documentation

API Workflows

Data Processing

Security

Operations

Integrate HiBob with Martini

Use Martini to connect HiBob REST APIs and supported webhook events with the systems that run your workforce, identity, finance, and service-management processes.

EXPLORE MARTINI
BOOK A DEMO