Load Adzuna data to DuckDB
Build a Adzuna to DuckDB pipeline with your coding agent. One prompt scaffolds it with the dltHub AI harness, plus the Adzuna API base URL, auth, endpoints, and incremental loading.
Adzuna is a job search engine API providing programmatic access to job advertisement listings and employment market data. Everything needed to build a working Adzuna → DuckDB pipeline is on this page: the API's base URL, authentication, endpoints, pagination and incremental field — plus a prompt that hands the whole job to your coding agent.
Build your Adzuna to DuckDB pipeline
Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.
PromptRunuvx dlthub-init@latestto build a pipeline from Adzuna to DuckDB and run it on dltHub
That scaffolds a dltHub workspace and installs the dltHub AI harness — the project rules, the secrets-management skill, and the dlt MCP server your agent needs to work safely. From there it reads the Adzuna API, proposes the endpoints to load, then writes, runs and validates the pipeline while you review rather than type. Credentials are inspected through MCP tools, so your agent never reads secrets.toml itself. How the LLM-native workflow works →
Prefer to write it yourself? Every fact the agent uses is below.
Adzuna API at a glance
| Base URL | https://api.adzuna.com/v1/api |
| Example endpoint | GET jobs/gb/search/1 |
| Records found at | results |
| Authentication | all requests require app_id and app_key as query parameters — sent in the Authorization header, prefixed Api-Key |
| Pagination | Page-number page size via results_per_page |
| API reference | https://developer.intelligence.adzuna.com/doc-592758 |
These values come from the Adzuna API reference — the authoritative source if anything here looks out of date.
How do I authenticate with the Adzuna API?
All requests require the 'app_id' and 'app_key' parameters passed as query parameters in the URL.
1. Get your credentials
- Navigate to the Adzuna developer signup page (https://developer.adzuna.com/signup) to register for a developer account. 2. Once registered, log in to the Adzuna Developer Portal. 3. After successful login, you will be directed to your Adzuna Developer Dashboard. 4. Within the dashboard, follow the steps to create a new application by providing a name and description. 5. Upon creation, the platform will generate and display your unique 'Application ID' (app_id) and 'Application Key' (app_key). Keep these credentials secure.
2. Add them to .dlt/secrets.toml
[sources.adzuna_source] app_id, app_key = "REPLACE_ME"
dlt reads this file automatically at runtime. With the harness, the setup-secrets skill prompts you for the values and never handles the raw credential in chat. For production, see setting up credentials with dlt.
What Adzuna data can I load into DuckDB?
These are the Adzuna endpoints dlt can load into DuckDB:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| jobs_search | jobs/{country}/search/{page} | GET | results | Retrieve job advertisement listings |
| salary_histogram | jobs/{country}/histograms | GET | Get salary distribution histograms | |
| salary_averages | jobs/{country}/salary | GET | Get salary data for job titles and locations | |
| vacancies_trends | jobs/{country}/vacancies | GET | Get latest vacancy trends | |
| location_search | jobs/{country}/geodata | GET | Retrieve location-specific data |
How do I load only new Adzuna records?
The Adzuna API reference does not document a timestamp or sequence field for these endpoints, so there is nothing to advertise here as verified. Pick a field from the endpoints table above that increases with every write, then set it as the cursor_path.
{"name": "jobs_search", "endpoint": { "path": "jobs/gb/search/1", # Replace with a field that increases on every write. "incremental": {"cursor_path": "REPLACE_ME", "initial_value": "2024-01-01T00:00:00Z"}, }}
On the first run dlt loads everything from initial_value; on every run after that it requests only what changed and appends with write_disposition="merge" if you set a primary key. See incremental loading.
What does the generated Adzuna pipeline look like?
A standard dlt REST API pipeline — the same code you would write by hand, loading jobs/search and salaries from the Adzuna API into DuckDB:
import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def adzuna_source(app_id_app_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.adzuna.com/v1/api", "auth": {"type": "api_key", "api_key": app_id_app_key, "name": "Authorization", "location": "header"}, }, "resources": [ {"name": "jobs_search", "endpoint": {"path": "jobs/gb/search/1", "data_selector": "results"}}, {"name": "salary_histogram", "endpoint": {"path": "jobs/gb/histograms"}} ], } yield from rest_api_resources(config) def load_adzuna_to_duckdb() -> None: pipeline = dlt.pipeline( pipeline_name="adzuna_pipeline", destination="duckdb", dataset_name="adzuna_data", ) load_info = pipeline.run(adzuna_source()) print(load_info) if __name__ == "__main__": load_adzuna_to_duckdb()
Run it with python adzuna_pipeline.py. The agent iterates on this until it loads cleanly — you review and approve, rather than write it from scratch.
How do I query Adzuna data in DuckDB?
dlt creates one table per resource. Query the loaded data with Python or SQL — or ask your agent to, through the MCP server's execute_sql_query tool.
Python (pandas DataFrame):
import dlt data = dlt.pipeline("adzuna_pipeline").dataset() df = data.jobs_search.df() print(df.head())
SQL:
SELECT * FROM adzuna_data.jobs_search LIMIT 10;
See querying your data with dataset and exploring it in marimo notebooks.
How do I deploy the Adzuna to DuckDB pipeline in production?
The pipeline runs locally, which is ideal for prototyping and one-off analysis. When you need it on a schedule, monitored on every load, and shared with your team, deploy the same dlt code on the dltHub platform — no infrastructure to maintain. The prompt above already ends with "run it on dltHub", so your agent can take it there directly.
- Deploy & schedule — run the pipeline as a managed job with automatic retries.
- Monitor — observable job queues, alerting, and load metrics for every run.
- Transform — promote raw Adzuna loads into governed, documented models.
- Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.
What other destinations can I load Adzuna data to?
dlt loads into any of these — only the destination argument changes:
| Destination | Example value |
|---|---|
| PostgreSQL | "postgres" |
| BigQuery | "bigquery" |
| Snowflake | "snowflake" |
| Redshift | "redshift" |
| Databricks | "databricks" |
| Filesystem (S3, GCS, Azure) | "filesystem" |
Set dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. On the dltHub platform the same pipeline runs against a managed Iceberg lakehouse. See the full destinations list.
Next steps
Was this page helpful?
Community Hub
Need more dlt context for Adzuna to DuckDB?
Request dlt skills, commands, AGENT.md files, and AI-native context.