Yes, Jaapi integrates with HiBob. A scheduled sync of your active employees keeps the swag store’s user list current and lets Bob fields drive credit — welcome budgets on start date, anniversary gifts, per-site amounts. New joiners get store access on day one, leavers are deactivated with unspent credit reclaimed, and the user list stops being anyone’s job.
How does the HiBob integration work?
The sync starts from a report in Bob listing active employees with the fields the store should see — email, name, employee ID, plus anything that should drive credit (start date, department, site). Bob is well equipped for getting that report out on a schedule: its scheduled reports feature runs any report automatically, and the Reports API serves report downloads to a read-only service user.
Either way, the export lands at Jaapi’s sync endpoint authenticated with a Bearer token — for the API route, a small scheduled job fetches and forwards it (a few lines in a cron job, Make, or Power Automate; we provide a working script). Jaapi reconciles the list against the store’s users on every run.
What does the HiBob sync automate?
One daily reconciliation covers three workflows:
- Onboarding. Anyone in today’s report without a store account gets one, with any welcome credit allocated immediately.
- Offboarding. Anyone missing from today’s report is deactivated, and their unspent credit returns to the company wallet.
- Credit distribution. Bob fields drive the rules — a welcome budget for new starters, monthly allowances per department, site-aware amounts where swag costs differ.
How do I set up the HiBob integration?
- Build a report in Bob with your active employees and the fields the store needs. Email is the only required column.
- Create a service user with read access to the report (for the API route), or configure the report’s schedule.
- Send us a sample export. We map the columns, agree the credit rules and a first-run plan with you, and help wire up the delivery.
Most teams are live within a working week.
HiBob or SCIM — which should I use?
If you only need account creation and deactivation, SCIM from your identity provider (Okta, Entra ID, Rippling) is the simplest route. Use the Bob sync when HR data should also drive credit and gifting — SCIM doesn’t carry start dates, departments, or sites. Many customers run both, and they don’t conflict: SSO plus SCIM for access, the Bob report for credit logic. Our HRIS swag automation guide has the full comparison.
Is the integration secure?
Yes. The Bob service user is read-only and stays on your side; requests to Jaapi use a store-scoped Bearer token over HTTPS, new accounts are validated against your allowed email domain, and every sync run is audit-logged. Jaapi AB is ISO 27001:2022 certified with EU-hosted data.
