Yahoo Search API for web results
Query Yahoo web results over HTTP in the same request shape as every other engine. Yahoo’s organic results are supplied by Bing, so reach for this when you specifically need the Yahoo result set.
Endpoint
Results arrive in the same JSON shape as every other engine, so existing parsing continues to work.
Clean titles, without the scraping artefacts.
The result description as Yahoo renders it.
Set crawl_results and the top results return markdown.
Useful for
Yahoo-specific checks / SERP monitoring / AI answers
Read this before you pick Yahoo over Bing
Set `search_service` to `yahoo` and the results come from Yahoo. The endpoint, the authentication, and the response shape are the same as every other engine — but the results themselves will look familiar, because Bing supplies them.
Bing supplies the organic results
Under the long-standing Microsoft–Yahoo search alliance, Yahoo’s organic web listings come from Bing. On a ten-query developer sample, `yahoo` and `bing` returned identical link sets seven times.
When to use it anyway
Yahoo controls its own presentation and ranking on top of those listings, so use this engine when the Yahoo result set is the thing being checked — SEO monitoring, regional coverage, or reproducing what a Yahoo user sees.
When to use `bing` instead
For general web coverage in an agent pipeline, query `bing` directly. Running both costs two credits for what is usually one result set.
Standard Search parameters
`max_results` up to 50, plus `include_sites`, `exclude_sites`, and `time_range`.
What is a Yahoo search API?
A Yahoo search API is an HTTP interface that returns Yahoo web results as structured data. Yahoo does not publish a general web search API for third parties, and its organic listings have been supplied by Bing since the Microsoft–Yahoo search alliance, so the two engines return substantially the same pages. Search1API exposes Yahoo as one of the search services on its Search endpoint, returning titles, links, and snippets in the same JSON shape it returns for its other engines. The honest use for it is narrow: check it when the Yahoo result set specifically matters, and query `bing` when what you want is general web coverage.
Typical workflow
Query Yahoo web results over HTTP in the same request shape as every other engine. Yahoo’s organic results are supplied by Bing, so reach for this when you specifically need the Yahoo result set.
Send a query with `search_service` set to `yahoo`.
Read the structured result list of titles, links, and snippets.
Compare against a `bing` query when you need to know whether the two diverge.
One request, the Yahoo result set
A single call searches Yahoo and returns results in the standard shape. Because the Search endpoint accepts an array of query objects, a Yahoo and a Bing query can be sent together and diffed.
bash
Best for
SEO monitoring that tracks Yahoo rankings specifically.
Reproducing what a Yahoo user sees for a given query.
Diffing Yahoo against Bing to see where the two diverge.
Coverage checks in markets where Yahoo retains share.
FAQ
Is Yahoo search the same as Bing?
For organic web results, largely yes. Yahoo’s listings are supplied by Bing under their search alliance. On a ten-query developer sample, `yahoo` and `bing` returned identical link sets seven times out of ten.
Then why use the Yahoo engine at all?
Because Yahoo controls presentation and ranking on top of the supplied listings, and because some work is specifically about Yahoo — SEO monitoring, regional coverage checks, or reproducing a Yahoo user’s result page. For general web coverage, query `bing` and save the credit.
Is there an official Yahoo search API?
Yahoo does not publish a general web search API for third-party applications. Search1API covers the case by offering Yahoo as one of the engines on its Search endpoint.
What does a Yahoo search cost?
One credit per search, and one additional credit for each page retrieved successfully through `crawl_results`. At the base top-up rate of $1 for 1,000 credits, that is $1 per 1,000 searches. Signup includes 100 free credits with no credit card.
Can I query Yahoo and Bing in one request?
Yes. The Search endpoint accepts an array of query objects, so both can be sent in a single batch and compared. Each item is billed individually and a failed item is not charged.
Which other general engines are supported?
The same Search endpoint accepts `google`, `bing`, and `duckduckgo`, alongside vertical sources and the Chinese-language engines, for 17 engines in total on one contract.