Memberpress Python API Docs | dltHub

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

Last updated:

MemberPress Developer Tools Add-on extends MemberPress to include a full REST API and full Webhook event capability. The REST API base URL is http://yourdomain.com/wp-json/mp/v1 and All requests primarily require an API key for authentication, sent in the MEMBERPRESS-API-KEY HTTP header..

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


What data can I load from Memberpress?

Here are some of the endpoints you can load from Memberpress:

ResourceEndpointMethodData selectorDescription
memeGETTest MemberPress REST endpoint Authentication
membersmembersGETRetrieve a list of members
member_by_idmembers/{id}GETRetrieve a specific member by ID
subscriptionssubscriptionsGETRetrieve a list of subscriptions
subscription_by_idsubscriptions/{id}GETRetrieve a specific subscription by ID
membershipsmembershipsGETRetrieve a list of memberships
membership_by_idmemberships/{id}GETRetrieve a specific membership by ID
transactionstransactionsGETRetrieve a list of transactions
transaction_by_idtransactions/{id}GETRetrieve a specific transaction by ID
couponscouponsGETRetrieve a list of coupons
coupon_by_idcoupons/{id}GETRetrieve a specific coupon by ID
rulesrulesGETRetrieve a list of rules
rule_by_idrules/{id}GETRetrieve a specific rule by ID
webhooks_subscribewebhooks/subscribeGETSubscribe to webhooks
webhooks_unsubscribewebhooks/unsubscribeGETUnsubscribe from webhooks
membersmembersPOSTAdd or update user meta via REST requests

How do I authenticate with the Memberpress API?

Authentication is primarily done by including an API key in the MEMBERPRESS-API-KEY HTTP header. Basic Authentication using WordPress Application Passwords is also supported but less preferred.

1. Get your credentials

To obtain API credentials, navigate to the MemberPress Developer Tools settings within your WordPress dashboard. The API key will be available there.

2. Add them to .dlt/secrets.toml

[sources.memberpress_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 Memberpress 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 memberpress_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline memberpress_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 members and subscriptions from the Memberpress 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 memberpress_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "http://yourdomain.com/wp-json/mp/v1", "auth": { "type": "api_key", "api_key": api_key, }, }, "resources": [ {"name": "members", "endpoint": {"path": "members"}}, {"name": "subscriptions", "endpoint": {"path": "subscriptions"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="memberpress_pipeline", destination="duckdb", dataset_name="memberpress_data", ) load_info = pipeline.run(memberpress_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("memberpress_pipeline").dataset() sessions_df = data.members.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM memberpress_data.members LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("memberpress_pipeline").dataset() data.members.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 Memberpress 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.


Troubleshooting

Authentication Failures

If you encounter a 401 status code, it indicates an authentication failure. Ensure that your API key is correctly included in the MEMBERPRESS-API-KEY HTTP header. While Basic Auth via WordPress Application Passwords is supported, it may require specific server configurations to properly pass the Authorization header.

Webhook Validation

For webhook requests, validate the request by checking for the memberpress-webhook-key header.

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 Memberpress?

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