Wp-all-export-pro Python API Docs | dltHub

WP All Export Pro is a WordPress plugin that enables real‑time data exports and can push exported records to external URLs via a POST‑based integration. The REST API base URL is `` and No authentication is required for WP All Export Pro's outgoing requests; any auth is handled by the target endpoint..

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 Wp-all-export-pro data in under 10 minutes.

---

What data can I load from Wp-all-export-pro?

Here are some of the endpoints you can load from Wp-all-export-pro:

---

How do I authenticate with the Wp-all-export-pro API?

WP All Export Pro does not perform authentication when posting export data; authentication is optional and must be handled by the target endpoint.

1. Get your credentials

1. Log in to your WordPress admin dashboard.
2. Navigate to WP All Export → Settings.
3. Open the "Real‑time Exports" tab.
4. Enable "Export each post in real time as they are completed".
5. Enter the destination endpoint URL (the URL of the service that will receive the POST).
6. Save the settings. No API key or token is required from WP All Export Pro.

2. Add them to .dlt/secrets.toml

Copy
[sources.wp_all_export_pro_source]

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:

Copy
uv venv && source .venv/bin/activate
uv pip install "dlt[workspace]"

1. Install the dlt AI Workbench:

Copy
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:

Copy
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 Wp-all-export-pro 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:

Copy
python wp_all_export_pro_pipeline.py

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

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

Inspect your pipeline and data:

Copy
dlt pipeline wp_all_export_pro_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 real_time_export and pmxe_after_export_hook from the Wp-all-export-pro API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

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

@dlt.source
def wp_all_export_pro_source(=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "",
            "auth": {
                "type": "none",
                "": ,
            },
        },
        "resources": [
            {"name": "real_time_export", "endpoint": {"path": "(user-defined URL)"}},
            {"name": "pmxe_after_export_hook", "endpoint": {"path": "pmxe_after_export"}}
        ],
    }
    yield from rest_api_resources(config)


def get_data() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="wp_all_export_pro_pipeline",
        destination="duckdb",
        dataset_name="wp_all_export_pro_data",
    )
    load_info = pipeline.run(wp_all_export_pro_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):

Copy
import dlt

data = dlt.pipeline("wp_all_export_pro_pipeline").dataset()
sessions_df = data.real_time_export.df()
print(sessions_df.head())

SQL (DuckDB example):

Copy
SELECT * FROM wp_all_export_pro_data.real_time_export LIMIT 10;

In a marimo or Jupyter notebook:

Copy
import dlt

data = dlt.pipeline("wp_all_export_pro_pipeline").dataset()
data.real_time_export.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 Wp-all-export-pro data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.

---

Troubleshooting

HTTP POST Failures

• cURL errors – The plugin uses cURL to send the POST. If curl_errno or curl_error is set, the export will be marked as failed. Check server firewall rules and ensure the target URL is reachable.
• Network timeouts – Large payloads may cause timeouts. Increase the PHP max_execution_time or split exports.

Authentication Errors on Receiver

• Since WP All Export Pro does not include authentication, the receiving endpoint must handle any auth. If the endpoint returns a 401/403, the POST will fail. Configure the endpoint to accept unauthenticated requests or add custom headers in the integration code.

Payload Validation

• The JSON payload must be valid UTF‑8. Malformed data will cause the POST to be rejected by the receiver. Verify the exported fields for special characters.

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.

Copy
dlt ai toolkit data-exploration install
dlt ai toolkit dlthub-runtime install

• How to deploy a pipeline
• How to explore your data in marimo Notebooks
• How to query your data in Python with dataset
• Join the dlt community on Slack