Load World Bank Indicators API data to DuckDB
Build a World Bank Indicators API to DuckDB pipeline with your coding agent. One prompt scaffolds it with the dltHub AI harness, plus the World Bank Indicators API API base URL, auth, endpoints, and incremental loading.
The World Bank Indicators API provides programmatic access to over 45 databases and nearly 16,000 time series indicators. Everything needed to build a working World Bank Indicators API → 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 World Bank Indicators API to DuckDB pipeline
Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.
PromptRunuvx dlthub-init@latestto build a pipeline from World Bank Indicators API 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 World Bank Indicators API 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.
World Bank Indicators API API at a glance
| Base URL | https://api.worldbank.org/v2 |
| Example endpoint | GET v2/indicator |
| Records found at | 1 |
| Authentication | no authentication required for public data access — sent in the request header |
| Pagination | Page-number via page, page size via per_page (default 50, max 1000). World Bank Indicators API (v2) uses a page number (query param page) and a results-per-page parameter (query param per_page). Responses include pagination metadata fields page/pages/per_page/total. Documentation excerpts provided show page numbers and per_page defaults, but no explicit max per_page; a third-party schema lists per_page maximum 1000. |
| API reference | https://datahelpdesk.worldbank.org/knowledgebase/articles/889392 |
These values come from the World Bank Indicators API API reference — the authoritative source if anything here looks out of date.
How do I authenticate with the World Bank Indicators API API?
The World Bank Indicators API does not require any authentication; public data access is unrestricted.
No credentials required. The World Bank Indicators API API is public, so there is nothing to obtain and nothing to add to .dlt/secrets.toml — the pipeline above runs as written.
What World Bank Indicators API data can I load into DuckDB?
These are the World Bank Indicators API endpoints dlt can load into DuckDB:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| countries | v2/country | GET | 1 | List of countries and regions |
| indicators | v2/indicator | GET | 1 | List of available data indicators |
| topics | v2/topic | GET | 1 | List of data topics |
| sources | v2/sources | GET | 1 | List of available data sources |
| languages | v2/languages | GET | 1 | List of supported languages |
How do I load only new World Bank Indicators API records?
The World Bank Indicators API 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": "indicators", "endpoint": { "path": "v2/indicator", # 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 World Bank Indicators API pipeline look like?
A standard dlt REST API pipeline — the same code you would write by hand, loading indicator and sources from the World Bank Indicators API API into DuckDB:
import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def world_bank_indicators_api_source(): config: RESTAPIConfig = { "client": { "base_url": "https://api.worldbank.org/v2", }, "resources": [ {"name": "indicators", "endpoint": {"path": "v2/indicator", "data_selector": "1"}}, {"name": "countries", "endpoint": {"path": "v2/country", "data_selector": "1"}} ], } yield from rest_api_resources(config) def load_world_bank_indicators_api_to_duckdb() -> None: pipeline = dlt.pipeline( pipeline_name="world_bank_indicators_api_pipeline", destination="duckdb", dataset_name="world_bank_indicators_api_data", ) load_info = pipeline.run(world_bank_indicators_api_source()) print(load_info) if __name__ == "__main__": load_world_bank_indicators_api_to_duckdb()
Run it with python world_bank_indicators_api_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 World Bank Indicators API 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("world_bank_indicators_api_pipeline").dataset() df = data.indicator.df() print(df.head())
SQL:
SELECT * FROM world_bank_indicators_api_data.indicator LIMIT 10;
See querying your data with dataset and exploring it in marimo notebooks.
How do I deploy the World Bank Indicators API 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 World Bank Indicators API 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 World Bank Indicators API 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 World Bank Indicators API to DuckDB?
Request dlt skills, commands, AGENT.md files, and AI-native context.