STiX Cloud Ticketing Python API Docs | dltHub
Build a STiX Cloud Ticketing-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
STiX Cloud is a ticketing and event booking platform exposing a REST API for event discovery, seat selection, and transaction management. The REST API base URL is https://api.stixcloud.com/api/v0/{tenant} and All requests require an OAuth 2.0 Bearer token obtained via a client credentials grant..
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 STiX Cloud Ticketing data in under 10 minutes.
What data can I load from STiX Cloud Ticketing?
Here are some of the endpoints you can load from STiX Cloud Ticketing:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| events | {tenant}/icc/{icc}/products | GET | content | Get events / show timings for an Internet Content Code |
| event_showtimes | {tenant}/products/{productId}/showdates | GET | content | Get event show date & time |
| seatmap_overview | {tenant}/products/{productId}/seatmap/overview | GET | Retrieve overview seat map for a product | |
| seat_section_availability | {tenant}/products/{productId}/seatmap/availability | GET | Get availability per seat section | |
| ticket_types | {tenant}/products/{productId}/tickettype | GET | Retrieve ticket pricing / price classes | |
| patron_transactions | {tenant}/patrons/account/transactions | GET | content | Patron transaction history (paginated) |
How do I authenticate with the STiX Cloud Ticketing API?
The API uses OAuth 2.0 with a client credentials grant to obtain an access token. This token must be included in the Authorization header of all subsequent requests in the format 'Authorization: Bearer <access_token>'.
1. Get your credentials
- Contact STiX Cloud or your SISTIC account manager to request access to the STiX Cloud Ticketing API and provision a tenant. 2. Request that they generate your OAuth 2.0 credentials, specifically your client_id and client_secret. 3. Obtain your unique tenant code from the account manager, which is required for all API paths.
2. Add them to .dlt/secrets.toml
[sources.stix_cloud_ticketing_source] client_id = "your_client_id" client_secret = "your_client_secret" tenant = "your_tenant_code"
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 STiX Cloud Ticketing 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 stix_cloud_ticketing_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline stix_cloud_ticketing_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset stix_cloud_ticketing_data The duckdb destination used duckdb:/stix_cloud_ticketing.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 oauth/token and api/v0/{tenant}/ from the STiX Cloud Ticketing 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 stix_cloud_ticketing_source(client_credentials=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.stixcloud.com/api/v0/{tenant}", "auth": {"type": "bearer", "token": client_credentials}, }, "resources": [ {"name": "events", "endpoint": {"path": "{tenant}/icc/{icc}/products", "data_selector": "content"}}, {"name": "patron_transactions", "endpoint": {"path": "{tenant}/patrons/account/transactions", "data_selector": "content"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="stix_cloud_ticketing_pipeline", destination="duckdb", dataset_name="stix_cloud_ticketing_data", ) load_info = pipeline.run(stix_cloud_ticketing_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("stix_cloud_ticketing_pipeline").dataset() sessions_df = data.patron_transactions.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM stix_cloud_ticketing_data.patron_transactions LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("stix_cloud_ticketing_pipeline").dataset() data.patron_transactions.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 STiX Cloud Ticketing 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 STiX Cloud Ticketing?
Request dlt skills, commands, AGENT.md files, and AI-native context.