Authenticate to Bob's public API with a service user and read employee data via the People search endpoint.
domain: apidocs.hibob.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
In Bob, create a new API Service User to get an ID and token (service users can't log into Bob and exist only to authenticate API calls).
Create a dedicated permission group, add the service user to it, and grant view access to the 'root,' 'about,' 'employment,' and 'work' categories (Default Employee Fields) needed for basic reads.
Fetch field metadata first to learn field IDs, categories, and data types before building your query.
Authenticate each request with the service user ID and token in the Authorization header.
POST to /v1/people/search with a fields array (dot-notation IDs like root.id, work.department) and optional filters to retrieve employee records in one response.
Set showInactive: true in the request when you need terminated, inactive, or former employees, since the default excludes them.
Known gotchas
The search endpoint has no pagination — it returns all matching employees in a single call, so for large companies fetch just root.id first, then batch subsequent calls filtered by id.
If the service user lacks permission for a requested field, the API silently drops it from the response (still HTTP 200) rather than erroring — always verify all expected fields actually came back.
Response keys use slash notation (e.g. /root/id) even though fields are requested using dot notation (root.id) — parsing must account for this mismatch.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?