Hibob Bob API

Name: Bob API
Brand: Bob API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentHR recruitingEmployee ManagementapiKey, basic94 EndpointsREST

For Agents

Manage HiBob employees, onboarding, time-off, attendance, custom fields, and reports through 94 endpoints with token or Basic authentication, including a sandbox host.

Install Jentic One Beta

Connect the Bob API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Bob API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Bob API.

Search employees with rich filters via POST /people/search and read details via GET /people/{identifier}

Create, update, terminate, and uninvite employees through the /people and /employees endpoints

Onboard new hires by setting start dates and sending welcome wizards via POST /employees/{employeeId}/invitations

GET STARTED

Start building with Bob API

Explore with Jentic

View OpenAPI Document

The Bob API is HiBob's HR platform interface for managing employees, onboarding, time-off, attendance, reports, and company configuration. Across 94 endpoints, integrators can search and read employees, create and terminate employees, set start dates and welcome wizards, manage avatars and tasks, configure custom fields and named lists, submit and inspect time-off requests, query who's-out today, and import attendance. Authentication accepts a Bearer-style API token in the Authorization header or HTTP Basic for service users, and a sandbox host (api.sandbox.hibob.com) is available for testing.

Use Cases

Patterns agents use Bob API for, with concrete tasks.

★ Joiner-Mover-Leaver Automation

HRIS automations create new employees with POST /people, set their start date via POST /employees/{employeeId}/start-date, and trigger welcome wizards through POST /employees/{employeeId}/invitations. When someone leaves, POST /employees/{identifier}/terminate handles the termination workflow and POST /employees/{identifier}/uninvite revokes Bob access. This collapses what is typically a multi-tab UI process into a single workflow.

Call POST /people to create the employee, then POST /employees/{employeeId}/invitations with welcome wizard id 42, then POST /employees/{employeeId}/start-date with the agreed date.

Time-Off Coordination

Workforce planning agents read who's-out via GET /timeoff/whosout and GET /timeoff/outtoday, then submit time-off requests with POST /timeoff/employees/{id}/requests when an employee asks via Slack or chat. Balance enquiries through GET /timeoff/employees/{id}/balance let the same agent confirm policy entitlements before submitting.

Call GET /timeoff/employees/1234/balance to confirm vacation balance, then POST /timeoff/employees/1234/requests for the requested dates.

Reporting Pipeline

Analytics teams trigger HR reports via GET /company/reports to discover available reports, then GET /company/reports/{reportId}/download or its async variant to fetch the file. The async download polling pattern handles large reports without blocking the request, ideal for warehouse loaders that ship daily or weekly headcount data.

Call GET /company/reports/{reportId}/download-async, poll the returned URL until the file is ready, then push the contents to a data warehouse loader.

AI Agent HR Operations

Through Jentic, an AI assistant can answer 'how many people are out today?' or 'what's John's start date?' by calling Bob's read endpoints, and submit time-off requests for an employee on demand. Jentic's vault holds the API token, so the agent operates on HR data without seeing the raw credential — important for SOC-2 controls.

Search Jentic for 'who is out of the office today', execute GET /timeoff/outtoday, and return the list as a Slack-friendly summary.

Key Endpoints

94 endpoints — the bob api is hibob's hr platform interface for managing employees, onboarding, time-off, attendance, reports, and company configuration.

METHOD

PATH

DESCRIPTION

POST

/people/search

Search employees with rich filters

POST

/people

Create an employee

POST

/employees/{employeeId}/invitations

Send a welcome wizard invitation

POST

/employees/{identifier}/terminate

Terminate an employee

POST

/timeoff/employees/{id}/requests

Submit a time-off request

GET

/timeoff/whosout

List employees out of the office on a given date

GET

/company/reports/{reportId}/download-async

Async download URL for a large HR report

POST

/people/search

Search employees with rich filters

POST

/people

Create an employee

POST

/employees/{employeeId}/invitations

Send a welcome wizard invitation

POST

/employees/{identifier}/terminate

Terminate an employee

POST

/timeoff/employees/{id}/requests

Submit a time-off request

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

HiBob service-user tokens and Basic credentials are stored encrypted in the Jentic vault. Agents call Bob via Jentic and the right Authorization header is injected per endpoint, so the raw credential never enters the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'create an employee' or 'who is out today') and Jentic returns the matching Bob operation with its input schema, so the agent calls the right endpoint without scanning HiBob's docs.

Time to first call

Direct HiBob integration: 3-5 days for service-user setup, async report polling, custom fields, and time-off flows. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using Bob API through Jentic.

What authentication does the Bob API use?

The Bob API supports two schemes: a service-user token passed as Authorization: Bearer <token> (the Bearer scheme in the spec is implemented as an apiKey-style header), or HTTP Basic for service users. Tokens are generated under HiBob's automation users. Through Jentic, both credential types live in the encrypted vault and are injected at execution time.

Can I create and onboard a new employee with the Bob API?

Yes. POST /people creates the employee record; POST /employees/{employeeId}/start-date sets or updates the start date; POST /employees/{employeeId}/invitations sends a welcome wizard. The three calls together handle the onboarding flow that is otherwise multiple screens in the Bob UI.

How do I download a HiBob report through Jentic?

Run pip install jentic, search for 'download a hibob report', and choose between GET /company/reports/{reportId}/download for synchronous downloads or GET /company/reports/{reportId}/download-async for large files. Jentic resolves the auth header from the vault.

Is there a sandbox environment for the Bob API?

Yes — the spec lists https://api.sandbox.hibob.com/v1 as an alternate server. Use it for development and integration testing before pointing your integration at https://api.hibob.com/v1 in production.

How do I list employees who are out today?

Call GET /timeoff/outtoday for the current day or GET /timeoff/whosout with a date parameter for a specific date. Both return the list of employees on time off so an agent can build an out-of-office digest without reading individual time-off records.

What are the rate limits for the Bob API?

HiBob enforces per-token rate limits that are not published in the spec but are returned through HTTP 429 responses. Implement backoff on 429 responses and prefer the async report download endpoints for any payload over a few megabytes to avoid tying up request slots.

Hibob Bob API

Connect the Bob API to your agent

Capabilities

Start building with Bob API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs