Load BP REST API data to DuckDB

The BP REST API provides endpoints for interacting with BuddyPress community data and actions on a WordPress site remotely using JSON objects. Everything needed to build a working BP REST 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 BP REST API to DuckDB pipeline

Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.

PromptCopy prompt
Run uvx dlthub-init@latest to build a pipeline from BP REST 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 BP REST 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.

---

BP REST API API at a glance

These values come from the BP REST API API reference — the authoritative source if anything here looks out of date.

---

How do I authenticate with the BP REST API API?

The BP REST API (BuddyPress) utilizes WordPress cookie authentication. Requests require a non-expiring nonce (often named X-WP-Nonce) passed in the request headers.

1. Get your credentials

To obtain the API credentials for the BookingPress REST API, log in to your account on the BookingPress website, navigate to the 'Access Passes' section, and download the 'REST API' add-on. Once the plugin is installed and activated in your WordPress dashboard, navigate to 'BookingPress' > 'Settings' > 'API Settings'. From there, click the 'Generate' button to create your API Security Key.

2. Add them to .dlt/secrets.toml

Copy
[sources.bp_rest_api_source]
api_key = "your_generated_bookingpress_api_key_here"

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 BP REST API data can I load into DuckDB?

These are the BP REST API endpoints dlt can load into DuckDB:

---

How do I load only new BP REST API records?

BP REST API exposes page on buddypress/v1/members, so dlt can request only the records that changed since the last run. Set it as the cursor_path and dlt tracks the high-water mark for you between runs.

Copy
{"name": "members", "endpoint": {
    "path": "buddypress/v1/members",
    "incremental": {"cursor_path": "page", "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 BP REST API pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading /bookings and /customers from the BP REST API API into DuckDB:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def bp_rest_api_source(nonce=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://example.com/wp-json/buddypress/v1/",
            "auth": {"type": "bearer", "token": nonce},
        },
        "resources": [
            {"name": "members", "endpoint": {"path": "buddypress/v1/members"}},
            {"name": "activity", "endpoint": {"path": "buddypress/v1/activity"}}
        ],
    }
    yield from rest_api_resources(config)


def load_bp_rest_api_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="bp_rest_api_pipeline",
        destination="duckdb",
        dataset_name="bp_rest_api_data",
    )
    load_info = pipeline.run(bp_rest_api_source())
    print(load_info)


if __name__ == "__main__":
    load_bp_rest_api_to_duckdb()

Run it with python bp_rest_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 BP REST 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):

Copy
import dlt

data = dlt.pipeline("bp_rest_api_pipeline").dataset()
df = data.members.df()
print(df.head())

SQL:

Copy
SELECT * FROM bp_rest_api_data.members LIMIT 10;

See querying your data with dataset and exploring it in marimo notebooks.

---

How do I deploy the BP REST 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 BP REST API loads into governed, documented models.
• Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.

Book a demo →

---

What other destinations can I load BP REST API data to?

dlt loads into any of these — only the destination argument changes:

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

• Ready for production? Book a demo of the dltHub platform →
• dlt LLM-native workflow docs
• REST API source reference
• Join the dlt community on Slack