Integrations
HiBob Integration Services
HiBob is popular with fast-growing, multi-country companies, and every Bob account is configured differently. We build HiBob integrations that handle custom fields, tables and permissions, and keep people data in sync.
We build integrations with HiBob (Bob) using its Public API, service users and webhooks. Typical use cases are provisioning employees into an LMS or SaaS app, syncing departments, sites and managers, pulling time off and lifecycle data, and writing training records back to Bob. A single HRIS→LMS sync usually takes 3–6 weeks.
Who is this for?
- SaaS vendors whose customers run HiBob. HiBob is a frequently requested HRIS among mid-market and international buyers. A reliable Bob connector, ready for HiBob’s marketplace, removes a common blocker in deals.
- Companies running HiBob. You want Bob to be the single source of truth for your LMS, IT, finance and collaboration tools, without exporting reports by hand.
What do we build?
- Employee provisioning New joiners, changes and leavers flow from Bob into your LMS (e.g. LearnUpon), SaaS app or identity provider.
- Org structure sync Departments, sites, teams and reporting lines mapped to groups and approval chains.
- Time off and availability Approved leave and who’s-out data for scheduling, resourcing or payroll tools.
- Write-back Training completions, certifications or custom field values written back to Bob employee records.
- Marketplace connectors A multi-customer HiBob connector for your SaaS, with per-customer field mapping and onboarding.
Typical data flows
| Data | Direction | Method | Frequency |
|---|---|---|---|
| Employee fields (standard and custom) | Bob → target | People search API | Webhooks + nightly reconcile |
| Joiners, leavers, field changes | Bob → target | Webhooks (employee events) | Near real-time |
| Work history and lifecycle tables | Bob → target | Employee table endpoints | On change |
| Time off | Bob → target | Time off API (who’s out, requests) | Hourly / daily |
| Training records, custom fields | Target → Bob | API write-back (fields, custom tables) | Event-driven |
Have an integration request in your backlog?
Send it over. You get a written scope and a fixed quote within 2–3 days.
How do we approach HiBob?
- API and authentication Bob’s Public API is a REST API authenticated with service user credentials (an ID and token) over basic auth. Each service user belongs to a permission group, so the integration sees only the fields and employees it needs.
- Events and change detection Bob webhooks are signed with HMAC-SHA512 in the Bob-Signature header, which we verify against the raw request body. Payloads are lightweight, naming the event, the employee and the changed fields, so we fetch current data from the API and run a nightly reconcile.
- Known gotchas Fields are addressed by path, such as work.department, and custom fields and tables differ per account, so we discover the schema per customer rather than hard-code it. Endpoints have their own rate limits, so full syncs on large accounts are batched and back off on HTTP 429.
Delivery process
- Scoping (2–3 days) Systems, fields and edge cases mapped; written scope and fixed quote.
- Build (2–5 weeks) Senior-reviewed build with weekly demos.
- Reconcile and launch Dry run, source-vs-target report, cutover.
- Run and maintain Monitoring, alerts and fixes when APIs change.
Proof
Related work. As a LearnUpon Professional Partner, we connect enterprise customers’ HRIS, CRM, SSO and internal systems to LearnUpon, and HRIS→LMS provisioning is a core part of that work. HiBob projects use the same provisioning, reconciliation and monitoring patterns we apply across the 200+ platforms we’ve integrated. See our case studies.
FAQ
Frequently asked questions
Can't find your question? An integration engineer will answer it.
Last updated
Which HiBob products do you integrate with?
HiBob’s Bob platform, including core people data, custom fields and tables, time off and lifecycle data, through the Public API and webhooks.
How long does a HiBob integration take?
A single HRIS→LMS sync usually takes 3–6 weeks. A multi-customer marketplace connector takes longer, depending on the onboarding flow and HiBob’s partner requirements.
Can you maintain it after launch?
Yes. We offer monitoring, alerting and ongoing support, or a full handover with documentation.
Scope your HiBob integration in 30 minutes.
Tell us what needs to connect and get a clear plan.