> ## Documentation Index
> Fetch the complete documentation index at: https://support.configview.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Bing Webmaster Tools setup

Configview reads your Bing Webmaster Tools account (the console where you register your sites with Bing search) through the **Bing Webmaster API** (`https://ssl.bing.com/webmaster/api.svc/json/<Method>`), using an **API key** generated in Webmaster Tools. Configview only reads. It never submits URLs, adds or removes sites or users, or changes settings.

You will end up with **1 required secret** (`BING_WEBMASTER_API_KEY`) in Configview when setup is complete.

> **Scope of this integration today.** Configview answers "who can manage our sites in Bing, and in what state are they": every site with its verification state, who holds access to each site and with which role (administrator, read and write, read only), who granted it and when, expired delegations, daily crawl and index health counts, crawl issues grouped by HTTP status, submitted sitemaps by host, and the URL submission quota. It does **not** read search queries, keywords, traffic, backlinks, page addresses or verification codes. The API has no audit log, API key list or user-activity data, so those are not collected.

***

## What you need

* A Bing Webmaster Tools account that owns or administers the sites you want to review
* The **Administrator** role on those sites. Bing returns a site's access list only to administrators, so a read-only user would see sites but no people.

***

## Step 1: Open the Bing Webmaster Tools page in Configview

Open Configview in a second browser tab and leave it open:

`https://{companyname}.configview.com/admin/integrations/bing-webmaster`

***

## Step 2: Create the API key

1. Sign in to [Bing Webmaster Tools](https://www.bing.com/webmasters) with a dedicated user that is an **Administrator** on your sites (not a personal account if you can avoid it)
2. Click **Settings** (top right) and open **API Access**
3. Accept the terms the first time, click **API Key**, then **Generate API Key**. Bing allows **one key per user**, and the key works for every site that user can see.
4. Copy the key
5. In the Configview tab paste it into `BING_WEBMASTER_API_KEY` under **Credentials** and save

If the key is lost or exposed, delete it on the same page and generate a new one. Deleting a key stops every application using it until they are updated.

***

## Step 3: Connect and verify

1. Click **Connect**. Configview creates its tables and schedules every collector at your default run time:

| Script | Notes |
| - | - |
| **Sites** | Every site the key's user can see and whether it is verified. |
| **Site roles** | Who has which role on each verified site, who granted it, expired delegations. |
| **Crawl stats** | Daily crawl and index counts per site. |
| **Crawl issues** | Problem pages per site grouped by HTTP status and issue type, counts only. |
| **Sitemaps** | Submitted sitemaps and feeds per site, host only. |
| **URL submission quota** | Remaining daily and monthly URL submissions per site. |

2. Click **Verify now**. The health check reads the secret, then calls `GetUserSites`.

If a check fails:

* **Key refused.** The key was deleted, regenerated or mistyped.
* **Sites visible but no roles.** The key's user is not an administrator of those sites.

***

## Data Tables

Each table has a `run_at` column and keeps only the newest run.

| Table | Source | Key Columns |
| - | - | - |
| `bingwmt_sites` | `GetUserSites` | site\_url, site\_host, is\_verified |
| `bingwmt_site_roles` | `GetSiteRoles` | site\_url, email, role\_name, delegator\_email, has\_delegated\_code, expired, granted\_at |
| `bingwmt_crawl_stats` | `GetCrawlStats` | site\_url, stat\_date, crawled\_pages, in\_index, crawl\_errors, code\_4xx, code\_5xx, malware\_pages |
| `bingwmt_crawl_issues` | `GetCrawlIssues` | site\_url, http\_code, issue\_flags, url\_count, inbound\_links |
| `bingwmt_feeds` | `GetFeeds` | site\_url, feed\_host, feed\_type, feed\_status, url\_count, submitted\_at, last\_crawled\_at |
| `bingwmt_url_quota` | `GetUrlSubmissionQuota` | site\_url, daily\_quota, monthly\_quota |

***

## Things worth knowing

**One key, one user's view.** The API key belongs to a person, not to your organisation. It sees only the sites that person can see, and a person who leaves takes the key's access with them. Use a shared, dedicated Webmaster Tools user rather than a personal account.

**Verification and invitation codes are never read.** Site responses carry ownership verification codes and role responses carry invitation codes; Configview reads named fields only and keeps just a flag that a code exists.

**Page addresses are never kept.** Crawl issues arrive one page at a time. Configview counts them per site, HTTP status and issue type before storing anything. Sitemap addresses are reduced to their host.

**Rate limit.** Bing publishes no request ceiling for this API. Configview paces itself at 30 requests a minute, waits as long as Bing asks on HTTP 429, and makes one request per verified site per collector.

## Known gaps

* No audit log, user activity or API key list in the API
* Search performance (queries, keywords, clicks, backlinks) is deliberately not collected
* Only sites verified for the key's user get role, crawl, sitemap and quota data
* Values such as role and issue flags are enums; unfamiliar values are stored as returned

## What isn't collected

* Search queries, keywords, traffic and ranking data
* Backlinks and inbound link sources
* Individual page addresses and fetched page content
* Verification codes, DNS codes and invitation codes
* The API key value


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.