Map Your Show Python API Docs | dltHub
Build a Map Your Show-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
Map Your Show provides a REST API for accessing event, exhibitor, and booth data for exhibitors and organizers. The REST API base URL is https://api.mapyourshow.com/mysRest/v2/ and all requests require a Bearer token obtained from an authorization endpoint.
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 Map Your Show data in under 10 minutes.
What data can I load from Map Your Show?
Here are some of the endpoints you can load from Map Your Show:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| exhibitors | Exhibitors/Modified | GET | Retrieves modified exhibitors based on time parameters. | |
| booth_sales_contacts | BoothSales/Contacts/Modified | GET | Retrieves modified booth sales contacts. | |
| orders | Orders/Modified | GET | Retrieves modified orders. | |
| sessions | Sessions/Modified | GET | Retrieves modified sessions. | |
| booth_assignments | Booths/Assignments/Modified | GET | Retrieves modified booth assignments. |
How do I authenticate with the Map Your Show API?
Authentication is a two-step process: first, perform Basic Authentication via the /Authorize endpoint with username, password, and showCode to obtain a token; then, use this token in all subsequent requests by passing it in the 'Authorization' header with the 'Bearer' prefix.
1. Get your credentials
Map Your Show API access is not self-service and cannot be set up through a standard dashboard. You must contact your Map Your Show (MYS) Account Manager directly to request API credentials for your event. You will receive an API-specific username, password, and client ID (also known as a show code), which are distinct from your standard MYS login credentials.
2. Add them to .dlt/secrets.toml
[sources.map_your_show_source] api_username = "your_api_username_here" api_password = "your_api_password_here" client_id = "your_client_id_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 Map Your Show 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 map_your_show_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline map_your_show_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset map_your_show_data The duckdb destination used duckdb:/map_your_show.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 /Authorize and /Exhibitors/Modified from the Map Your Show 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 map_your_show_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.mapyourshow.com/mysRest/v2/", "auth": {"type": "bearer", "token": access_token}, }, "resources": [ {"name": "exhibitors_modified", "endpoint": {"path": "Exhibitors/Modified"}}, {"name": "booth_sales_contacts_modified", "endpoint": {"path": "BoothSales/Contacts/Modified"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="map_your_show_pipeline", destination="duckdb", dataset_name="map_your_show_data", ) load_info = pipeline.run(map_your_show_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("map_your_show_pipeline").dataset() sessions_df = data.exhibitors_modified.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM map_your_show_data.exhibitors_modified LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("map_your_show_pipeline").dataset() data.exhibitors_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 Map Your Show 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 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 Map Your Show?
Request dlt skills, commands, AGENT.md files, and AI-native context.