Cambridge Dictionary Python API Docs | dltHub

Build a Cambridge Dictionary-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.

Last updated:

The Cambridge Dictionary API provides programmatic access to dictionary content, search functionality, and thesaurus data for integration into external applications and websites. The REST API base URL is https://dictionary.cambridge.org/api/v1 and All requests require an 'accessKey' 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 add "dlt[hub]" and start loading Cambridge Dictionary data in under 10 minutes.


What data can I load from Cambridge Dictionary?

Here are some of the endpoints you can load from Cambridge Dictionary:

ResourceEndpointMethodData selectorDescription
dictionariesdictionariesGETRetrieves a list of available dictionaries.
dictionarydictionaries/{dictCode}GETRetrieves information about a specific dictionary.
entriesdictionaries/{dictCode}/entriesGETRetrieves entries for a specific dictionary.
entrydictionaries/{dictCode}/entries/{entryId}GETRetrieves the full entry for a given entryId.
searchdictionaries/{dictCode}/searchGETPerforms a search for a word or phrase.

How do I authenticate with the Cambridge Dictionary API?

Authentication is handled by passing a custom 'accessKey' header with the API key in the request.

1. Get your credentials

To obtain credentials for the Cambridge Dictionary API, you must request access through their official portal. Visit the Cambridge Dictionaries Online API Developer Hub (https://dictionary-api.cambridge.org/) and navigate to the application form (https://dictionary-api.cambridge.org/apply). Complete the data licensing query form with details about your intended use case. Cambridge will review your request and, if approved, provide an API development key via email. Note that the API is a commercial service and is not available for free prototyping or general research; however, they may provide a 30-day evaluation key upon request for testing purposes.

2. Add them to .dlt/secrets.toml

[sources.cambridge_dictionary_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:

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 Cambridge Dictionary 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 cambridge_dictionary_pipeline.py

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

Pipeline cambridge_dictionary_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset cambridge_dictionary_data The duckdb destination used duckdb:/cambridge_dictionary.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 dictionaries and entries from the Cambridge Dictionary 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 cambridge_dictionary_source(accesskey=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://dictionary.cambridge.org/api/v1", "auth": {"type": "api_key", "api_key": accesskey, "name": "accessKey", "location": "header"}, }, "resources": [ {"name": "dictionaries", "endpoint": {"path": "dictionaries"}}, {"name": "entries", "endpoint": {"path": "dictionaries/{dictCode}/entries"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="cambridge_dictionary_pipeline", destination="duckdb", dataset_name="cambridge_dictionary_data", ) load_info = pipeline.run(cambridge_dictionary_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("cambridge_dictionary_pipeline").dataset() sessions_df = data.entries.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM cambridge_dictionary_data.entries LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("cambridge_dictionary_pipeline").dataset() data.entries.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 Cambridge Dictionary data to?

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

DestinationExample 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 Cambridge Dictionary?

Request dlt skills, commands, AGENT.md files, and AI-native context.

Available Pipelines