HiBob: moving from the legacy connector to the OAuth connector
Apideck has two HiBob connectors:
HiBob (Legacy) | HiBob (OAuth) | |
|---|---|---|
How customers connect | They create a service user in Bob and paste its ID and token into Vault | They click Connect and install your app from the HiBob Marketplace. Nothing to copy or paste. |
Your setup | None | Your own HiBob Marketplace app, as a HiBob partner |
Data available | Same resources and events | Same resources and events |
HiBob is moving its integration partners to its App Marketplace, which uses OAuth. For new integrations, use the HiBob (OAuth) connector.
What you need to set up
Join HiBob's partner programme. OAuth apps are only available to HiBob Tech Partners. Apideck can't provide shared HiBob credentials.
Create your HiBob Marketplace app in HiBob's developer portal. Set the redirect URI and the scopes your integration needs.
Add the app's Client ID, Client Secret and App ID in Apideck under Configuration → HRIS → HiBob (OAuth). Start with Development credentials.
Pass HiBob's technical review. HiBob issues Production credentials after it. Then switch the credentials type to Production.
The full steps are in the HiBob (OAuth) configuration guide. For questions about the partner programme, its review or costs, contact HiBob directly.
Moving your customers over
Each customer connects again with the HiBob (OAuth) connector. A Bob admin (or a user allowed to install Marketplace apps) clicks Connect, reviews the install screen and approves it. See the HiBob (OAuth) connection guide.
It's a new connection in Apideck, with its own connection ID. Employee data comes from the same HiBob account, so the HiBob employee IDs should match what you already have. Check this against your own data before switching over fully.
Webhooks: the new connection gets its own virtual webhook polling. Its first sync records a starting point, so events begin from the next sync.
Once the new connection works, disconnect the legacy one.
Things to know
Disconnecting takes two steps. To fully disconnect a HiBob (OAuth) connection, the customer disconnects in Apideck and uninstalls the app in Bob (Settings → Integrations → Marketplace apps). If they only do one, reconnecting fails with "App is already installed", or the connection looks connected but returns no data.
What you can read depends on what was approved at install. HiBob returns only the fields and employees covered by the scopes and the people-data access chosen when the app was installed. It doesn't return an error for the rest. To change this, the customer uninstalls and reinstalls the app.
Moving to OAuth doesn't fix missing data on its own. If fields or employees are missing today because of permissions, check the access settings in Bob for the new install too. See HiBob: Missing or Incorrect Employee Fields Due to Service User Permissions.
Contact Apideck support through the Customer Portal (the Requests link at the top of this help center), your Slack channel with us, or support@apideck.com if you need help planning the move.