Yahoo Search API endpoint
Use Crawlora's Yahoo Search News API to extract supported public Yahoo Search data as structured JSON. This page includes request parameters, cURL examples, response schema, error behavior, credit cost, and a Playground link for testing before integration.
/yahoo-search/newsReturns Yahoo's news-search results for a query: title, destination URL, description, source, and relative publish age. Results are fetched from Yahoo's own server-rendered news-search page (news.search.yahoo.com) -- a distinct product from the yahoo-news family, which covers the www.yahoo.com/news portal itself. Yahoo wraps every result link in its own click-tracking redirect; this endpoint always returns the decoded destination URL, never the raw redirect link. Developers commonly use this endpoint for data enrichment, monitoring, research dashboards, internal automation, and agent-native workflows that need repeatable structured public web data. Authentication uses the documented Crawlora headers, and usage is metered with the credit cost shown on this page.
Request parameters are generated from the active endpoint catalog. Required values must be sent before Crawlora can call the upstream public web data source.
| Parameter | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
| q | string | Yes | Search query | ||
| x-api-key (header) | string | Yes | API key required |
curl -X GET "https://api.crawlora.net/api/v1/yahoo-search/news?q=coffee" \ -H "x-api-key: $CRAWLORA_API_KEY"
Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.
Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.
| Plan | Price | Included credits | Daily cap | Rate limit | Overage |
|---|---|---|---|---|---|
| Free | $0/mo | 2,000 | 500 daily credits | 5/min | No overage |
| Starter | $9/mo | 20,000 | 5,000 daily credits | 15/min | $0.75/1,000 overage credits when enabled |
| Growth | $29/mo | 100,000 | 25,000 daily credits | 45/min | $0.45/1,000 overage credits when enabled |
| Pro | $79/mo | 400,000 | No daily cap | 120/min | $0.30/1,000 overage credits |
| Business | $199/mo | 1,200,000 | No daily cap | 300/min | $0.20/1,000 overage credits |
| Enterprise | $499/mo | 5,000,000 | No daily cap | 1,000/min | $0.12/1,000 overage credits |
This endpoint is executed through Crawlora's managed scraping infrastructure.
Some targets require real browser execution because the data is loaded through JavaScript, dynamic rendering, or interaction-like browser behavior.
For supported endpoints, Crawlora can route requests through a managed browser cluster. This allows Crawlora to execute JavaScript, load dynamic content, apply browser-level request behavior, and normalize the rendered result into JSON.
You do not need to operate your own Playwright, Puppeteer, Chrome, proxy, queue, or retry infrastructure.
- Yahoo wraps every result link in its own click-tracking redirect (`r.search.yahoo.com/...`); `url` in the response is always the decoded destination URL, never the raw redirect link. - A query with no matches returns a genuine empty `results` array, not an error. Example response: ```json { "code": 200, "msg": "OK", "data": { "query": "chatgpt", "results": [ { "position": 1, "title": "I Asked ChatGPT How To Retire Early at 55", "url": "https://www.aol.com/articles/asked-chatgpt-retire-early-55.html", "description": "I asked ChatGPT how to retire at 55. The roadmap it built was mostly right.", "source": "MoneyLion", "age": "29 minutes ago", "thumbnail_url": "https://s.yimg.com/fz/api/res/example.jpg" } ] } } ```
Crawlora does not silently return bad data when the upstream page cannot be used.
| Status | Common failure case |
|---|---|
| 400 | Invalid input or missing required parameter |
| 429 | Plan or endpoint rate limit exceeded |
| 500 | Internal execution error |
| 502 | Upstream platform failed, returned unusable HTML, or served a challenge page that could not be resolved |
When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.
| Status | Description | Schema |
|---|---|---|
| 400 | Bad Request | #/definitions/app.Response |
| 429 | Too Many Requests | #/definitions/app.Response |
| 500 | Internal Server Error | #/definitions/app.Response |
| 503 | Service Unavailable | #/definitions/app.Response |
{
"code": 200,
"msg": "OK",
"data": {
"query": "chatgpt",
"results": [
{
"position": 1,
"title": "I Asked ChatGPT How To Retire Early at 55",
"url": "https://www.aol.com/articles/asked-chatgpt-retire-early-55.html",
"description": "I asked ChatGPT how to retire at 55. The roadmap it built was mostly right.",
"source": "MoneyLion",
"age": "29 minutes ago",
"thumbnail_url": "https://s.yimg.com/fz/api/res/example.jpg"
}
]
}
}Request schema
No body schema
Response schema
#/definitions/yahoosearch.newsResponseDoc
| Field | Type | Required | Enum | Bounds | Example | Description |
|---|---|---|---|---|---|---|
| code | integer | No | 200 | |||
| data | yahoosearch.NewsResponse | No | ||||
| data.query | string | No | chatgpt | |||
| data.results | array | No | ||||
| data.results[].age | string | No | 29 minutes ago | |||
| data.results[].description | string | No | ||||
| data.results[].position | integer | No | 1 | |||
| data.results[].source | string | No | AFP | |||
| data.results[].thumbnail_url | string | No | ||||
| data.results[].title | string | No | OpenAI announces ChatGPT update | |||
| data.results[].url | string | No | https://example.com/article | |||
| msg | string | No | OK |
Use environment variables for secrets and keep Crawlora API keys server-side.
curl -X GET "https://api.crawlora.net/api/v1/yahoo-search/news?q=coffee" \
-H "x-api-key: $CRAWLORA_API_KEY"Crawlora is designed for responsible structured public web data workflows. Customers are responsible for using Crawlora in compliance with applicable laws, third-party rights, target-platform rules, and Crawlora terms.
Read Crawlora terms