OneUptime Python API Docs | dltHub

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

Last updated:

The OneUptime API reference for Scheduled Maintenance Note Template documents the completion of maintenance activities with a structured format. It includes details on posting scheduled maintenance events via the API. The template is part of OneUptime's broader API documentation. The REST API base URL is https://oneuptime.com/api and All requests require an ApiKey header with your API key..

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


What data can I load from OneUptime?

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

ResourceEndpointMethodData selectorDescription
status_page_resource/api/status-page-resource/get-listGETRetrieve a paginated list of status page resources.
status_page_resource_item/api/status-page-resource/:id/get-itemGETRetrieve a single status page resource by ID.
scheduled_maintenance/api/scheduled-maintenance/get-listGETList scheduled maintenance events.
scheduled_maintenance_item/api/scheduled-maintenance/:id/get-itemGETGet details of a specific scheduled maintenance event.
scheduled_maintenance_note_template/api/scheduled-maintenance-note-template/get-listGETList note templates for scheduled maintenance.
scheduled_maintenance_note_template_item/api/scheduled-maintenance-note-template/:id/get-itemGETRetrieve a specific note template by ID.

How do I authenticate with the OneUptime API?

Include an "ApiKey" header with the value of your OneUptime API key on every request.

1. Get your credentials

  1. Log into your OneUptime account.
  2. Navigate to the Settings or Account section.
  3. Find the "API Keys" or "Integrations" tab.
  4. Click "Create New API Key" (if none exists) and give it a label.
  5. Copy the generated key; you will use it as the value for the ApiKey header.

2. Add them to .dlt/secrets.toml

[sources.oneuptime_source] api_key = "YOUR_API_KEY"

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

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

dlt 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 OneUptime 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 oneuptime_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline oneuptime_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 status_page_resource and scheduled_maintenance from the OneUptime 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 oneuptime_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://oneuptime.com/api", "auth": { "type": "api_key", "api_key": api_key, }, }, "resources": [ {"name": "status_page_resource", "endpoint": {"path": "status-page-resource/get-list"}}, {"name": "scheduled_maintenance", "endpoint": {"path": "scheduled-maintenance/get-list"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="oneuptime_pipeline", destination="duckdb", dataset_name="oneuptime_data", ) load_info = pipeline.run(oneuptime_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("oneuptime_pipeline").dataset() sessions_df = data.status_page_resource.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM oneuptime_data.status_page_resource LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("oneuptime_pipeline").dataset() data.status_page_resource.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 OneUptime 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 Workbench:

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-runtime — Deploy, schedule, and monitor your pipeline in production.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install

Was this page helpful?

Community Hub

Need more dlt context for OneUptime?

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