Docplanner Python API Docs | dltHub

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

Last updated:

Docplanner Integrations API provides RESTful access to integrate medical software with the Docplanner platform. The REST API base URL is https://www.docplanner.com/api/v3/integration and all requests require an OAuth2 Bearer token in the Authorization 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 Docplanner data in under 10 minutes.


What data can I load from Docplanner?

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

ResourceEndpointMethodData selectorDescription
facilities/facilitiesGET_itemsList all facilities
facility/facilities/{facility_id}GETRetrieve a single facility
doctors/facilities/{facility_id}/doctorsGET_itemsList doctors for a facility
doctor/facilities/{facility_id}/doctors/{doctor_id}GETRetrieve a specific doctor
addresses/facilities/{facility_id}/doctors/{doctor_id}/addressesGET_itemsList addresses for a doctor
address/facilities/{facility_id}/doctors/{doctor_id}/addresses/{address_id}GETRetrieve a specific address
services/servicesGET_itemsList all services
address_services/facilities/{facility_id}/doctors/{doctor_id}/addresses/{address_id}/servicesGET_itemsServices available at an address
slots/facilities/{facility_id}/doctors/{doctor_id}/addresses/{address_id}/slotsGET_itemsAvailable appointment slots
bookings/facilities/{facility_id}/doctors/{doctor_id}/addresses/{address_id}/bookingsGET_itemsBookings for a doctor/address
calendar_breaks/facilities/{facility_id}/doctors/{doctor_id}/addresses/{address_id}/breaksGET_itemsCalendar break periods

How do I authenticate with the Docplanner API?

Docplanner uses the OAuth 2.0 Client Credentials flow. After requesting a token from the /oauth/v2/token endpoint using client_id and client_secret, it must be included in the 'Authorization' header of every request as a 'Bearer' token.

1. Get your credentials

Docplanner credentials are not self-service and require an integration partnership. To obtain them: 1. Visit the Integrations Guide at https://integrations.docplanner.com/guide/integration-process.html. 2. If you are a medical software provider, fill out the contact form on the homepage or email integrations@docplanner.com to request access to the sandbox environment. 3. For production credentials, follow the project plan guided by a Docplanner specialist, which may involve getting approval from the target clinic. If you manage the integration yourself, email integrations@docplanner.com and CC the clinic representative to request credentials.

2. Add them to .dlt/secrets.toml

[sources.docplanner_source] access_token = "REPLACE_ME"

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 Docplanner 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 docplanner_pipeline.py

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

Pipeline docplanner_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset docplanner_data The duckdb destination used duckdb:/docplanner.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 facilities and doctors from the Docplanner 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 docplanner_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://www.docplanner.com/api/v3/integration", "auth": {"type": "bearer", "token": access_token}, }, "resources": [ {"name": "facilities", "endpoint": {"path": "facilities", "data_selector": "_items"}}, {"name": "doctors", "endpoint": {"path": "facilities/{facility_id}/doctors", "data_selector": "_items"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="docplanner_pipeline", destination="duckdb", dataset_name="docplanner_data", ) load_info = pipeline.run(docplanner_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("docplanner_pipeline").dataset() sessions_df = data.facilities.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM docplanner_data.facilities LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("docplanner_pipeline").dataset() data.facilities.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 Docplanner 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 Docplanner?

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