News: In early August 2026 Microsoft reminded developers that the Bing Webmaster Tools SOAP and POX APIs will be retired on August 31, 2026. After that date, requests to those endpoints will no longer be served and integrations must move to the JSON/HTTP API (Krishna Madhavan, Microsoft, reported by Search Engine Roundtable, August 3, 2026).
The essentials in 20 seconds
- Two protocols die on August 31, 2026: SOAP and POX/HTTP. JSON/HTTP stays.
- The migration is light: same methods, same API key, same quotas. In the URL,
/pox/becomes/json/. - The stake is not the code, it is the measurement: since February 2026 Bing Webmaster Tools hosts the Copilot citation report.
- A broken reporting pipe does not look like an error, it looks like a flat line. That is the real risk.
Twenty six days. That is what is left for anyone whose SEO reporting chain still runs on Bing's legacy protocols. And unlike an outage, this one will make no noise at all.
What Microsoft is actually retiring
Three protocols have coexisted on the Bing Webmaster Tools API: SOAP, POX/HTTP (plain XML over HTTP) and JSON/HTTP. Two are going away, one survives.
- SOAP and POX: no requests served after August 31, 2026.
- JSON/HTTP, also called REST: supported and actively developed.
The good news is that the migration is cosmetic in most cases. Per the announcement, all API methods remain fully available over JSON/HTTP with identical functionality, the API key does not change and needs no reissuance, and quotas, rate limits and permissions are preserved. In practice, in the call URL documented by Microsoft, the /webmaster/api.svc/pox/ segment becomes /webmaster/api.svc/json/. The rest of the work is reading JSON where you used to read XML.
One detail worth noting: the official Bing Webmaster Tools API Services page on Microsoft Learn still documented all three protocols side by side, with no retirement notice whatsoever, when we checked it on August 5, 2026. In other words: an endpoint still being documented is no proof it will still be served on September 1. Do not mistake documentation for a schedule.
Why this is more than a technical migration
What makes this announcement worth more than a backlog line is what Bing Webmaster Tools has become in 2026.
Since February 11, 2026, the tool has hosted the AI Performance report, which surfaces the pages on your site cited by Microsoft Copilot along with grounding queries, the internal reformulations the assistant generates to go and fetch its sources. It is one of the few first party windows into how an AI system actually consumes your content, where most vendors leave you guessing.
In a matter of months, Bing Webmaster Tools went from secondary tool to GEO measurement instrument. And a measurement instrument that stops without warning is more dangerous than one you never had: at least when you have no thermometer, you know you have none.
What it changes for a small business
You probably do not call this API yourself. Your tools do. Your agency does. Your SEO plugin may well do too, to push URLs for indexing.
The real risk is not a loud 500 error. It is silence. A dashboard that stops refreshing looks a lot like a flat line. You will not see an incident, you will see stagnation, and you will draw the wrong conclusions from it for weeks: cutting a budget that was working, restarting a project that was pointless, concluding a channel is dead when it is merely no longer measured.
The question to ask your agency or tool vendor this week: "Does our Bing Webmaster Tools integration still use SOAP or POX, and if so, what is the cutover date?" A vague answer is an answer.
What to do before August 31
- Inventory. Search for
api.svc/poxand any SOAP reference across your scripts, connectors, automation scenarios and scheduled jobs. - Switch the URL. Replace the
/pox/segment with/json/and move the parsing from XML to JSON. The API key stays the same. - Test before the end of August. Not on the 30th. A failure found on September 1 is a month of lost data, and crawl data cannot be backfilled retroactively.
- Add a freshness alert. If your reporting has received no rows for 48 hours, somebody should be told. That rule holds well beyond this particular deadline.
Not sure where your AI visibility numbers come from? We look at your setup and tell you what is measured, what is not, and what is about to break. .
Our take
An API migration is not spectacular, and that is exactly why it slips through. The real lesson is not technical: many companies do not know which pipes feed their visibility numbers, and find out on the day the numbers stop.
Our position fits in one sentence: measure what you steer, and know how the measurement reaches you. August 31 is a good occasion to check both.
What this article does not cover
The link between the API and the AI data is not demonstrated. The announced retirement concerns the classic Webmaster API methods. Microsoft does not document the AI Performance report as an API endpoint, and we found no source confirming those citation figures can be pulled that way. We are flagging a measurement chain risk, we are not claiming your Copilot citations will disappear.
This does not touch Google. Search Console is a separate perimeter with its own AI reporting.
We have no inventory of affected tools. To our knowledge, no vendor has published a list of its connectors still running on SOAP. Hence the question to ask directly, rather than assume.
Frequently asked questions
Which Bing Webmaster Tools APIs go away on August 31, 2026?
Does my Bing API key change with the migration?
How do I know whether my integration is affected?
Is my Copilot AI citation data affected?
Related reading
- Grounding queries and cited pages : what Bing actually exposes about how Copilot fetches its sources.
- Bing Webmaster Tools GEO metrics : which ones steer decisions and which are noise.
- Google's AI visibility report : the Search Console counterpart, on a separate perimeter.
- How Bing AI grounding picks sources : the rules classic rank tracking never surfaces.
Editorial note. Disclosure: Cicéro is an SEO and GEO content agency. This analysis is editorial, is not sponsored, and carries no commercial relationship with Microsoft.
Sources
- → Search Engine Roundtable : announcement of the SOAP and POX API retirement on August 31, 2026, reporting Krishna Madhavan (Microsoft), August 3, 2026
- → Microsoft Learn, Bing Webmaster Tools API Services : official documentation of the SOAP, POX and JSON protocols and their URL formats (accessed August 5, 2026)
- → Bing Webmaster Tools, AI Performance : documentation of the Copilot citation report and grounding queries
Growth and SEO content strategist, I founded Cicéro to help businesses build lasting organic visibility, on Google and in AI-generated answers alike. Every piece of content we produce is designed to convert, not just to exist.
LinkedIn