Bing webmaster tools Python API Docs | dltHub

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

Last updated:

Bing Webmaster Tools API is a REST API that provides access to data and functionalities of Bing Webmaster Tools. The REST API base URL is https://ssl.bing.com/webmaster/api.svc and Requests can be authenticated using either an API Key or OAuth 2.0..

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 Bing webmaster tools data in under 10 minutes.


What data can I load from Bing webmaster tools?

Here are some of the endpoints you can load from Bing webmaster tools:

ResourceEndpointMethodData selectorDescription
get_crawl_issues/json/GetCrawlIssuesGETRetrieves crawl issues
get_page_traffic/json/GetPageTrafficGETRetrieves page traffic data
get_query_data/json/GetQueryDataGETRetrieves search query data
get_site_info/json/GetSiteInfoGETRetrieves information about a site
get_sitemaps/json/GetSitemapsGETRetrieves sitemap information
submit_url/json/SubmitUrlPOSTSubmits a URL for indexing

How do I authenticate with the Bing webmaster tools API?

Authentication can be done via an API Key passed as an apikey query parameter, or using OAuth 2.0 with a Bearer token in the Authorization HTTP header.

1. Get your credentials

To obtain an API Key: Sign in to your account on Bing Webmaster Tools. Click on Settings. Go to API Access. Click on Generate API Key to create an API Key. Only one API key can be generated per user.

2. Add them to .dlt/secrets.toml

[sources.bing_webmaster_tools_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 Bing webmaster tools 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 bing_webmaster_tools_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline bing_webmaster_tools_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 crawl_issues and query_data from the Bing webmaster tools 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 bing_webmaster_tools_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://ssl.bing.com/webmaster/api.svc", "auth": { "type": "api_key", "api_key": api_key, }, }, "resources": [ {"name": "crawl_issues", "endpoint": {"path": "json/GetCrawlIssues"}}, {"name": "query_data", "endpoint": {"path": "json/GetQueryData"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="bing_webmaster_tools_pipeline", destination="duckdb", dataset_name="bing_webmaster_tools_data", ) load_info = pipeline.run(bing_webmaster_tools_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("bing_webmaster_tools_pipeline").dataset() sessions_df = data.crawl_issues.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM bing_webmaster_tools_data.crawl_issues LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("bing_webmaster_tools_pipeline").dataset() data.crawl_issues.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 Bing webmaster tools 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

API Key Errors

If an invalid API key is used, the API will return an HTTP status code 400. The response body will contain an error description, such as {"ErrorCode": 3, "Message": "InvalidApiKey"}.

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 Bing webmaster tools?

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