Junction Lab Testing Python API Docs | dltHub

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

Last updated:

Junction Lab Testing is a REST API platform for ordering, managing, and retrieving lab tests, appointments, and results. The REST API base URL is https://api.us.junction.com/ (Production US), https://api.eu.junction.com/ (Production EU), https://api.sandbox.us.junction.com/ (Sandbox US), https://api.sandbox.eu.junction.com/ (Sandbox EU) and Requests require either an x-vital-api-key header or an Authorization: Bearer token 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 Junction Lab Testing data in under 10 minutes.


What data can I load from Junction Lab Testing?

Here are some of the endpoints you can load from Junction Lab Testing:

ResourceEndpointMethodData selectorDescription
lab_tests/v3/lab_testGETdataPaginated list of lab tests
lab_test/v3/lab_tests/{lab_test_id}GETlab_testRetrieve a single lab test by ID
labs/v3/lab_tests/labsGETList all available labs
lab_accounts/v3/lab_test/lab_accountGETGet lab accounts for the team
orders/v3/ordersGETdataList orders with optional filters

How do I authenticate with the Junction Lab Testing API?

Junction Lab Testing API supports two authentication methods: Team API Key (passed in the x-vital-api-key header) or Team API Access Token (passed in the Authorization header as a Bearer token). Management endpoints require an X-Management-Key header.

1. Get your credentials

  1. Sign into the Junction Dashboard at app.junction.com. 2. Navigate to Team or Org settings, then find the API keys section. 3. Select the option to create or rotate a Team API Key. 4. Copy the generated key securely to use as the value for the x-vital-api-key header in your requests.

2. Add them to .dlt/secrets.toml

[sources.junction_lab_testing_source] api_key = "your_team_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 Junction Lab Testing 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 junction_lab_testing_pipeline.py

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

Pipeline junction_lab_testing_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset junction_lab_testing_data The duckdb destination used duckdb:/junction_lab_testing.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 /v3/lab_test and /v3/orders from the Junction Lab Testing 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 junction_lab_testing_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.us.junction.com/ (Production US), https://api.eu.junction.com/ (Production EU), https://api.sandbox.us.junction.com/ (Sandbox US), https://api.sandbox.eu.junction.com/ (Sandbox EU)", "auth": {"type": "api_key", "api_key": api_key, "name": "x-vital-api-key", "location": "header"}, }, "resources": [ {"name": "lab_tests", "endpoint": {"path": "v3/lab_test", "data_selector": "data"}}, {"name": "orders", "endpoint": {"path": "v3/orders", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="junction_lab_testing_pipeline", destination="duckdb", dataset_name="junction_lab_testing_data", ) load_info = pipeline.run(junction_lab_testing_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("junction_lab_testing_pipeline").dataset() sessions_df = data.lab_tests.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM junction_lab_testing_data.lab_tests LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("junction_lab_testing_pipeline").dataset() data.lab_tests.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 Junction Lab Testing 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 Junction Lab Testing?

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