Explara Python API Docs | dltHub

Explara is an event management, ticketing and booking platform exposing REST APIs to create/manage events, tickets, bookings and retrieve reports/attendees. The REST API base URL is https://www.explara.com and All requests require an OAuth2 access token (Bearer) for authentication..

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

---

What data can I load from Explara?

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

---

How do I authenticate with the Explara API?

Explara uses OAuth2. Obtain an access token (user or app flow) and include header Authorization: Bearer YOUR_ACCESS_TOKEN_HERE on all API calls over HTTPS.

1. Get your credentials

1. Sign in to your Explara account (https://www.explara.com/a/login).
2. Go to 'API & Developers' in your account dashboard.
3. For User Access, copy the User Access Token shown.
4. For App Access, register a new application to receive client_id and client_secret.
5. Use the OAuth2 authorization code flow: send the user to https://www.explara.com/a/account/oauth/authorize?response_type=code&client_id=YOUR_CLIENT_ID&state=xyz, obtain the code and POST to https://www.explara.com/a/account/oauth/token with client_id, client_secret, grant_type=authorization_code, and code to obtain an access token.

2. Add them to .dlt/secrets.toml

Copy
[sources.explara_source]
api_key = "your_access_token_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:

Copy
uv venv && source .venv/bin/activate
uv pip install "dlt[workspace]"

1. Install the dlt AI Workbench:

Copy
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:

Copy
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 Explara 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:

Copy
python explara_pipeline.py

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

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

Inspect your pipeline and data:

Copy
dlt pipeline explara_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 events and tickets from the Explara API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def explara_source(api_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://www.explara.com",
            "auth": {
                "type": "bearer",
                "token": api_key,
            },
        },
        "resources": [
            {"name": "events", "endpoint": {"path": "api/e/get-all-events", "data_selector": "events"}},
            {"name": "tickets", "endpoint": {"path": "api/e/get-tickets", "data_selector": "tickets"}}
        ],
    }
    yield from rest_api_resources(config)


def get_data() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="explara_pipeline",
        destination="duckdb",
        dataset_name="explara_data",
    )
    load_info = pipeline.run(explara_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):

Copy
import dlt

data = dlt.pipeline("explara_pipeline").dataset()
sessions_df = data.events.df()
print(sessions_df.head())

SQL (DuckDB example):

Copy
SELECT * FROM explara_data.events LIMIT 10;

In a marimo or Jupyter notebook:

Copy
import dlt

data = dlt.pipeline("explara_pipeline").dataset()
data.events.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 Explara data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.

---

Troubleshooting

Authentication failures

If you receive 401 or errors referencing invalid API key (E001/E008), verify you are sending Authorization: Bearer <access_token> over HTTPS and that the token has not expired (tokens are valid ~3 months). For app flows ensure you exchanged the authorization code at https://www.explara.com/a/account/oauth/token with correct client_id and client_secret.

Pagination & attendee limits

Attendee list endpoints limit requests to 50 records per call; use fromRecord and toRecord query/form parameters to page (e.g., fromRecord=0,toRecord=50 then 51‑100). Large range requests may be rejected.

Rate limiting & bot detection

If you receive error code E023 or messages about too many requests, slow down request rate and implement exponential backoff. Some endpoints may return T005/T006 when the system is busy; retry later.

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.

Copy
dlt ai toolkit data-exploration install
dlt ai toolkit dlthub-runtime install

• How to deploy a pipeline
• How to explore your data in marimo Notebooks
• How to query your data in Python with dataset
• Join the dlt community on Slack