Skip to main content

Bing Webmaster Tools

Bing Webmaster Tools is Microsoft's free service for monitoring and improving how websites appear in Bing search. The Bing Webmaster Tools connector reads your verified sites, search query and page statistics, daily traffic, crawl statistics and crawl issues, inbound links, submitted sitemaps, URL index details, URL submission quota, and keyword search volumes, and can submit URLs and sitemaps to Bing for crawling.

Bing Webmaster Tools icon

Power end-to-end data operations for your Bing Webmaster Tools API with Nexla. Our bi-directional Bing Webmaster Tools connector is purpose-built for Bing Webmaster Tools, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Bing Webmaster Tools or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Bing Webmaster Tools workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

  • Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
  • Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
  • API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
  • Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites​

Nexla connects to the Bing Webmaster API as a Bing Webmaster Tools user. You need at least one site added and verified in Bing Webmaster Tools; sign in with a Microsoft, Google, or Facebook account, add your site, and verify it (for example with a DNS record, a meta tag, an XML file, or by importing it from Google Search Console). Statistics are only returned for verified sites that have Bing search traffic.

The connector supports two authentication methods. Both give access to every site verified in your Bing Webmaster Tools account.

  1. In Bing Webmaster Tools, click Settings (the gear icon in the top right), and select API Access.

  2. Accept the terms of use if prompted, select API Key, and click Generate API Key.

  3. Copy the key, and store it securely. Each user has one API key, and it works for all of that user's verified sites.

For details, see Microsoft's Getting access to the Bing Webmaster Tools API guide.

OAuth 2.0 with your own client​

  1. In Bing Webmaster Tools, go to Settings > API Access, and select OAuth Client.

  2. Register a client, and add this redirect URI: https://dataops.nexla.io/nexla-api/oauth/callback.

  3. Copy the client ID and client secret. Store the secret securely.

When you authorize the credential, Nexla requests the webmaster.manage scope and refreshes the access token automatically. For details, see Microsoft's OAuth 2.0 guide.

URL submission quota

Submit URL and Submit URL Batch use your site's daily and monthly URL submission quota. Use the Get URL Submission Quota template to check how much quota is left before sending URLs.

Authenticate​

Credentials required​

Bing Webmaster API key from Settings > API Access, sent as the apikey query parameter on every call to ssl.bing.com. Free; works for all your verified sites.

FieldRequiredSecretDescription
API KeyYesYesYour Bing Webmaster API key: Settings > API Access > Generate API Key. One key per user, valid for all your verified sites. Sent as the apikey query parameter.

Create a credential in Nexla​

  1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

  2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

  3. Select the Authentication Type: API Key or OAuth 2.0.

  4. For API Key, paste your Bing Webmaster API key into the API Key field. Nexla sends it as the apikey query parameter on every request.

    The API key is sensitive and should be kept secure. If it is exposed, generate a new key under Settings > API Access in Bing Webmaster Tools, and update this credential.

  5. For OAuth 2.0, enter the Client ID and Client Secret of your OAuth client, click Authorize, and sign in to Bing Webmaster Tools to grant access. The client must have https://dataops.nexla.io/nexla-api/oauth/callback registered as a redirect URI.

  6. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Nexla tests the credential by listing the sites in your Bing Webmaster Tools account.

Use as a data source​

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Bing Webmaster Tools connector tile, then select the credential that will be used to connect to your Bing Webmaster Tools account, and click Next; or, create a new Bing Webmaster Tools credential for use in this flow.

Endpoint templates​

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Bing Webmaster Tools endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below, grouped by area.

Each template makes a single request per run. Almost every template needs a Site URL: the verified site exactly as it appears in Bing Webmaster Tools, for example https://www.example.com/. Use the Get User Sites template to find it. In the request paths below, {base_url} is the Bing API host, which Nexla sets from the authentication method (https://ssl.bing.com for an API key, https://www.bing.com for OAuth 2.0).

The search and crawl statistics templates take no date range; Bing returns the weekly or daily series it holds for the site. Dates in Bing responses are strings in the form /Date(1316156400000-0700)/ (milliseconds since 1970 and a time zone offset).

Query values, such as page URLs and search queries, are inserted into the request URL as entered. A value that contains &, #, or + can break the request.

Sites​

Get User Sites

Lists every site in your Bing Webmaster Tools account, with its URL and verification status. Use it first to find the Site URL that the other templates need.

Search performance​

Get Query Stats

Returns your site's top Bing search queries by week, with impressions, clicks, and average click and impression positions. Use it to see what people search for to find your site.

  • Calls GET {base_url}/webmaster/api.svc/json/GetQueryStats?siteUrl={Site URL}.
  • Site URL (required): The verified site exactly as it appears in Bing Webmaster Tools, for example https://www.example.com/. Use Get User Sites to find it.
  • See the Bing Webmaster Tools API reference for the response fields.

Get Page Stats

Returns your site's top pages in Bing search by week, with impressions, clicks, and average positions. The Query field holds the page URL.

  • Calls GET {base_url}/webmaster/api.svc/json/GetPageStats?siteUrl={Site URL}.
  • Site URL (required): The verified site exactly as it appears in Bing Webmaster Tools, for example https://www.example.com/. Use Get User Sites to find it.
  • See the Bing Webmaster Tools API reference for the response fields.

Get Rank and Traffic Stats

Returns daily total impressions and clicks for your site in Bing search. Use it for overall Bing traffic trends.

  • Calls GET {base_url}/webmaster/api.svc/json/GetRankAndTrafficStats?siteUrl={Site URL}.
  • Site URL (required): The verified site exactly as it appears in Bing Webmaster Tools, for example https://www.example.com/. Use Get User Sites to find it.
  • See the Bing Webmaster Tools API reference for the response fields.

Get Query Page Stats

Returns the pages of your site that ranked for one search query, with impressions, clicks, and average positions per page and week.

  • Calls GET {base_url}/webmaster/api.svc/json/GetQueryPageStats?siteUrl={Site URL}&query={Search Query}.
  • Site URL (required): The verified site exactly as it appears in Bing Webmaster Tools, for example https://www.example.com/. Use Get User Sites to find it.
  • Search Query (required): The search query to break down. Use Get Query Stats to find queries.
  • See the Bing Webmaster Tools API reference for the response fields.

Get Page Query Stats

Returns the search queries that led to one page of your site, with impressions, clicks, and average positions per query and week. Use it to see what a page ranks for.

  • Calls GET {base_url}/webmaster/api.svc/json/GetPageQueryStats?siteUrl={Site URL}&page={Page URL}.
  • Site URL (required): The verified site exactly as it appears in Bing Webmaster Tools, for example https://www.example.com/. Use Get User Sites to find it.
  • Page URL (required): The full URL of a page on the site. Use Get Page Stats to find page URLs.
  • See the Bing Webmaster Tools API reference for the response fields.

Get Query Traffic Stats

Returns daily impressions and clicks for one search query on your site. Use it to trend a single query over time.

  • Calls GET {base_url}/webmaster/api.svc/json/GetQueryTrafficStats?siteUrl={Site URL}&query={Search Query}.
  • Site URL (required): The verified site exactly as it appears in Bing Webmaster Tools, for example https://www.example.com/. Use Get User Sites to find it.
  • Search Query (required): The search query to trend. Use Get Query Stats to find queries.
  • See the Bing Webmaster Tools API reference for the response fields.

Crawling and indexing​

Get Crawl Stats

Returns daily Bingbot crawl statistics for your site: pages crawled, pages in the index, crawl errors, counts of 2xx, 3xx, 4xx, and 5xx responses, robots.txt blocks, DNS failures, and pages with malware.

  • Calls GET {base_url}/webmaster/api.svc/json/GetCrawlStats?siteUrl={Site URL}.
  • Site URL (required): The verified site exactly as it appears in Bing Webmaster Tools, for example https://www.example.com/. Use Get User Sites to find it.
  • See the Bing Webmaster Tools API reference for the response fields.

Get Crawl Issues

Lists the URLs on your site that have crawl issues, with each URL's HTTP status code, issue flags, and inbound link count. Use it to find broken or blocked pages.

  • Calls GET {base_url}/webmaster/api.svc/json/GetCrawlIssues?siteUrl={Site URL}.
  • Site URL (required): The verified site exactly as it appears in Bing Webmaster Tools, for example https://www.example.com/. Use Get User Sites to find it.
  • See the Bing Webmaster Tools API reference for the response fields.

Get URL Info

Returns Bing's index details for one URL: HTTP status, discovery and last crawled dates, anchor count, size, and number of child URLs. Use it to check whether a page is indexed.

  • Calls GET {base_url}/webmaster/api.svc/json/GetUrlInfo?siteUrl={Site URL}&url={Page URL}.
  • Site URL (required): The verified site exactly as it appears in Bing Webmaster Tools, for example https://www.example.com/. Use Get User Sites to find it.
  • Page URL (required): The full URL of the page to look up in the Bing index.
  • See the Bing Webmaster Tools API reference for the response fields.

Get Feeds (Sitemaps)

Lists the sitemaps and feeds submitted for your site, with each one's URL, type, status, URL count, and last crawled and submitted dates.

  • Calls GET {base_url}/webmaster/api.svc/json/GetFeeds?siteUrl={Site URL}.
  • Site URL (required): The verified site exactly as it appears in Bing Webmaster Tools, for example https://www.example.com/. Use Get User Sites to find it.
  • See the Bing Webmaster Tools API reference for the response fields.

Get URL Submission Quota

Returns how many URLs your site can still submit today (DailyQuota) and this month (MonthlyQuota). Check it before using the Submit URL or Submit URL Batch destination templates.

  • Calls GET {base_url}/webmaster/api.svc/json/GetUrlSubmissionQuota?siteUrl={Site URL}.
  • Site URL (required): The verified site exactly as it appears in Bing Webmaster Tools, for example https://www.example.com/. Use Get User Sites to find it.
  • See the Bing Webmaster Tools API reference for the response fields.

Get Link Counts

Lists the pages of your site that have inbound links, with the number of links to each. Use it for a backlink overview.

  • Calls GET {base_url}/webmaster/api.svc/json/GetLinkCounts?siteUrl={Site URL}&page={Page Index}.
  • Site URL (required): The verified site exactly as it appears in Bing Webmaster Tools, for example https://www.example.com/. Use Get User Sites to find it.
  • Page Index (required; default 0): The zero-based page of results to read. Each response includes TotalPages; to read the next page, increase this value and run the template again.
  • Each run reads one page of results.
  • See the Bing Webmaster Tools API reference for the response fields.

Get URL Links

Lists the inbound links to one page of your site, with each linking URL and its anchor text.

  • Calls GET {base_url}/webmaster/api.svc/json/GetUrlLinks?siteUrl={Site URL}&link={Target Page URL}&page={Page Index}.
  • Site URL (required): The verified site exactly as it appears in Bing Webmaster Tools, for example https://www.example.com/. Use Get User Sites to find it.
  • Target Page URL (required): The URL of the page on your site whose inbound links you want. Use Get Link Counts to find pages with links.
  • Page Index (required; default 0): The zero-based page of results to read. Each response includes TotalPages; to read the next page, increase this value and run the template again.
  • Each run reads one page of results.
  • See the Bing Webmaster Tools API reference for the response fields.

Keyword research​

Get Keyword Stats

Returns the weekly Bing search volume history for a keyword in one market, with exact-match and broad-match impressions by date. Use it for keyword research. This template does not need a site.

  • Calls GET {base_url}/webmaster/api.svc/json/GetKeywordStats?q={Keyword}&country={Country}&language={Language}.
  • Keyword (required): The keyword to look up, for example running shoes.
  • Country (required; default us): The market's country, as a lowercase two-letter ISO 3166 code, for example us, gb, or de.
  • Language (required; default en-US): The market's language, as an IETF language tag, for example en-US, en-GB, or de-DE.
  • See the Bing Webmaster Tools API reference for the response fields.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration​

Bing Webmaster Tools data sources can also be manually configured to ingest data from any valid Bing Webmaster Tools API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Bing Webmaster Tools data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination​

Click the + icon on the Nexset that will be sent to the Bing Webmaster Tools destination, and select the Send to Destination option from the menu. Select the Bing Webmaster Tools connector from the list of available destination connectors, then select the credential that will be used to connect to your Bing Webmaster Tools account, and click Next; or, create a new Bing Webmaster Tools credential for use in this flow.

Endpoint templates​

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Bing Webmaster Tools endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

These templates ask Bing to crawl pages on your site. In the request paths below, {base_url} is the Bing API host set by the authentication method.

Submit Feed (Sitemap)

Submits a sitemap or an RSS or Atom feed to Bing for the site set in Site URL, for each record.

  • Sends POST {base_url}/webmaster/api.svc/json/SubmitFeed.
  • Site URL (required): The verified site exactly as it appears in Bing Webmaster Tools, for example https://www.example.com/. Use Get User Sites to find it.
  • Each record must have a feedUrl field with the full URL of the sitemap or feed. Nexla sends one request per record.
  • See the Bing Webmaster Tools API reference for the request fields.

Submit URL

Asks Bing to crawl and index one URL now, for each record. Each submission uses one URL from your site's submission quota.

  • Sends POST {base_url}/webmaster/api.svc/json/SubmitUrl.
  • Site URL (required): The verified site exactly as it appears in Bing Webmaster Tools, for example https://www.example.com/. Use Get User Sites to find it.
  • Each record must have a url field with the full URL of a page on the site set in Site URL. Nexla sends one request per record.
  • See the Bing Webmaster Tools API reference for the request fields.

Submit URL Batch

Asks Bing to crawl and index a list of up to 500 URLs in one request. Each URL uses one URL from your site's submission quota.

  • Sends POST {base_url}/webmaster/api.svc/json/SubmitUrlBatch.
  • Each record is sent as the JSON request body, one request per record. A record must have siteUrl (the verified site) and urlList (an array of up to 500 full URLs on that site).
  • See the Bing Webmaster Tools API reference for the request fields.

Manual configuration​

Bing Webmaster Tools destinations can also be manually configured to send data to any valid Bing Webmaster Tools API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

Save & activate​

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Bing Webmaster Tools endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Bing Webmaster Tools endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.