Website-toolbox-forum Python API Docs | dltHub

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

Last updated:

Website Toolbox Forum API is a REST service that provides website analytics data including categories, messages and page view statistics. The REST API base URL is https://api.websitetoolbox.com and All requests require the x-api-key, x-api-username and x-api-email headers for authentication..

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 Website-toolbox-forum data in under 10 minutes.


What data can I load from Website-toolbox-forum?

Here are some of the endpoints you can load from Website-toolbox-forum:

ResourceEndpointMethodData selectorDescription
categoriesv1/api/categoriesGETdataRetrieve the list of available categories.
messagesv1/api/messagesGETdataList messages with pagination information.
page_viewsv1/api/page_viewsGETReturns an array of page view objects.
sitesv1/api/sitesGETdataGet information about sites owned by the account.
usersv1/api/usersGETdataFetch user profile details.

How do I authenticate with the Website-toolbox-forum API?

Authentication is performed via three HTTP headers: x-api-key (your API key), x-api-username (your account username) and x-api-email (the email address associated with the account). These must be sent with every request.

1. Get your credentials

  1. Sign in to your Website Toolbox account.
  2. Navigate to the dashboard or account settings page.
  3. Locate the "API Access" or "Developer Settings" section.
  4. Click "Create New API Key" (or view the existing key).
  5. Copy the displayed API Key.
  6. Note your account username and the email address associated with the account (visible on the profile page).
  7. Store these three values securely; they will be used as the x-api-key, x-api-username and x-api-email header values in API calls.

2. Add them to .dlt/secrets.toml

[sources.website_toolbox_forum_source] api_key = "your_api_key_here" api_username = "your_username_here" api_email = "your_email_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 Website-toolbox-forum 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 website_toolbox_forum_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline website_toolbox_forum_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 categories and page_views from the Website-toolbox-forum 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 website_toolbox_forum_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.websitetoolbox.com", "auth": { "type": "api_key", "api_key": api_key, }, }, "resources": [ {"name": "categories", "endpoint": {"path": "v1/api/categories", "data_selector": "data"}}, {"name": "page_views", "endpoint": {"path": "v1/api/page_views"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="website_toolbox_forum_pipeline", destination="duckdb", dataset_name="website_toolbox_forum_data", ) load_info = pipeline.run(website_toolbox_forum_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("website_toolbox_forum_pipeline").dataset() sessions_df = data.categories.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM website_toolbox_forum_data.categories LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("website_toolbox_forum_pipeline").dataset() data.categories.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 Website-toolbox-forum 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

Rate Limits

The API enforces a limit of 3 requests per second. Exceeding this limit returns a 400 Bad Request response.

{ "error": "Rate limit exceeded", "code": 400 }

Authentication Errors

If any of the required headers (x-api-key, x-api-username, x-api-email) are missing or invalid, the server responds with a 401 Unauthorized error.

{ "error": "Invalid authentication credentials", "code": 401 }

Pagination

Responses that include a list of records contain a has_more boolean field. When has_more is true, use the provided pagination parameters (e.g., page or limit) to request the next page.

{ "data": [ ... ], "has_more": true, "size": 100, "total_size": 350 }

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 Website-toolbox-forum?

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