Last reviewed: 2026-09-09.
On August 11, 2025, Microsoft retired all standalone Azure Bing Search APIs, including Bing News Search v7 (official retirement announcement). Existing instances have been decommissioned, and new signups on Azure are permanently disabled.
Microsoft recommends developers migrate to Grounding with Bing Search inside Azure AI Agents. However, if your application requires a standalone REST API for raw JSON news data without paying for enterprise Azure AI agent compute, you need an independent provider.
Here is a step-by-step guide to translating your Bing News queries, parameters, and payloads into Currents API.
Parameter Mapping: Bing News Search vs. Currents API
| Bing News v7 Parameter | Currents API Parameter | Description & Syntax |
|---|---|---|
q |
query (Boolean) / keywords
|
query supports AND/OR/NOT with parentheses (query=(chatgpt OR gemini) AND regulation). keywords takes plain terms, quoted phrases, OR, and - exclusions — Boolean AND/NOT do not work there. |
mkt |
language + country
|
mkt=en-US combines language and country; Currents takes them as two parameters: language=en and country=US
|
cc |
country |
2-letter ISO country code (country=GB) |
setLang |
— (no direct equivalent) |
setLang sets the language of Bing's user-interface strings, not article content. Choose Currents' language from the article language your application needs; do not copy setLang mechanically |
category |
category |
News topic, comma-separated (category=business,technology) |
count |
page_size |
Results per request; plan caps: 20 (Free), 50 (Builder), 100 (Professional), 200 (Scale) |
offset |
page_number |
Bing is offset-based; Currents is page-based. For offsets aligned to your page size: page_number = floor(offset / page_size) + 1. Valid range is 1–180. |
freshness |
start_date / end_date
|
STRICT RFC 3339 timestamps (2026-09-01T00:00:00Z) — bare dates are rejected. Maximum span: 7 days (Free), 31 days (Builder), 90 days (Professional), 180 days (Scale) |
sortBy |
— (reverse-chronological) | Articles return newest-first by publication time; there is no sort parameter |
Ocp-Apim-Subscription-Key |
Authorization header |
Send Authorization: Bearer YOUR_API_KEY with every request |
Python Migration Example
Before (Bing News Search API v7):
import requests
endpoint = "https://api.bing.microsoft.com/v7.0/news/search"
headers = {"Ocp-Apim-Subscription-Key": "BING_KEY"}
params = {"q": "artificial intelligence", "mkt": "en-US", "count": 20}
response = requests.get(endpoint, headers=headers, params=params)
articles = response.json().get("value", [])
After (Currents API):
import requests
endpoint = "https://api.currentsapi.services/v1/search"
headers = {"Authorization": "Bearer YOUR_API_KEY"}
params = {
"keywords": "artificial intelligence",
"country": "US",
"language": "en",
"page_size": 20
}
response = requests.get(endpoint, headers=headers, params=params, timeout=10)
response.raise_for_status()
articles = response.json().get("news", [])
Translating Bing query patterns (before → after)
Pagination. Bing paginates with offset + count; Currents paginates with page_number + page_size. For an offset aligned to your page size, use page_number = floor(offset / page_size) + 1. Non-aligned offsets need rounding (which repeats or drops boundary articles), so pick an aligned page size when you can. Note that pagination is bounded: page_number runs 1–180, and the API rejects a request once the offset passes your plan's retrievable limit: 100 results on Free and 1,000 on Builder.
# Before (Bing): 20 results starting at item 40
params = {"q": "electric vehicles", "mkt": "en-US", "count": 20, "offset": 40}
# After (Currents): floor(40 / 20) + 1 = page 3
params = {
"keywords": "electric vehicles",
"language": "en",
"country": "US",
"page_size": 20,
"page_number": 3,
}
Language and market. mkt=en-US bundles language and country into one code; Currents expresses them as two parameters:
# Before (Bing)
params = {"q": "electric vehicles", "mkt": "en-US", "count": 20}
# After (Currents): one market becomes two parameters
params = {"keywords": "electric vehicles", "language": "en", "country": "US", "page_size": 20}
Boolean operators. Bing's q accepts AND/OR/NOT and parentheses. In Currents, that syntax belongs to the query parameter — keywords does not evaluate AND/NOT:
# Before (Bing)
params = {"q": "(chatgpt OR gemini) AND regulation", "mkt": "en-US", "count": 20}
# After (Currents): boolean syntax lives in `query`
params = {"query": "(chatgpt OR gemini) AND regulation", "language": "en", "country": "US", "page_size": 20}
Freshness windows. Bing's freshness is not a publication-date filter: per Microsoft's Bing News Search documentation it accepts discovery-recency values such as freshness=Week (also Day, Month) alongside date ranges, tuning which results Bing's index surfaces — not what datePublished must say. Currents has no identical discovery-freshness parameter; a start_date/end_date publication-time window approximates the intent, but the semantics differ and results should not be expected to match one-for-one. Currents requires two STRICT RFC 3339 timestamps — a bare date such as 2026-09-01 is rejected — and the span is plan-capped (≤ 7 days Free, ≤ 31 Builder, ≤ 180 Scale). The window must also fall inside your plan's lookback, which is 30 days on Free, so requests for older dates are rejected:
# Before (Bing)
params = {"q": "electric vehicles", "freshness": "2026-09-01..2026-09-08", "mkt": "en-US", "count": 20}
from datetime import datetime, timedelta, timezone
# After (Currents): a recent 7-day window in strict RFC 3339
end = datetime.now(timezone.utc).replace(microsecond=0)
start = end - timedelta(days=7)
params = {
"keywords": "electric vehicles",
"language": "en",
"country": "US",
"page_size": 20,
"start_date": start.strftime("%Y-%m-%dT%H:%M:%SZ"),
"end_date": end.strftime("%Y-%m-%dT%H:%M:%SZ"),
}
Response Field Mapping
| Bing News v7 field | Currents API field | Notes |
|---|---|---|
name |
title |
|
url |
url |
Canonical publisher URL |
snippet / description
|
description |
~300-character preview on the free plan |
datePublished |
published |
Timestamp formatted as 2026-03-24 11:10:00 +0000 (space separator, UTC offset without a colon). Parse it with datetime.strptime(value, "%Y-%m-%d %H:%M:%S %z")
|
image.thumbnail.contentUrl |
image |
May be empty |
category |
category |
|
provider[0].name |
— | No dedicated source field; derive a publisher label from the url domain |
webSearchUrl |
— | No equivalent |
totalEstimatedMatches |
— | No equivalent; the response reports the returned page number instead |
Bing answer groups (news answers, spell-suggestions), total match counts, and server-side ranking controls have no Currents equivalent. One more caveat when you validate the migration: different providers do not guarantee identical result ranking — the same query can return a different ordering and a slightly different result set, so compare coverage and freshness rather than position-by-position order.
Key Differences & Trade-offs
- Self-Service Onboarding: You do not need an active Azure Subscription or enterprise agreement. You can generate a free key in 30 seconds at currentsapi.services/en/register.
- Predictable USD Quotas: Rather than complex Azure transaction tiering, Currents uses transparent quotas: 250 requests/day free, and $69/mo for 75,000 calls a month (2,500/day) on Builder.
- Structured Response Objects: Currents returns standardized JSON objects containing title, description, canonical source URL, image, author, language, category, and a published timestamp.
This post first appeared on the Currents API blog.
Top comments (0)