Bing Webmaster Tools officially retired its legacy SOAP and POX/HTTP APIs on August 31, 2026. If you missed this, and your integration was still calling those endpoints, requests to them have now stopped working entirely.
What changed
Bing Webmaster Tools previously supported three API protocols — SOAP, POX/HTTP, and JSON/HTTP. Bing has now consolidated everything onto JSON/HTTP (REST), retiring the two older protocols for good.
What stayed the same
All API methods remain fully available through JSON/HTTP with identical functionality. Your API key hasn’t changed, and quotas, rate limits, and permissions remain the same.
Who’s affected
You’re impacted if your integration calls URLs matching:
https://ssl.bing.com/webmaster/api.svc/pox/...https://ssl.bing.com/webmaster/api.svc/soap/...
You’re fine if you’re already using:
https://ssl.bing.com/webmaster/api.svc/json/...
Summary of Changes
See the full Migration Guide
Bing has published detailed before-and-after examples for common operations like GetUserSites, AddSite, and SubmitUrlBatch, showing exactly how request and response formats change between POX/SOAP and JSON.
The post Bing has retired its legacy SOAP and POX Webmaster APIs appeared first on Search Engine Watch.
