Planyo Python API Docs | dltHub

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

Last updated:

Planyo is an API that allows for advanced functions and automation of the Planyo reservation system, such as importing resource data and making automated reservations. The REST API base URL is https://www.planyo.com/rest/ and All requests require an API key for authentication, which is passed as a parameter..

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


What data can I load from Planyo?

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

ResourceEndpointMethodData selectorDescription
list_resources/?method=list_resourcesGETdataReturns resources defined in a Planyo site or meta site along with additional information and photos.
get_resource_info/?method=get_resource_infoGETdataReturns information for a given resource, including photos and resource-specific properties.
list_reservations/?method=list_reservationsGETdataReturns a list of reservations.
list_sites/?method=list_sitesGETdataReturns a list of sites.
get_reservation_products/?method=get_reservation_productsGETdataReturns detailed information about additional products reserved for a given reservation ID.
get_resource_pricing/?method=get_resource_pricingGETdataReturns pricing information for a resource.
get_simplified_daily_pricing/?method=get_simplified_daily_pricingGETdataReturns simplified daily pricing.
list_additional_products/?method=list_additional_productsGETdataReturns a list of additional products.
list_packages/?method=list_packagesGETdataReturns a list of packages.
list_users/?method=list_usersGETdataReturns a list of users.

How do I authenticate with the Planyo API?

Authentication requires an API key to be passed as a parameter in all requests. Stronger security can optionally be achieved using a hash key and timestamp, and all communication must use SSL.

1. Get your credentials

To obtain your API key, log in to your Planyo account and click the 'API Key' button.

2. Add them to .dlt/secrets.toml

[sources.planyo_source] api_key = "your_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 Planyo 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 planyo_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline planyo_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 list_resources and get_resource_info from the Planyo 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 planyo_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://www.planyo.com/rest/", "auth": { "type": "api_key", "api_key": api_key, }, }, "resources": [ {"name": "list_resources", "endpoint": {"path": "?method=list_resources", "data_selector": "data"}}, {"name": "get_resource_info", "endpoint": {"path": "?method=get_resource_info", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="planyo_pipeline", destination="duckdb", dataset_name="planyo_data", ) load_info = pipeline.run(planyo_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("planyo_pipeline").dataset() sessions_df = data.list_resources.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM planyo_data.list_resources LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("planyo_pipeline").dataset() data.list_resources.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 Planyo 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.


Troubleshooting

API Error Codes

The Planyo API returns specific response_code values in case of failure, which can help in troubleshooting:

  • 1: Authentication error (e.g., invalid API key) or invalid method.
  • 3: Invalid input data provided in the request.
  • 4: Other error originating from the method being called.
  • 5: Call rejected due to API overuse (rate limit).
  • 6: A fatal error occurred on the server side.

When encountering these codes, verify your API key, ensure correct input parameters, and check for rate limit adherence.

Ensure that the API key is valid to avoid 401 Unauthorized errors. Also, verify endpoint paths and parameters to avoid 404 Not Found errors.


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 Planyo?

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