Autohost Python API Docs | dltHub
Build a Autohost-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
To retrieve details from a reservation using Autohost's API, use the GET request to the endpoint with your API key. The API is private; contact sales for access. The API documentation is available for integration guidance. The REST API base URL is https://data.autohost.ai/v1 and all requests require an API key sent in the x-api-key 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 pip install "dlt[workspace]" and start loading Autohost data in under 10 minutes.
What data can I load from Autohost?
Here are some of the endpoints you can load from Autohost:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| accounts_me | accounts/me | GET | (single object) | Get the authenticated account (test API key) |
| accounts_children | accounts/children | GET | items | Reseller: list child accounts (paginated object with items array) |
| accounts_keys | accounts/keys | GET | (top-level array) | List API keys for the account |
| listings | listings | GET | items | Search/list listings (response: { total, from, size, count, items }) |
| listing_property_types | listings/propertyTypes | GET | (top-level array) | Static list of supported property types (returns array of strings) |
| listing_details | listings/{id} | GET | (single object) | Get a single listing object by id |
| reservations | reservations | GET | items | Search/list reservations (paginated response with items) |
| reservation_details | reservations/{id} | GET | (single object) | Get reservation details by id |
| reservations_stargate | reservations/{id}/stargate | GET | (top-level array or object per endpoint) | Get reservation messages / stargate messages |
| tenant_evictions_search | tenant-evictions/search | GET | (object) | Search tenant-evictions (lookup results object) |
| tenant_evictions_sources | tenant-evictions/sources | GET | sources | List tenant-eviction sources (response: { sources: [...] }) |
How do I authenticate with the Autohost API?
Autohost uses a single API key for authentication. Include the API key in every request using the HTTP header "x-api-key: YOUR_API_KEY".
1. Get your credentials
- Log in to the Autohost dashboard. 2) Go to Account / API Keys (or Reseller -> API keys for reseller accounts). 3) Create a new API key if none exists (optionally mark as SDK). 4) Copy the key value and store it securely; use it in the x-api-key header for API requests.
2. Add them to .dlt/secrets.toml
[sources.autohost_source] api_key = "your_autohost_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 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 Autohost 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 autohost_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline autohost_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset autohost_data The duckdb destination used duckdb:/autohost.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline autohost_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 listings and reservations from the Autohost 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 autohost_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://data.autohost.ai/v1", "auth": { "type": "api_key", "api_key": api_key, }, }, "resources": [ {"name": "listings", "endpoint": {"path": "listings", "data_selector": "items"}}, {"name": "reservations", "endpoint": {"path": "reservations", "data_selector": "items"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="autohost_pipeline", destination="duckdb", dataset_name="autohost_data", ) load_info = pipeline.run(autohost_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("autohost_pipeline").dataset() sessions_df = data.listings.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM autohost_data.listings LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("autohost_pipeline").dataset() data.listings.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 Autohost data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example 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 Autohost?
Request dlt skills, commands, AGENT.md files, and AI-native context.