Microsoft is retiring its legacy SOAP and POX/HTTP APIs for Bing Webmaster Tools on August 31, 2026. After that date, requests to those endpoints will no longer be served. If your site or agency runs any integration built on those protocols, it stops working on September 1. The REST/JSON API replaces them entirely, with identical functionality, the same API key, and the same quotas.

What changed and why it matters

Krishna Madhavan from Microsoft posted reminders on both LinkedIn and X, urging anyone still using these legacy APIs to migrate to the JSON/HTTP (REST) API before the deadline.

The migration is less painful than it sounds. All API methods remain fully available in the REST version. Your existing API key carries over with no re-issuance required. Quotas, rate limits, and permissions stay the same. The REST/JSON endpoints are the ones Microsoft is actively developing going forward, so this is a forced upgrade to the better-supported option.

Separately, SEO consultant Lily Ray publicly asked Madhavan on X to add page-level filtering to queries and keywords in Bing Webmaster Tools performance reports, a feature Google Search Console has had for years. Madhavan responded on July 31, 2026: “We will work on it.” Bing currently offers no native filter box in its reporting interface, though data can be downloaded and filtered manually.

Two signals in one week: Microsoft is actively investing in Bing Webmaster Tools infrastructure and listening to practitioner feedback. That matters when deciding how much operational weight to give Bing in your reporting stack.

How the API retirement affects your business by segment

E-commerce stores running automated URL submission

If your store runs any automated feed submission or crawl-submission scripts through Bing Webmaster Tools APIs, pushing new product URLs to Bing’s index after catalog updates for example, and those scripts were built on SOAP or POX, they stop working on September 1, 2026. For Performance Max campaigns where organic Bing visibility supplements paid traffic, a broken indexing pipeline means new SKUs or landing pages may not surface organically on Bing, pushing more volume through paid channels and quietly inflating your CPA. Check with whoever built your integrations. If it is a plugin or third-party tool, check their changelog for a REST migration update.

B2B manufacturing and equipment companies

In B2B, Bing often punches above its weight. Microsoft’s own data has consistently shown higher household income and professional demographics among Bing users. If your agency or in-house team built custom reporting dashboards that pull Bing Webmaster Tools data via API, keyword performance, crawl errors, index coverage, those pipelines break on August 31 if they are still on SOAP/POX. For long sales cycles, losing even two weeks of Bing organic visibility data mid-funnel creates blind spots in attribution. The upcoming page-level filtering feature will also make it easier to isolate which landing pages drive qualified traffic versus informational bounces, useful for accounts where every lead counts.

Local service businesses using the web interface

Most local service businesses are not running custom API integrations. They use Bing Webmaster Tools through the web interface directly. If that is you, this retirement has zero operational impact. The web UI is unaffected. The only scenario where this touches a local account is if a white-label SEO platform or reporting tool your agency uses has not updated its Bing integration. Ask your provider directly.

What to do before August 31, 2026

1. Audit your integrations this week. Search your codebase or ask your developer to grep for “SOAP” or “POX” in any scripts touching Bing Webmaster Tools. Check third-party SEO platforms such as Conductor or Botify for their migration status.

2. Follow Microsoft’s migration guide. The official JSON/HTTP REST API documentation is linked from the Bing Webmaster Tools API page. Your API key, quotas, and permissions are unchanged, so the migration is largely a protocol swap: SOAP envelope structures replaced with standard HTTP requests and JSON payloads.

3. Set a hard internal deadline of August 10. That gives you three weeks before the August 31 cutoff to test in staging, catch errors, and deploy without a weekend emergency.

4. If you use a third-party tool, open a support ticket today. Do not assume they have migrated. Confirm it in writing. If they have not, escalate or plan a manual workaround.

5. For local businesses using only the web UI: this does not apply to you. The interface is unaffected. Spend your time on review generation and local pack optimization instead.

Frequently asked questions

Does the Bing Webmaster Tools API retirement affect the web interface?
No. The retirement applies only to the legacy SOAP and POX/HTTP API endpoints. Anyone using Bing Webmaster Tools through the browser-based dashboard will see no change on or after August 31, 2026.

Do I need a new API key to use the REST API?
No. Microsoft confirmed that existing API keys carry over to the JSON/HTTP REST API with no re-issuance required. Quotas, rate limits, and permissions remain the same, so the migration is a protocol change, not an account change.

What happens if I miss the August 31 deadline?
Requests sent to the legacy SOAP or POX endpoints will no longer be served after August 31, 2026. Any automated integration still using those endpoints will break silently, which means URL submissions, crawl data pulls, or keyword reporting pipelines will stop returning data without an obvious error message to the end user.

Work with me

If you are not sure whether your Bing Webmaster Tools setup uses legacy APIs, or you want a full technical audit of your organic and paid Bing presence before the deadline, I offer a fixed-scope account audit that covers exactly this. You get a clear action list, not a slide deck. [Contact me here] and I will tell you within 24 hours whether it is worth your time.