Bing Search API Deprecated: Complete Migration Guide (2026)

Why Bing Search API Was Deprecated

Microsoft officially deprecated the Bing Search API in August 2025 as part of a broader shift toward integrating search capabilities directly into Azure AI services and Copilot. If your application relied on Bing Web Search, Bing Image Search, or Bing News Search endpoints, those API keys will stop working.

This guide walks you through migrating to Searlo — a REST API that returns real-time Google search results with a similar JSON structure to what you're used to.

What You Need to Change

The migration has three parts: authentication, endpoint URLs, and response field mapping.

1. Authentication

Bing API used an Ocp-Apim-Subscription-Key header tied to an Azure subscription.

Searlo uses a simple X-API-Key header with a key you get from the dashboard:

2. Endpoint URLs

Every Searlo endpoint is a GET with the same header. The full list, with every parameter and what each call costs, is on the API reference.

Parameters

3. Response Field Mapping

Bing returned results in webPages.value[]. Searlo returns them in organic[]:

Map webPages.value[].url → organic[].link, webPages.value[].name → organic[].title, webPages.value[].snippet → organic[].snippet, webPages.value[].displayUrl → organic[].domain, and webPages.totalEstimatedMatches → totalResults. Bing's rankingResponse has no equivalent: Searlo's position is the rank on the results page.

What You Gain

• Google results instead of Bing — the results page your users actually see

• TOON format — token-optimized output for LLM/RAG pipelines (63% fewer tokens, per the format reference)

• MCP protocol — connect Claude, Cursor, and VS Code directly

• No subscription — one-time credit packs from $3.99, with 90-day validity for new users and unlimited credits for legacy accounts

What a call costs

A web search is one credit, and the endpoint cards on the API reference list the cost of every other call. A new account starts with 3,000 credits and no card. After that, credits come in one-time packs — the smallest is 5,000 credits for $3.99, and the Scale pack works out at $0.30 per 1,000 queries. Nothing renews and nothing is billed monthly; the pricing page has every pack and its per-1,000 rate, beside the published rates of the APIs people migrate from.

Test the mapping with one call

Run the same query against both APIs and diff the fields you use:

The response carries organic[] with position, title, link, domain and snippet, plus totalResults, searchTime and credits in the envelope — the same shape the homepage playground shows, which is a real capture of exactly this call.

If the reader is a language model

Bing's JSON was never meant for a prompt. Add &format=toon and the same results come back as text — a header line, then one block per result — that a model reads in 63% fewer tokens, per the format reference in the docs. If the caller is an agent rather than your own code, skip HTTP altogether: Searlo ships an MCP server that Claude, Cursor and any MCP client can call as a tool, with the same key in the same header.

Testing Your Migration

1. Sign up at dashboard.searlo.tech (3,000 free credits)

2. Update your base URL and API key header

3. Run your existing test suite

4. Verify response field mapping

5. Deploy

Most developers complete the migration in under an hour because the REST pattern is very similar.

Need Help?

Check the API documentation for the full endpoint reference, or reach out at [email protected].

bash
# Old (Bing)
curl -H "Ocp-Apim-Subscription-Key: YOUR_BING_KEY" \
  "https://api.bing.microsoft.com/v7.0/search?q=test"

# New (Searlo)
curl -H "X-API-Key: YOUR_SEARLO_KEY" \
  "https://api.searlo.tech/api/v1/search/web?q=test"

json
// Searlo response
{
  "organic": [
    {
      "position": 1,
      "title": "Result Title",
      "link": "https://example.com/page",
      "domain": "example.com",
      "snippet": "Description text..."
    }
  ],
  "totalResults": 85000,
  "searchParameters": {
    "q": "test",
    "gl": "us"
  }
}

bash
curl "https://api.searlo.tech/api/v1/search/web?q=postgres+connection+pooling&num=3" \
  -H "x-api-key: $SEARLO_KEY"