Viator Python API Docs | dltHub

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

Last updated:

Viator Partner API allows developers to search, retrieve product details, and manage bookings for travel experiences and tours. The REST API base URL is https://api.viator.com/partner and all requests require an 'exp-api-key' header and an 'Accept' version 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 Viator data in under 10 minutes.


What data can I load from Viator?

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

ResourceEndpointMethodData selectorDescription
products_modifiedproducts/modified-sinceGETproductsRetrieve all products modified since a specific point in time using a cursor.
availability_modifiedavailability/schedules/modified-sinceGETdataRetrieve all availability schedules modified since a specific point in time using a cursor.
bookings_modifiedbookings/modified-sinceGETbookingsRetrieve all booking-event notifications since a point in time or using a cursor.
taxonomy_destinationstaxonomy/destinationsGETdataRetrieves a list of destination names, types and unique identifiers.
taxonomy_categoriestaxonomy/categoriesGETdataRetrieves a list of product categories for a destination.

How do I authenticate with the Viator API?

Access is managed via an API key passed in the 'exp-api-key' header. Additionally, an 'Accept' header specifying the API version (e.g., 'application/json;version=2.0') is mandatory.

1. Get your credentials

To obtain your Viator API credentials, log in to your partner account dashboard and navigate to Tools -> Affiliate API -> Start your development. You will be required to verify your email address to generate your unique API key. For higher access levels (Full or Full+Booking), request authorization directly through your account dashboard or contact your business development account manager.

2. Add them to .dlt/secrets.toml

[sources.viator_source] exp_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 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 Viator 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 viator_pipeline.py

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

Pipeline viator_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset viator_data The duckdb destination used duckdb:/viator.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 /partner/products/search and /bookings/cancel from the Viator 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 viator_source(exp_api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.viator.com/partner", "auth": {"type": "api_key", "api_key": exp_api_key, "name": "exp-api-key", "location": "header"}, }, "resources": [ {"name": "products_modified", "endpoint": {"path": "products/modified-since", "data_selector": "products"}}, {"name": "bookings_modified", "endpoint": {"path": "bookings/modified-since", "data_selector": "bookings"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="viator_pipeline", destination="duckdb", dataset_name="viator_data", ) load_info = pipeline.run(viator_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("viator_pipeline").dataset() sessions_df = data.products_modified.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM viator_data.products_modified LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("viator_pipeline").dataset() data.products_modified.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 Viator 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 Viator?

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