Wellcome Collection Python API Docs | dltHub
Build a Wellcome Collection-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Wellcome Collection API is a platform that provides access to works, images, and concepts from the Wellcome Collection. The REST API base URL is https://api.wellcomecollection.org/catalogue/v2 and No authentication is required for requests to the Wellcome Collection API..
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 Wellcome Collection data in under 10 minutes.
What data can I load from Wellcome Collection?
Here are some of the endpoints you can load from Wellcome Collection:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| works | /works | GET | results | Returns a paginated list of works |
| work | /works/{id} | GET | Returns a single work by ID | |
| images | /images | GET | results | Returns a paginated list of images |
| image | /images/{id} | GET | Returns a single image by ID | |
| concepts | /concepts | GET | results | Returns a paginated list of concepts |
| concept | /concepts/{id} | GET | Returns a single concept by ID |
How do I authenticate with the Wellcome Collection API?
The Wellcome Collection API does not require any authentication or sign-up to access its resources.
1. Get your credentials
No credentials are required as the Wellcome Collection API does not require authentication.
2. Add them to .dlt/secrets.toml
[sources.wellcome_collection_source]
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 venv && source .venv/bin/activate uv pip install "dlt[workspace]"
1. Install the dlt AI Workbench:
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:
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 Wellcome Collection 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:
python wellcome_collection_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline wellcome_collection_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset wellcome_collection_data The duckdb destination used duckdb:/wellcome_collection.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline wellcome_collection_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 works and images from the Wellcome Collection 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 wellcome_collection_source(=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.wellcomecollection.org/catalogue/v2", "auth": { "type": "None", "": , }, }, "resources": [ {"name": "works", "endpoint": {"path": "works", "data_selector": "results"}}, {"name": "images", "endpoint": {"path": "images", "data_selector": "results"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="wellcome_collection_pipeline", destination="duckdb", dataset_name="wellcome_collection_data", ) load_info = pipeline.run(wellcome_collection_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("wellcome_collection_pipeline").dataset() sessions_df = data.works.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM wellcome_collection_data.works LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("wellcome_collection_pipeline").dataset() data.works.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 Wellcome Collection 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.
Troubleshooting
Licensing Restrictions
Some content accessed via the Wellcome Collection API may have licensing restrictions. Users should review the licensing information associated with specific works or images to ensure compliance. Failure to adhere to these restrictions could lead to issues with data usage.
Pagination
The API returns paginated lists for endpoints like /works, /images, and /concepts. Ensure that your implementation correctly handles pagination to retrieve all available records, as incomplete pagination handling can lead to missing data.
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.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install
Was this page helpful?
Community Hub
Need more dlt context for Wellcome Collection?
Request dlt skills, commands, AGENT.md files, and AI-native context.