Load Map Your Show data to DuckDB

Map Your Show provides a REST API for accessing event, exhibitor, and booth data for exhibitors and organizers. Everything needed to build a working Map Your Show → DuckDB pipeline is on this page: the API's base URL, authentication, endpoints, pagination and incremental field — plus a prompt that hands the whole job to your coding agent.

---

Build your Map Your Show to DuckDB pipeline

Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.

PromptCopy prompt
Run uvx dlthub-init@latest to build a pipeline from Map Your Show to DuckDB and run it on dltHub

That scaffolds a dltHub workspace and installs the dltHub AI harness — the project rules, the secrets-management skill, and the dlt MCP server your agent needs to work safely. From there it reads the Map Your Show API, proposes the endpoints to load, then writes, runs and validates the pipeline while you review rather than type. Credentials are inspected through MCP tools, so your agent never reads secrets.toml itself. How the LLM-native workflow works →

Prefer to write it yourself? Every fact the agent uses is below.

---

Map Your Show API at a glance

These values come from the Map Your Show API reference — the authoritative source if anything here looks out of date.

---

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

Copy
[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 file automatically at runtime. With the harness, the setup-secrets skill prompts you for the values and never handles the raw credential in chat. For production, see setting up credentials with dlt.

---

What Map Your Show data can I load into DuckDB?

These are the Map Your Show endpoints dlt can load into DuckDB:

---

How do I load only new Map Your Show records?

Map Your Show exposes updated_at on Exhibitors/Modified, so dlt can request only the records that changed since the last run. Set it as the cursor_path and dlt tracks the high-water mark for you between runs.

Copy
{"name": "exhibitors_modified", "endpoint": {
    "path": "Exhibitors/Modified",
    "incremental": {"cursor_path": "updated_at", "initial_value": "2024-01-01T00:00:00Z"},
}}

On the first run dlt loads everything from initial_value; on every run after that it requests only what changed and appends with write_disposition="merge" if you set a primary key. See incremental loading.

---

What does the generated Map Your Show pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading /Authorize and /Exhibitors/Modified from the Map Your Show API into DuckDB:

Copy
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 load_map_your_show_to_duckdb() -> 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)


if __name__ == "__main__":
    load_map_your_show_to_duckdb()

Run it with python map_your_show_pipeline.py. The agent iterates on this until it loads cleanly — you review and approve, rather than write it from scratch.

---

How do I query Map Your Show data in DuckDB?

dlt creates one table per resource. Query the loaded data with Python or SQL — or ask your agent to, through the MCP server's execute_sql_query tool.

Python (pandas DataFrame):

Copy
import dlt

data = dlt.pipeline("map_your_show_pipeline").dataset()
df = data.exhibitors_modified.df()
print(df.head())

SQL:

Copy
SELECT * FROM map_your_show_data.exhibitors_modified LIMIT 10;

See querying your data with dataset and exploring it in marimo notebooks.

---

How do I deploy the Map Your Show to DuckDB pipeline in production?

The pipeline runs locally, which is ideal for prototyping and one-off analysis. When you need it on a schedule, monitored on every load, and shared with your team, deploy the same dlt code on the dltHub platform — no infrastructure to maintain. The prompt above already ends with "run it on dltHub", so your agent can take it there directly.

• Deploy & schedule — run the pipeline as a managed job with automatic retries.
• Monitor — observable job queues, alerting, and load metrics for every run.
• Transform — promote raw Map Your Show loads into governed, documented models.
• Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.

Book a demo →

---

What other destinations can I load Map Your Show data to?

dlt loads into any of these — only the destination argument changes:

Set dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. On the dltHub platform the same pipeline runs against a managed Iceberg lakehouse. See the full destinations list.

---

Next steps

• Ready for production? Book a demo of the dltHub platform →
• dlt LLM-native workflow docs
• REST API source reference
• Join the dlt community on Slack