Wondercraftai Python API Docs | dltHub

Wondercraftai is an API platform for programmatically generating audio content (podcasts, ads, meditations, audiobooks) using AI-driven script generation and voice synthesis. The REST API base URL is https://api.wondercraft.ai/v1 and All requests require an API key sent in the X-API-KEY 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 pip install "dlt[workspace]" and start loading Wondercraftai data in under 10 minutes.

---

What data can I load from Wondercraftai?

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

---

How do I authenticate with the Wondercraftai API?

Authentication uses an API key sent in the X-API-KEY header on every request.

1. Get your credentials

1. Log in to Wondercraft Studio (https://wondercraft.ai/studio).\n2) Open the workspace selector (top‑left) and choose Workspace Settings.\n3) Navigate to API keys and create a new API key (requires a paid plan).\n4) Copy the generated key and use it in the X-API-KEY request header.

2. Add them to .dlt/secrets.toml

Copy
[sources.wondercraftai_source]
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:

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 Wondercraftai 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 wondercraftai_pipeline.py

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

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

Inspect your pipeline and data:

Copy
dlt pipeline wondercraftai_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 podcast and podcast_status from the Wondercraftai 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 wondercraftai_source(api_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.wondercraft.ai/v1",
            "auth": {
                "type": "api_key",
                "api_key": api_key,
            },
        },
        "resources": [
            {"name": "podcast", "endpoint": {"path": "podcast", "data_selector": "job_id"}},
            {"name": "podcast_status", "endpoint": {"path": "podcast/{job_id}"}}
        ],
    }
    yield from rest_api_resources(config)


def get_data() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="wondercraftai_pipeline",
        destination="duckdb",
        dataset_name="wondercraftai_data",
    )
    load_info = pipeline.run(wondercraftai_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("wondercraftai_pipeline").dataset()
sessions_df = data.podcast.df()
print(sessions_df.head())

SQL (DuckDB example):

Copy
SELECT * FROM wondercraftai_data.podcast LIMIT 10;

In a marimo or Jupyter notebook:

Copy
import dlt

data = dlt.pipeline("wondercraftai_pipeline").dataset()
data.podcast.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 Wondercraftai 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/403 or missing‑key errors, verify the X-API-KEY header is present and the key is valid. API keys require a paid plan and must be created in Workspace Settings > API keys.

Rate limits / concurrent jobs

The API limits concurrent jobs to 5 in flight per account; exceeding this returns 429. Backoff and retry when receiving 429.

Validation and input errors

Endpoints may return 422 for validation errors and 400 for invalid voice_id or music_id values. Ensure voice_ids are unique where required and that convo‑mode AI‑scripted requires exactly 2 voice_ids.

Common error responses referenced in docs: 200 (success), 400 (bad request / invalid ids), 422 (validation error), 429 (too many concurrent jobs).

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