Bob Python API Docs | dltHub
Build a Bob-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
Hibob is an HR management platform that provides a REST API for accessing and managing employee data, custom fields, and business operations. The REST API base URL is https://api.hibob.com/v1/ and all requests require an 'Authorization' header with Basic authentication for service users.
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 pip install "dlt[workspace]" and start loading Bob data in under 10 minutes.
What data can I load from Bob?
Here are some of the endpoints you can load from Bob:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| work_history | /v1/bulk/people/work | GET | List work history for a list of employees | |
| lifecycle_history | /v1/bulk/people/lifecycle | GET | List the lifecycle history for a list of employees | |
| employment_history | /v1/bulk/people/employment | GET | List employment history for a list of employees | |
| payroll_history | /v1/bulk/people/salaries | GET | List payroll history (salaries) for a list of employees | |
| dependents | /v1/bulk/people/dependents | GET | List dependents for a list of employees |
How do I authenticate with the Bob API?
Hibob supports Basic authentication for service users, requiring an 'Authorization' header with the format 'Basic '. The credentials consist of 'SERVICE-USER-ID
' combined and Base64 encoded.1. Get your credentials
To obtain API credentials for the Hibob (Bob) REST API, follow these steps in your Hibob account: 1. Navigate to the Service Users configuration page (usually found in system settings or integration settings). 2. Create a new Service User. 3. Upon creation, you will be provided with a unique Service User ID and a one-time API Token. 4. Assign the Service User to a permission group with the necessary access rights for the data you intend to retrieve. 5. Keep the ID and Token secure; they are required to build the HTTP Basic Authentication header, formatted as 'Basic <base64_encoded_id
>'."},secrets_toml_example:{citations:,confidence:2. Add them to .dlt/secrets.toml
[sources.bob_source] service_user_token = "base64_encoded_id: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 venv && source .venv/bin/activate uv pip install "dlt[workspace]"
1. Install the dlt AI harness:
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:
dlthub ai toolkit rest-api-pipeline install
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 Bob 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:
python bob_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline bob_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset bob_data The duckdb destination used duckdb:/bob.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline bob_pipeline 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 profiles and people/search from the Bob 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 bob_source(service_user_credentials=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.hibob.com/v1/", "auth": {"type": "http_basic", "username": "REPLACE_ME", "password": service_user_credentials}, }, "resources": [ {"name": "work_history", "endpoint": {"path": "v1/bulk/people/work"}}, {"name": "employment_history", "endpoint": {"path": "v1/bulk/people/employment"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="bob_pipeline", destination="duckdb", dataset_name="bob_data", ) load_info = pipeline.run(bob_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("bob_pipeline").dataset() sessions_df = data.work_history.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM bob_data.work_history LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("bob_pipeline").dataset() data.work_history.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 Bob data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example 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.
dlthub ai toolkit data-exploration install dlthub ai toolkit dlthub-platform install
Was this page helpful?
Community Hub
Need more dlt context for Bob?
Request dlt skills, commands, AGENT.md files, and AI-native context.