Overview
Early access. Tell us what you're building and we'll set you up. Contact us
Lempile's Yahoo Search API returns Yahoo's web results in SerpApi's Yahoo format, from real browsers. It works like the Google Search API: create a search, poll it, read the archive. Use engine=yahoo on the same GET /search.json route, with the same API key.
Yahoo applies site: filters such as site:linkedin.com/in, so it suits searches for LinkedIn profiles.
Quickstart#
Create a search:
curl -sS "https://api.lempile.com/search.json?engine=yahoo&p=site%3Alinkedin.com%2Fin%20%22Head%20of%20Growth%22%20Paris" \
-H "X-API-KEY: your-api-key"A new search answers 202 with search_metadata.status: "Processing". Poll its search_metadata.json_endpoint:
curl -sS "https://api.lempile.com/searches/{search_id}.json" \
-H "X-API-KEY: your-api-key"Stop polling when search_metadata.status is Success or Error. Once a search has finished, the same search sent again within the hour returns its stored result at once with 200, unless you add no_cache=true. While the first one is still Processing, the same request starts another search.
Parameters#
| Parameter | Required | What it does |
|---|---|---|
engine |
Yes | yahoo. |
p |
Yes | The query, as you would type it on Yahoo. Operators such as site: and quotes work. Yahoo names it p, not q. |
b |
No | The position of the page's first result, from 1. A Yahoo page has 7 results: page 2 starts at b=8, page 3 at b=15. |
yahoo_domain |
No | search.yahoo.com (the default) or a country's Yahoo, such as fr.search.yahoo.com. |
vc |
No | A country, as 2 letters (fr). |
vl |
No | A language, such as lang_fr. |
vm |
No | The adult filter: r (strict), i (moderate) or p (off). |
vs |
No | Only results from these domains or endings, comma-separated (.fr,.com). |
vf |
No | Only this file type, such as pdf. |
no_cache |
No | true runs a new search instead of returning the same search made in the last hour. |
output |
No | json (the default) or html, the page as Yahoo showed it. |
device |
No | desktop, the only device for now. |
async |
No | Accepted for SerpApi compatibility. A new search always answers 202 and is polled. |
vc, vl, vm, vs and vf go to Yahoo as you send them. A search needs the search.write scope, and reading the archive needs search.read, as for Google.
Result#
{
"search_metadata": {
"id": "search_id",
"status": "Success",
"json_endpoint": "https://api.lempile.com/searches/search_id.json",
"raw_html_file": "https://api.lempile.com/searches/search_id.html",
"yahoo_url": "https://search.yahoo.com/search?p=site%3Alinkedin.com%2Fin+%22Head+of+Growth%22+Paris",
"created_at": "2026-11-15 10:00:00 UTC",
"processed_at": "2026-11-15 10:00:09 UTC",
"total_time_taken": 3.2
},
"search_parameters": {
"engine": "yahoo",
"p": "site:linkedin.com/in \"Head of Growth\" Paris",
"yahoo_domain": "search.yahoo.com",
"device": "desktop"
},
"search_information": {
"query_displayed": "site:linkedin.com/in \"Head of Growth\" Paris",
"organic_results_state": "Results for exact spelling"
},
"organic_results": [
{
"position": 1,
"title": "Jane Example - Head of Growth - Example Company | LinkedIn",
"link": "https://fr.linkedin.com/in/jane-example",
"displayed_link": "https://fr.linkedin.com › in › jane-example",
"source": "LinkedIn",
"snippet": "Head of Growth at Example Company · Location: Paris · 500+ connections on LinkedIn."
}
],
"pagination": {
"current": 1,
"next": "https://search.yahoo.com/search?p=site%3Alinkedin.com%2Fin+%22Head+of+Growth%22+Paris&b=8",
"other_pages": {
"2": "https://search.yahoo.com/search?p=…&b=8",
"3": "https://search.yahoo.com/search?p=…&b=15"
}
}
}linkis the result's own address, read from Yahoo's page. When Yahoo's page wraps it in its click link, that link is inredirect_link; most results have none.displayed_linkis the address as Yahoo shows it, with›between its parts: readlinkfor the address itself.paginationlists the pages Yahoo offers, with Yahoo's own addresses. For the next page, send the same search with thebofpagination.next(b=8, thenb=15...).- Ads are never in
organic_results.
How it runs#
Each search opens a real browser on one of Lempile's US IPs and reads Yahoo's results page. vc and yahoo_domain choose the country of the results. Lempile's IPs wait between Yahoo searches, so a burst of searches queues: they stay Processing and run in turn, and search_metadata may show runner_status_detail: "yahoo_proxy_paced" while one waits.
Errors#
The request errors are those of the Google Search API, with the same format:
| HTTP | Code | Meaning |
|---|---|---|
400 |
invalid_search_parameters |
A parameter is missing or invalid, for example no p, a b below 1, a device other than desktop, or a yahoo_domain that is not Yahoo's. The message says which. |
403 |
forbidden |
The API key does not include search.write (or search.read to read the archive). |
429 |
workspace_search_queue_full |
The workspace already has too many Yahoo searches queued or running. |
503 |
proxy_unavailable |
Lempile has no IP that can run a Yahoo search right now. Retry later. |
A search that ends with status: "Error" says why in error and in search_metadata.status_detail:
status_detail |
Meaning |
|---|---|
yahoo_blocked |
Yahoo refused the search on all 3 tries. |
yahoo_consent_wall |
Yahoo showed its consent page on all 3 tries. |
yahoo_search_failed |
Yahoo's page showed no results list. |
search_queue_timeout |
The search could not leave the queue in time. |
Was this page helpful?