Microsoft's retirement of the Bing Webmaster Tools SOAP and POX/HTTP APIs closes the final chapter of an XML-era integration approach that dates back to when SOAP was the standard way every enterprise service communicated. The good news is genuinely good: nothing functionally changes, your API key stays the same, and every method you use today migrates directly to the JSON/REST equivalent. The bad news is the deadline is firm — August 31, 2026 — and any integration still calling the legacy URLs after that date stops working without warning. This guide gives you everything you need to understand exactly what's retiring, confirm whether your integration is affected, and complete the migration before the deadline hits.
I manage Bing Webmaster Tools integrations for clients across healthcare, legal services, hospitality, and e-commerce as part of broader SEO infrastructure strategy. API integrations for automated URL submission, performance data pulls, and crawl issue monitoring are standard tooling across agency-scale accounts — and the August 31 deadline is close enough that any team that hasn't already audited their stack for legacy SOAP or POX dependencies needs to do it this week, not next month. This article walks through the complete picture so you can move quickly and confidently.
What Is Actually Retiring — A Precise Definition
Bing Webmaster Tools has supported three distinct API protocols since it launched its programmatic access layer. Understanding what each protocol actually is — and why Microsoft is consolidating — makes the migration decision feel less like an administrative burden and more like the straightforward modernisation it actually is.
| Protocol | What It Is | Status After August 31, 2026 |
|---|---|---|
| SOAP | Simple Object Access Protocol — structures API requests and responses as XML-wrapped envelopes over HTTP. The enterprise standard of the early 2000s, designed for complex message exchange patterns, message-based security, and non-HTTP transports. | Retired — requests stop being served |
| POX/HTTP | Plain Old XML over HTTP — simpler than SOAP, uses basic XML without the envelope wrapper. Compatible with clients that don't support SOAP natively, including standard web browsers. Still sends and receives XML rather than JSON. | Retired — requests stop being served |
| JSON/HTTP (REST) | JavaScript Object Notation over HTTP — the modern web API standard. Lighter than XML, natively supported by every current programming language, framework, and tool in active use. All future development happens here. | Supported and actively developed |
Microsoft built its Webmaster API when SOAP and POX were the standard. JSON arrived as the simpler, lighter, universally-supported successor. Microsoft has quietly supported all three for years. After August 31, 2026, only JSON works. Nothing else about the API, your account, your API key, your quotas, your rate limits, or your permissions changes.
The Specific Deadline and What Happens If You Miss It
Microsoft's official notice contains no mention of a grace period, partial functionality degradation, or any transition period after August 31. Independent analysis confirms the mechanism: requests to the deprecated endpoints simply stop being answered after the cutoff date. Your integration doesn't get throttled first, receive a final deprecation warning in the response headers, or continue at reduced functionality. It fails outright. This makes the migration genuinely urgent for any team whose tooling still uses the legacy endpoints — and genuinely simple for any team that correctly identifies no legacy dependency exists.
How to Know Whether You Are Actually Affected — Two-Minute Audit
This is the first action every team should take — before reading anything else about the migration itself. The affected/not-affected determination is binary and takes minutes if you know where to look.
Search Your Codebase for Legacy URL Patterns
Run a search across your entire codebase — including configuration files, environment variable definitions, plugin settings, and any automation scripts — for these two URL fragments:
// These URL patterns mean you ARE impacted — migrate immediately https://ssl.bing.com/webmaster/api.svc/pox/... https://ssl.bing.com/webmaster/api.svc/soap/... // This URL pattern means you are NOT impacted — no action required https://ssl.bing.com/webmaster/api.svc/json/...
If neither the pox nor soap pattern appears anywhere in your stack, you are not impacted. Stop reading and move on — this change requires no action from you.
Check Third-Party Plugins and SEO Tooling Separately
Your own codebase may be clean, but third-party plugins, rank-tracking tools, SEO platforms, or automation connectors that access Bing Webmaster Tools programmatically on your behalf may still be calling legacy endpoints. Check your active integrations specifically:
// Locations to check beyond your own code
- WordPress SEO plugins with Bing integration (Rank Math, Yoast, etc.)
- Rank tracking or reporting tools with Bing Webmaster Tools connectors
- Custom automation scripts built by previous team members or agencies
- CI/CD pipelines that include URL submission or crawl-status checks
- CMS plugins that auto-submit new content to search engines
Review Content-Type Headers in Outgoing API Requests
A secondary confirmation signal: if your API calls send Content-Type: application/xml or a SOAP envelope header rather than Content-Type: application/json, those requests use a legacy protocol regardless of the URL. Both signals — the endpoint URL and the Content-Type — should point to JSON/REST for a fully migrated integration.
The Summary of Changes — Exactly What Moves, Exactly What Stays
| Area | SOAP / POX (Deprecated) | JSON/REST (Use This) |
|---|---|---|
| Endpoint URL |
.../api.svc/soapor .../api.svc/pox/{Operation}
|
.../api.svc/json/{Operation}
|
| Content-Type header |
application/xml (POX) or SOAP envelope wrapper
|
application/json
|
| Request body format | XML — verbose, envelope-wrapped, schema-dependent | JSON — lightweight, natively parseable, no envelope required |
| Response body format | XML — requires an XML parser to read and process | JSON — natively parseable in every modern language without additional libraries |
| API key | Your existing key | Same key — no re-issuance required |
| Available API methods | Full method set | Identical full method set — no functionality removed |
| Quotas and rate limits | Existing quotas | Unchanged — same limits apply |
| Future development | None — retired | All new features and enhancements land here only |
How to Complete the Migration — Step by Step
Update Every Legacy Endpoint URL to the JSON/REST Equivalent
Replace every occurrence of api.svc/soap/ or api.svc/pox/ in your endpoint URLs with api.svc/json/. The operation name itself typically remains the same — only the protocol path segment changes.
// Before — legacy SOAP endpoint (RETIRE THIS) POST https://ssl.bing.com/webmaster/api.svc/soap/SubmitUrl Content-Type: text/xml; charset=utf-8 SOAPAction: "SubmitUrl" // After — JSON/REST endpoint (USE THIS) POST https://ssl.bing.com/webmaster/api.svc/json/SubmitUrl Content-Type: application/json
Reformat Request Bodies From XML to JSON
Replace all XML-formatted request bodies with JSON equivalents. The data structure and available parameters remain the same — only the serialisation format changes from XML to JSON. Most modern languages and frameworks handle this automatically through standard library serialisers once you've updated the Content-Type header.
// Before — XML request body (SOAP/POX format) <SubmitUrlRequest> <siteUrl>https://example.com</siteUrl> <url>https://example.com/new-page</url> </SubmitUrlRequest> // After — JSON request body (REST format) { "siteUrl": "https://example.com", "url": "https://example.com/new-page" }
Update Response Parsing From XML to JSON
Anywhere your code parses an XML response from a Bing Webmaster API call — using an XML parser, XPath expressions, or DOM traversal — replace that parsing logic with JSON parsing. Again, the data structure in the response mirrors the existing XML structure; only the format changes. In most languages, JSON parsing requires fewer lines of code and no additional libraries beyond what modern runtimes provide natively.
Keep Your Existing API Key — No Changes Required
Your existing Bing Webmaster Tools API key passes through to the JSON/REST endpoints exactly as it did to the SOAP and POX endpoints — same header, same authentication mechanism, same key value. Microsoft's notice explicitly confirms no re-issuance is required. Do not regenerate your API key as part of this migration; it's unnecessary and will temporarily disrupt your access while the new key propagates.
Test Every Migrated Endpoint Against a Non-Production Environment Before Cutover
After updating URLs, Content-Type headers, and request/response body formatting, test every updated endpoint against a non-production site or a test account before deploying to your live integration. Confirm that each call returns the expected response structure, that error responses parse correctly, and that your application handles both successful and error responses as expected in the JSON format.
Deploy and Monitor — Before August 31, 2026
Deploy your migrated integration and monitor API call success rates for several days before the August 31 deadline to confirm the migration is complete and clean. Any remaining errors that surface in monitoring after deployment give you time to diagnose and fix before the legacy endpoints go dark. Cutting over on August 30 leaves no diagnostic runway if a problem surfaces — plan to complete deployment by mid-August at the latest.
"The first thing I did when this announcement broke was run a dependency check across every client account that uses any form of automated Bing Webmaster Tools integration — URL submission scripts, reporting connectors, and crawl-status monitors. Most were already clean, running JSON/REST endpoints that an earlier infrastructure update had migrated to during a platform consolidation. Two accounts had legacy integrations built by previous agencies: one a Python script submitting new URLs to Bing using a SOAP wrapper library from 2019, and the other a reporting connector in a third-party rank-tracking tool still calling the POX endpoint for performance data pulls. The Python script migration took under an hour — swap the endpoint URL, replace the XML serialiser with Python's built-in json module, update the Content-Type header, rewrite the response parser from ElementTree to json.loads, and test. The third-party tool required a support ticket to the vendor, who confirmed a JSON/REST-migrated update was releasing before the deadline. The message for any team in a similar position: start the audit this week, because the actual migration work is fast — it's the discovery and vendor coordination that takes time."
Why Microsoft Is Making This Change — The Broader Platform Direction
This retirement isn't an isolated decision affecting only Bing Webmaster Tools. Microsoft Advertising is simultaneously transitioning its broader API platform from SOAP to REST to provide a more modern and efficient integration experience, with new API feature enhancements available only through REST starting October 1, 2026, and the Microsoft Advertising SOAP API scheduled for full deprecation on January 31, 2027. The Bing Webmaster Tools retirement is one component of a platform-wide modernisation across Microsoft's search and advertising infrastructure.
- 🔴 SOAP was the enterprise API standard of the early 2000s — XML-wrapped, verbose, complex
- 🔴 POX was a simplified XML alternative — lighter than SOAP but still XML-dependent
- 🔴 Both require XML parsing libraries and produce larger request/response payloads than necessary
- 🔴 Neither is actively developed further — all investment shifted to REST years ago
- 🔴 Supporting three protocols simultaneously creates maintenance overhead with no current user benefit
- 🟢 JSON is natively parseable in every modern language without additional libraries
- 🟢 REST is the web API standard — every modern framework, tool, and developer already knows it
- 🟢 Lighter payloads mean faster API responses and lower bandwidth consumption at scale
- 🟢 All future Bing Webmaster Tools API feature development happens here exclusively
- 🟢 Same functionality, same API key, same quotas — zero capability regression in the migration
What This Change Does NOT Affect — Clearing Up Common Confusion
Several adjacent systems and features share the Bing Webmaster Tools namespace, and practitioners unfamiliar with API-level details sometimes assume this retirement affects more than it does. The following are explicitly unaffected by the August 31 retirement:
| System | Affected by This Retirement? | Notes |
|---|---|---|
| Bing Webmaster Tools dashboard | Not affected | The web interface at bing.com/webmasters operates entirely independently of API protocol choice |
| Your API key | Not affected | Same key, same permissions, same quotas — no re-issuance required |
| IndexNow | Not affected | IndexNow is a separate push-notification protocol for instant URL submission — completely distinct from the Webmaster API |
| Bing Search rankings | Not affected | This is purely an API protocol change — it has no effect on how Bing crawls, indexes, or ranks your site |
| JSON/HTTP API endpoints | Not affected | Actively supported and under continued development — this is where Microsoft is investing |
Frequently Asked Questions
api.svc/soap and api.svc/pox endpoints simply stop being served after August 31 — Microsoft's notice explicitly states no grace period exists. Any integration still pointing at those URLs will fail outright, producing connection errors or HTTP error responses rather than the expected API data. URL submission automations stop submitting, performance data pulls return errors, crawl-issue monitors go dark. The fix remains the same migration work described in this guide — it just needs to happen before the deadline to avoid any service interruption.The Bottom Line
Bing Webmaster Tools retires its SOAP and POX/HTTP API endpoints on August 31, 2026 — a firm deadline with no grace period. Any integration still calling api.svc/soap or api.svc/pox URLs after that date fails outright. The migration itself is straightforward: update endpoint URLs to api.svc/json, swap XML request bodies for JSON, update response parsing, keep your existing API key unchanged, and test before deploying. Every API method, quota, rate limit, and permission remains identical — this is a protocol format change, not a functionality change. The time-sensitive action is the audit: search your codebase and third-party tool stack for the legacy URL patterns this week. If you find nothing, you're done. If you find a dependency, the actual migration work is fast — plan to have it deployed and monitored well before the August 31 deadline, not on it.
.webp)
Driven by advanced SEO expertise, deep marketing analytics, high-impact content strategy
With 5+ years of hands-on experience, I specialize in holistic search strategies that don’t just rank—they drive real, measurable business growth. I’ve worked across industries including healthcare, hospitality, legal, e-commerce, and professional services, helping brands dominate their target markets. My approach bridges the gap between raw data and creative execution. Every strategy I build is rooted in rigorous market analysis, structured SEO frameworks, and tailored content ecosystems—no templates, no shortcuts. Whether you’re a single-location brand or scaling across multiple cities, I create data-driven marketing systems designed to compound results and grow with you.
Need Help Migrating Your Bing Webmaster API?
DigitalArka can help you migrate from deprecated SOAP and POX/HTTP endpoints to the latest Bing Webmaster Tools JSON/REST APIs. We audit your integration, update API calls, improve technical SEO, and ensure your website remains fully compatible before the August 31, 2026 deadline.
Get Your Free API Migration Audit →