Hibob integration via Apideck's HRIS unified API — same methods work across every connector in HRIS, switch by changing `serviceId`. Use when the user wants to read or sync employees, departments, payrolls, and time-off records in Hibob. Routes through Apideck with serviceId "hibob".
87
86%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Access Hibob through Apideck's HRIS unified API — one of 58 HRIS connectors that share the same method surface. Code you write here ports to BambooHR, Workday, Deel and 54 other HRIS connectors by changing a single serviceId string. Apideck handles auth, pagination, rate limiting, and retries so you don't write per-tenant Hibob plumbing.
hibobActivate this skill when the user explicitly wants to work with Hibob — for example, "sync employees in Hibob" or "list time-off requests in Hibob". This skill teaches the agent:
serviceId to pass on every call (hibob)For the full method surface (parameters, pagination, filtering), use your language SDK skill:
apideck-node, apideck-python, apideck-dotnet, apideck-java, apideck-go, apideck-php, or apideck-restFor the raw OpenAPI spec:
import { Apideck } from "@apideck/unify";
const apideck = new Apideck({
apiKey: process.env.APIDECK_API_KEY,
appId: process.env.APIDECK_APP_ID,
consumerId: "your-consumer-id",
});
// List employees in Hibob
const { data } = await apideck.hris.employees.list({
serviceId: "hibob",
});The Apideck HRIS unified API exposes the same methods for every connector in its catalog. Switching from Hibob to another HRIS connector is a one-string change — no rewrite, no new SDK.
// Today — Hibob
await apideck.hris.employees.list({ serviceId: "hibob" });
// Tomorrow — same code, different connector
await apideck.hris.employees.list({ serviceId: "bamboohr" });
await apideck.hris.employees.list({ serviceId: "workday" });This is the compounding advantage of using Apideck over integrating Hibob directly: code against the unified HRIS API once, gain access to every connector in it. New connectors Apideck adds become available to your app without code changes.
HiBob (Bob) is a modern HRIS for fast-growing companies. Apideck surfaces 101+ employee fields — the deepest employee coverage in the catalog.
| Bob entity | Apideck HRIS resource |
|---|---|
| Employee | employees (101+ fields) |
| Department | departments |
| Time Off Request | time-off-requests |
| Company | ⚠️ evolving |
| Sites / Locations | derived from employee attributes |
const { data } = await apideck.hris.employees.list({
serviceId: "hibob",
fields: "id,first_name,last_name,email,department,job_title,compensation",
});When an endpoint isn't covered by the HRIS unified API, use Apideck's Proxy to call Hibob directly — Apideck injects auth headers and handles token refresh. Set x-apideck-downstream-url to the target endpoint on Hibob's own API:
curl 'https://unify.apideck.com/proxy' \
-H "Authorization: Bearer ${APIDECK_API_KEY}" \
-H "x-apideck-app-id: ${APIDECK_APP_ID}" \
-H "x-apideck-consumer-id: ${CONSUMER_ID}" \
-H "x-apideck-service-id: hibob" \
-H "x-apideck-downstream-url: <target endpoint on Hibob>" \
-H "x-apideck-downstream-method: GET"See Hibob's API docs for available endpoints.
Other HRIS connectors that share this unified API surface (same method signatures, just change serviceId):
bamboohr, workday, deel (beta), personio, adp-ihcm (beta), adp-workforce-now (beta), paychex (beta), paylocity, and 49 more.
apideck-connector-coverage — programmatic coverage checksapideck-best-practices — architecture, Vault, pagination, error handlingapideck-node — TypeScript / Node SDK patterns9e04d86
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.