POST /api/bing/news/articles/search
Price: 10 credits
Search Bing News articles by keyword. Returns matching news articles with title, source publisher, external article url, publish time, snippet and image. Supports recency and sort filters.
Search Bing News by keyword across world, national and local news sources. Each result has title, web_url (external publisher link), source, published/published_at, snippet and image. Category feeds (Sports, Technology, World, Business...) are covered by using the category name as the keyword. Use count to control how many results to return, freshness to limit recency, sort for ordering.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)keyword string required — Search keyword (examples: "earthquake"; minLength: 1)count integer required — Max number of results (min: 1)freshness string — Restrict results to a recency window (default: "any"; one of: "any", "hour", "day", "week", "month")sort string — Result ordering (default: "relevance"; one of: "relevance", "date")market string — Region and language market (default: "en-US"; one of: "en-US", "en-GB", "en-CA", "en-AU", "en-IN", "en-IE", "en-NZ", "en-PH", "en-ZA", "en-MY", "en-SG", "de-DE", "de-AT", "de-CH", "fr-FR", "fr-BE", "fr-CA", "fr-CH", "es-ES", "es-MX", "es-AR", "es-US", "es-CL", "it-IT", "nl-NL", "nl-BE", "pt-BR", "pt-PT", "pl-PL", "ru-RU", "tr-TR", "sv-SE", "da-DK", "fi-FI", "nb-NO", "ar-SA", "he-IL", "ja-JP", "ko-KR", "zh-CN", "zh-HK", "zh-TW", "th-TH", "id-ID", "vi-VN", "hi-IN")@type string (default: "BingNewsArticle")web_url string nullablesource string nullableis_on_msn boolean (default: false)published string nullablepublished_at string nullablesnippet string nullableimage string nullable422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.X-Retry-After — Seconds to wait before retrying. Present only on 429.