WordPress VIP Python API Docs | dltHub

Build a WordPress VIP-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.

Last updated:

The WordPress REST API allows applications to interact with WordPress sites via JSON, enabling efficient content management and integration. VIP enhances its performance and security. VIP documentation provides detailed guidance on optimizing and using the API effectively. The REST API base URL is https://<your-custom-domain.com>/wp-json/ and The WordPress VIP REST API supports multiple authentication methods, including OAuth 2.0, Basic Auth, JWT, Cookies, and Application Passwords. OAuth 2.0 is generally recommended for secure programmatic access..

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 WordPress VIP data in under 10 minutes.


What data can I load from WordPress VIP?

Here are some of the endpoints you can load from WordPress VIP:

ResourceEndpointMethodData selectorDescription
postswp/v2/postsGETRetrieve a list of posts
pageswp/v2/pagesGETRetrieve a list of pages
userswp/v2/usersGETRetrieve a list of users
categorieswp/v2/categoriesGETRetrieve a list of categories
tagswp/v2/tagsGETRetrieve a list of tags

How do I authenticate with the WordPress VIP API?

Authentication for the WordPress VIP REST API can be handled via various methods, with OAuth 2.0 being a recommended approach. For OAuth 2.0, an access token is typically included in the Authorization header as a Bearer token.

1. Get your credentials

The method for obtaining API credentials varies by authentication type. For OAuth 2.0, you would typically register an application to receive a client ID and client secret, then use these to obtain an access token. For Application Passwords, these can be generated directly from your WordPress user profile. Consult the specific WordPress VIP documentation for detailed steps on your chosen authentication method.

2. Add them to .dlt/secrets.toml

[sources.wordpress_vip_source] 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 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 WordPress VIP 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 wordpress_vip_pipeline.py

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

Pipeline wordpress_vip_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset wordpress_vip_data The duckdb destination used duckdb:/wordpress_vip.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

dlt pipeline wordpress_vip_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 posts and pages from the WordPress VIP 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 wordpress_vip_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://<your-custom-domain.com>/wp-json/", "auth": { "type": "bearer", "token": access_token, }, }, "resources": [ {"name": "posts", "endpoint": {"path": "wp/v2/posts"}}, {"name": "pages", "endpoint": {"path": "wp/v2/pages"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="wordpress_vip_pipeline", destination="duckdb", dataset_name="wordpress_vip_data", ) load_info = pipeline.run(wordpress_vip_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("wordpress_vip_pipeline").dataset() sessions_df = data.posts.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM wordpress_vip_data.posts LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("wordpress_vip_pipeline").dataset() data.posts.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 WordPress VIP 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 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 WordPress VIP?

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