Bing Webmaster API SOAP/POX Retirement 2026

Bing Webmaster API SOAP/POX Retirement 2026: What It Means for You

Bing is retiring the SOAP and POX versions of its Webmaster API on August 31, 2026. If that sentence means nothing to you, good news: it probably doesn't affect you at all. If you or a tool you use submits URLs to Bing programmatically, this is worth ten minutes of your time before the deadline hits.

Key Takeaway

Bing Webmaster Tools has always offered three ways to talk to its API: SOAP, POX, and JSON. After August 31, 2026, only JSON works. Nothing about your account, API key, quotas, or the dashboard itself changes. This is strictly a "how requests are formatted" change, not a "what you can do" change.

What's Actually Changing

Bing built its Webmaster API back when SOAP and POX (Plain Old XML) were the standard way services talked to each other. Both wrap every request and response in XML. JSON came later as the lighter, easier-to-work-with option, and Bing has quietly supported all three for years.

Now Bing is cleaning house. Starting August 31, 2026, any request sent to a SOAP or POX endpoint simply won't be answered. The URLs to watch for are anything containing /api.svc/soap or /api.svc/pox/. If your setup calls /api.svc/json/ instead, you're already on the safe side and don't need to touch anything.

Everything else stays put:

• Your API key works exactly as it does today, no reissuing needed
• Every API method (submitting URLs, pulling traffic stats, checking crawl issues) stays fully available through JSON
• Rate limits and quotas are unchanged
• Permissions on your verified sites are unchanged

Who This Actually Affects

Here's the part that matters most for a Blogger-based site: almost nobody reading this needs to do anything.

If you manage panstag.com (or any Blogger blog) through the Bing Webmaster Tools dashboard in your browser — adding sites, submitting sitemaps, checking crawl stats — none of that touches SOAP or POX. The dashboard has run on modern infrastructure for years. You can close this tab and move on.

This only matters if:

• You've built a custom script that submits URLs to Bing directly (some bloggers do this for bulk indexing after a big content migration)
• You use a third-party SEO tool, WordPress plugin, or automation workflow that calls the Bing API under the hood and was built years ago
• You've connected an MCP server or AI agent tool to Bing Webmaster Tools for automated URL submission — several of these exist now, and older versions may default to SOAP or POX

If none of those apply, you're not affected. If one does, the fix is usually a single URL change on the developer's end, not something you personally have to patch.

Proof Block

Screenshot to grab: Log into Bing Webmaster Tools, go to Settings > API Access, and capture your API key page. This shows readers that verification and key generation haven't changed at all — useful as a visual reassurance next to this section, and it's a screenshot you'll want blurred or cropped around the actual key before publishing.

Warning

If you're using any SEO automation tool that submits URLs to Bing on your behalf — including some bulk indexing plugins or AI-agent-based SEO assistants — check with the tool provider before August 31, 2026. If their backend still calls the old SOAP or POX endpoints and they haven't updated it, your automated submissions could silently stop working with no error shown to you. You'd only notice weeks later when new posts aren't getting indexed on Bing as fast as usual.

Quick Win

Since you're already in Bing Webmaster Tools checking this, take two minutes to confirm panstag.com's sitemap is submitted and your recent posts are showing as indexed under URL Inspection. If your blog gets any traffic from ChatGPT or Perplexity, this step directly feeds into that — both tools lean on Bing's index to find and cite content, something we cover in more depth in how to get cited in ChatGPT and Perplexity.

Who Doesn't Need to Worry: Table

Pro Tip

If you ever do end up needing to submit URLs to Bing faster than its normal crawl cycle, skip the API entirely and use IndexNow instead. It's a simpler ping-based protocol that Bing, and several other search engines, support together, and it's a better fit for a Blogger site than wiring up direct API calls. Worth knowing if you're also thinking about how AI crawlers reach your site, which ties into the crawler-access changes we covered in Cloudflare's new AI bot defaults for bloggers.

FAQ

Q1. Do I need to change anything in my Blogger dashboard? 

No. Blogger itself has no direct connection to the Bing SOAP or POX API. This change happens entirely on Bing's side and only affects developers calling the API directly.

Q2. Will my site stop showing up in Bing search after August 31, 2026? 

No. Indexing, crawling, and search visibility are completely separate from which API protocol is used to submit URLs. Your existing indexed pages aren't affected in any way.

Q3. What happens if a tool I use still calls the old SOAP or POX endpoint after the deadline?

Requests to those endpoints simply stop being answered. There's no grace period mentioned in Bing's notice, so any integration still pointed at the old URLs after August 31, 2026 will fail outright rather than being throttled or warned first.

Q4. Is this related to IndexNow? 

No, they're separate systems. IndexNow is a push-based notification protocol for telling search engines about new or updated content instantly. The Webmaster API (SOAP/POX/JSON) is used for a broader set of tasks like pulling performance data, checking crawl issues, and managing site settings.

Where can I check if I'm affected? Search your site's codebase, plugins, or automation tool settings for the strings api.svc/soap or api.svc/pox. If nothing turns up, you're clear.