Bing webmaster tools Python API Docs | dltHub

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

Last updated:

Bing Webmaster Tools is a service for site owners to monitor site health, manage indexing, and submit content to Bing's search index. The REST API base URL is https://ssl.bing.com/webmaster/api.svc and supports API key or OAuth 2.0 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 add "dlt[hub]" 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_user_sitesjson/GetUserSitesGETRetrieves a list of sites registered to the user
get_link_countsjson/GetLinkCountsGETLinksRetrieves inbound link counts for a site
get_query_datajson/GetQueryDataGETRetrieves search query data
get_crawl_issuesjson/GetCrawlIssuesGETRetrieves a list of crawl issues for a site
get_site_infojson/GetSiteInfoGETRetrieves detailed information about a site
get_sitemapsjson/GetSitemapsGETRetrieves a list of submitted sitemaps

How do I authenticate with the Bing webmaster tools API?

Requests are authenticated via either an API key passed as a query parameter or an OAuth 2.0 access token provided in the Authorization header as a Bearer token.

1. Get your credentials

  1. Sign in to your Bing Webmaster Tools account. 2. Navigate to the Settings menu located in the top right corner of the dashboard. 3. Select the API Access section. 4. If this is your first time accessing this section, review and accept the displayed Terms and Conditions. 5. Click Generate API Key to create your credentials. Note that only one API key can be generated per user, and it applies to all verified sites within that account.

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 init uv add "dlt[hub]"

1. Install the dlt AI harness:

uv run dlthub 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:

uv run dlthub ai toolkit install rest-api-pipeline

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:

uv run 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:

uv run dlthub 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 json/GetCrawlIssues and json/GetQueryData 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": "bearer", "token": api_key}, }, "resources": [ {"name": "get_crawl_issues", "endpoint": {"path": "json/GetCrawlIssues"}}, {"name": "get_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.get_query_data.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM bing_webmaster_tools_data.get_query_data LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("bing_webmaster_tools_pipeline").dataset() data.get_query_data.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.


Next steps

Continue your data engineering journey with the other toolkits of the dltHub AI harness:

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-platform — Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform

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.

Available Pipelines