Reed Python API Docs | dltHub
Build a Reed-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Reed API is a platform that allows developers to access job listings and search functionalities from the Reed.co.uk website. The REST API base URL is https://www.reed.co.uk/api/1.0 and All requests to the Jobseeker API require basic authentication using an API key as the username..
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 Reed data in under 10 minutes.
What data can I load from Reed?
Here are some of the endpoints you can load from Reed:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| jobs | /jobs/{Job Id} | GET | Retrieves details for a specific job by ID. | |
| search | /search | GET | results | Searches for jobs based on keywords, location, employer, and distance. |
How do I authenticate with the Reed API?
The Reed Jobseeker API uses basic authentication. You must include your API key as the username in the basic authentication HTTP header, leaving the password empty.
1. Get your credentials
To obtain API credentials, you will need to create an account on Reed.co.uk and acquire an API key. Specific step-by-step instructions for obtaining the key from a dashboard are not provided in the available documentation.
2. Add them to .dlt/secrets.toml
[sources.reed_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 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 Reed 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 reed_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline reed_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset reed_data The duckdb destination used duckdb:/reed.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline reed_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 search and jobs from the Reed 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 reed_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://www.reed.co.uk/api/1.0", "auth": { "type": "http_basic", "username": api_key, }, }, "resources": [ {"name": "search", "endpoint": {"path": "search", "data_selector": "results"}}, {"name": "jobs", "endpoint": {"path": "jobs/{job_id}"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="reed_pipeline", destination="duckdb", dataset_name="reed_data", ) load_info = pipeline.run(reed_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("reed_pipeline").dataset() sessions_df = data.search.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM reed_data.search LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("reed_pipeline").dataset() data.search.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 Reed 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
Empty Search Results
If no jobs match the search parameters provided to the /search endpoint, the API will return an empty list.
Multiple Location Matches
If a search query results in more than one location match, these multiple matches will also be returned in the response.
Authentication Failures
Requests to the Jobseeker API require basic authentication with your API key as the username and an empty password. Incorrect or missing authentication credentials will result in failed requests.
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 Reed?
Request dlt skills, commands, AGENT.md files, and AI-native context.