MediaWiki Python API Docs | dltHub
Build a MediaWiki-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
MediaWiki REST API is a modern HTTP API for reading and writing wiki content with support for searching, page history, and transformations. The REST API base URL is https://{{wiki-host}}/w/rest.php/v1/ and supports OAuth 2.0 via Bearer token or session-based cookies with CSRF tokens for write requests.
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 MediaWiki data in under 10 minutes.
What data can I load from MediaWiki?
Here are some of the endpoints you can load from MediaWiki:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| search_page | /search/page | GET | pages | Searches wiki page titles and contents for search terms. |
| search_title | /search/title | GET | pages | Autocompletes wiki page titles. |
| get_page | /page/{title} | GET | Retrieves content of a wiki page. | |
| get_page_with_html | /page/{title}/with_html | GET | Retrieves content of a wiki page as HTML. | |
| get_page_history | /page/{title}/history | GET | Retrieves the edit history of a page. |
How do I authenticate with the MediaWiki API?
Authentication for third-party or server-side clients is performed by including an OAuth access token in the Authorization header using the Bearer scheme. For session-based cookie authentication, a CSRF token must be provided in the request body for write operations.
1. Get your credentials
To obtain API credentials for the MediaWiki REST API (via the OAuth extension), follow these steps: 1. Navigate to the Special
page on your target MediaWiki installation. 2. Register your consumer application by providing the required details. 3. Upon registration, you will be issued a consumer key (client ID) and a consumer secret (client secret). 4. For user-specific authorization, direct users through the standard OAuth flow (initiate request, authorize application, and exchange the authorization code for an access token). Store these credentials securely.2. Add them to .dlt/secrets.toml
[sources.mediawiki_source] client_id = "your_client_id_here" client_secret = "your_client_secret_here" access_token = "your_access_token_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 MediaWiki 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 mediawiki_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline mediawiki_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset mediawiki_data The duckdb destination used duckdb:/mediawiki.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 /page/{title} and /search/page from the MediaWiki 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 mediawiki_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://{{wiki-host}}/w/rest.php/v1/", "auth": {"type": "bearer", "token": access_token}, }, "resources": [ {"name": "search_page", "endpoint": {"path": "search/page", "data_selector": "pages"}}, {"name": "search_title", "endpoint": {"path": "search/title", "data_selector": "pages"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="mediawiki_pipeline", destination="duckdb", dataset_name="mediawiki_data", ) load_info = pipeline.run(mediawiki_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("mediawiki_pipeline").dataset() sessions_df = data.search_page.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM mediawiki_data.search_page LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("mediawiki_pipeline").dataset() data.search_page.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 MediaWiki 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.
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 MediaWiki?
Request dlt skills, commands, AGENT.md files, and AI-native context.