Hibob Python API Docs | dltHub

Build a Hibob-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.

Last updated:

Hibob is an HRIS platform providing a RESTful public API for accessing employee data, metadata, and related HR resources. The REST API base URL is https://api.hibob.com/v1 and all requests require an 'Authorization' header using Basic auth with a Service User ID and token.

dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv add "dlt[hub]" and start loading Hibob data in under 10 minutes.


What data can I load from Hibob?

Here are some of the endpoints you can load from Hibob:

ResourceEndpointMethodData selectorDescription
employersv1/employers/searchPOSTSearch for employers
calendar_eventsv1/timeoff/calendars/events/searchPOSTSearch calendar events
employee_work_historyv1/people/employees/{id}/workHistoryGETList employee's work history
employee_salary_historyv1/people/employees/{id}/salaryHistoryGETList employee's salary history
employee_employment_historyv1/people/employees/{id}/employmentHistoryGETList employee's employment history

How do I authenticate with the Hibob API?

The API requires HTTP Basic authentication. To authenticate, concatenate the Service User ID and token with a colon ('ID

'), then Base64-encode the resulting string and include it in the 'Authorization' header as 'Basic '.

1. Get your credentials

To obtain API credentials for Hibob: 1. Log in to your Hibob workspace as an administrator. 2. Navigate to the Service Users configuration page (typically under System Settings > Integrations > API Service Users, or a similar path in your administration dashboard). 3. Create a new service user by providing a name and ensuring you assign it to the necessary permission groups to grant access to the specific data or endpoints you require. 4. Upon creation, the system will display a unique Service User ID and a Token. You must copy these immediately, as the token cannot be retrieved again once the window is closed; if lost, you must generate a new token.

2. Add them to .dlt/secrets.toml

[sources.hibob_source] service_user_id = "your_service_user_id" service_user_token = "your_service_user_token"

dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.


How do I set up and run the pipeline?

Set up a virtual environment and install dlt:

uv init uv add "dlt[hub]"

1. Install the dlt AI harness:

uv run dlthub ai init --agent <your-agent> # <agent>: claude | cursor | codex

This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →

2. Install the rest-api-pipeline toolkit:

uv run dlthub ai toolkit install rest-api-pipeline

This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →

3. Start LLM-assisted coding:

Use /find-source to load data from the Hibob API into DuckDB.

The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.

4. Run the pipeline:

uv run python hibob_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline hibob_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset hibob_data The duckdb destination used duckdb:/hibob.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

uv run dlthub show

This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.


Python pipeline example

This example loads people/search and profiles from the Hibob API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def hibob_source(service_user_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.hibob.com/v1", "auth": {"type": "http_basic", "username": "REPLACE_ME", "password": service_user_token}, }, "resources": [ {"name": "employers", "endpoint": {"path": "v1/employers/search", "data_selector": "results"}}, {"name": "calendar_events", "endpoint": {"path": "v1/timeoff/calendars/events/search", "data_selector": "results"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="hibob_pipeline", destination="duckdb", dataset_name="hibob_data", ) load_info = pipeline.run(hibob_source()) print(load_info)

To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.


How do I query the loaded data?

Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.

Python (pandas DataFrame):

import dlt data = dlt.pipeline("hibob_pipeline").dataset() sessions_df = data.employers.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM hibob_data.employers LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("hibob_pipeline").dataset() data.employers.df().head()

See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.


What destinations can I load Hibob data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample value
DuckDB (local, default)"duckdb"
PostgreSQL"postgres"
BigQuery"bigquery"
Snowflake"snowflake"
Redshift"redshift"
Databricks"databricks"
Filesystem (S3, GCS, Azure)"filesystem"

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.


Next steps

Continue your data engineering journey with the other toolkits of the dltHub AI harness:

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-platform — Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform

Was this page helpful?

Community Hub

Need more dlt context for Hibob?

Request dlt skills, commands, AGENT.md files, and AI-native context.

Available Pipelines