Lever Hiring Python API Docs | dltHub

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

Last updated:

Lever is an applicant tracking and hiring platform that exposes REST APIs for managing job postings, opportunities, requisitions, and related HR data. The REST API base URL is https://api.lever.co/v1 and Supports both HTTP Basic authentication with an API key and OAuth 2.0 Bearer tokens..

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 Lever Hiring data in under 10 minutes.


What data can I load from Lever Hiring?

Here are some of the endpoints you can load from Lever Hiring:

ResourceEndpointMethodData selectorDescription
opportunities/opportunitiesGETdataList all opportunities (candidates)
postings/postingsGETList published job postings
requisitions/requisitionsGETdataList company requisitions
stages/stagesGETdataList hiring pipeline stages
tags/tagsGETdataList tags available in the account

How do I authenticate with the Lever Hiring API?

Lever supports two authentication methods: Basic Auth using an API key (where the key is the username and the password is left blank) and OAuth 2.0. For OAuth, requests require an 'Authorization: Bearer <access_token>' header.

1. Get your credentials

  1. Sign in to your Lever account as a Super Admin. 2. Navigate to Settings > Integrations and API > API Credentials. 3. Click the Generate New Key button. 4. Provide a name for the integration, configure the necessary read/write permissions under the 'Permissions' heading, and choose whether to allow access to confidential data. 5. Click Generate key to create the credential. 6. Click Copy Key to save the API key securely. Note that you cannot edit a key's permissions once generated; you must delete and recreate it if changes are needed.

2. Add them to .dlt/secrets.toml

[sources.lever_hiring_source] api_key = "your_lever_api_key_here"

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 Lever Hiring 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 lever_hiring_pipeline.py

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

Pipeline lever_hiring_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset lever_hiring_data The duckdb destination used duckdb:/lever_hiring.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 opportunities and candidates from the Lever Hiring 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 lever_hiring_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.lever.co/v1", "auth": {"type": "http_basic", "username": "REPLACE_ME", "password": api_key}, }, "resources": [ {"name": "opportunities", "endpoint": {"path": "opportunities", "data_selector": "data"}}, {"name": "requisitions", "endpoint": {"path": "requisitions", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="lever_hiring_pipeline", destination="duckdb", dataset_name="lever_hiring_data", ) load_info = pipeline.run(lever_hiring_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("lever_hiring_pipeline").dataset() sessions_df = data.opportunities.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM lever_hiring_data.opportunities LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("lever_hiring_pipeline").dataset() data.opportunities.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 Lever Hiring 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 Lever Hiring?

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

Available Pipelines