In HiBob (Bob), create an API Service User under Settings > Integrations > Service Users; assign it to a permission group that grants access to the required employee data fields.
Note the service user's ID and token provided at creation time — these are displayed once and cannot be retrieved again.
Authenticate using HTTP Basic Auth with the service user ID as the username and the service user token as the password; Base64-encode the id:token pair for the Authorization header.
Call GET https://api.hibob.com/v1/people to retrieve all employees, using pageSize and cursor parameters for pagination (pageSize up to 1000 records per page).
Use GET https://api.hibob.com/v1/people/{id} to retrieve the full record for a specific employee.
Known gotchas
The legacy API Access Token authentication method has been shut off — only Service User credentials are accepted; integrations built on the old token method must be migrated.
Service users are not tied to real employee accounts and remain active regardless of HR changes, but they must be assigned to a permission group — without permissions the token authenticates but returns empty or restricted data.
The service user ID and token are shown only once at creation; store them securely immediately, as there is no way to retrieve the token again after leaving the creation screen.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp