Bullhorn Invenias Python API Docs | dltHub

Invenias is a REST API providing programmatic access to create, read, update, and delete data from a Bullhorn Invenias CRM database. The REST API base URL is https://{subdomain}.invenias.com/api/v1 and All requests require an OAuth2 access token passed as a Bearer token in the header..

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 Bullhorn Invenias data in under 10 minutes.

---

What data can I load from Bullhorn Invenias?

Here are some of the endpoints you can load from Bullhorn Invenias:

---

How do I authenticate with the Bullhorn Invenias API?

The API utilizes OAuth 2.0 to obtain an access token, which must be included in the Authorization header as a Bearer token in the format 'Authorization: Bearer <access_token>'.

1. Get your credentials

1. Access your Invenias instance URL (e.g., https://{subdomain}.invenias.com). \n2. Navigate to the API Swagger documentation by appending /api/swagger/index to your base URL (e.g., https://{subdomain}.invenias.com/api/swagger/index). \n3. Locate the 'api_key' field at the top right-hand corner of the Swagger page and double-click it to generate an API key (you may be prompted to log in with your Invenias admin credentials). \n4. Expand the 'ThirdPartyApplications' section and locate the 'POST /api/v1/thirdpartyapplications' endpoint. \n5. In the request body, provide a JSON object (e.g., { 'Expiration': 'FiveYears', 'Name': 'YourAppName', 'ReplyUrl': 'your_redirect_url', 'FlowType': 'Code' }). \n6. Click 'Try it out!' to execute the request. \n7. Copy the 'ClientId' and 'ClientSecret' from the generated 'Response Body'.

2. Add them to .dlt/secrets.toml

Copy
[sources.bullhorn_invenias_source]
client_id = "your_client_id_here"
client_secret = "your_client_secret_here"
username = "your_username_here"
password = "your_password_here"
subdomain = "your_subdomain_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:

Copy
uv init
uv add "dlt[hub]"

1. Install the dlt AI harness:

Copy
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:

Copy
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 Bullhorn Invenias 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:

Copy
uv run python bullhorn_invenias_pipeline.py

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

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

Inspect your pipeline and data:

Copy
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 /api/v1/thirdpartyapplications and /identity/connect/token from the Bullhorn Invenias API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def bullhorn_invenias_source(access_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://{subdomain}.invenias.com/api/v1",
            "auth": {"type": "bearer", "token": access_token},
        },
        "resources": [
            {"name": "people_list", "endpoint": {"path": "api/v1/people/list", "data_selector": "Items"}},
            {"name": "companies_list", "endpoint": {"path": "api/v1/companies/list", "data_selector": "Items"}}
        ],
    }
    yield from rest_api_resources(config)


def get_data() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="bullhorn_invenias_pipeline",
        destination="duckdb",
        dataset_name="bullhorn_invenias_data",
    )
    load_info = pipeline.run(bullhorn_invenias_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):

Copy
import dlt

data = dlt.pipeline("bullhorn_invenias_pipeline").dataset()
sessions_df = data.people_list.df()
print(sessions_df.head())

SQL (DuckDB example):

Copy
SELECT * FROM bullhorn_invenias_data.people_list LIMIT 10;

In a marimo or Jupyter notebook:

Copy
import dlt

data = dlt.pipeline("bullhorn_invenias_pipeline").dataset()
data.people_list.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 Bullhorn Invenias data to?

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

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.

Copy
uv run dlthub ai toolkit install data-exploration
uv run dlthub ai toolkit install dlthub-platform

• How to deploy a pipeline
• How to explore your data in marimo Notebooks
• How to query your data in Python with dataset
• Join the dlt community on Slack