Yahoo Life API endpoint
Use Crawlora's Yahoo Life Article API to extract supported public Yahoo Life 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-life/articleReturns a single Yahoo Life article's full content: title, description, author, publish/update time, section, image, keywords, original publisher, and body paragraphs. Accepts a canonical www.yahoo.com/lifestyle article URL, such as one returned by the home story stream. 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 |
|---|---|---|---|---|---|
| url | string | Yes | Canonical www.yahoo.com/lifestyle article URL | ||
| x-api-key (header) | string | Yes | API key required |
curl -X GET "https://api.crawlora.net/api/v1/yahoo-life/article" \ -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.
- `provider` is the original outlet the story is syndicated from when applicable, otherwise `"Yahoo Life"`. - `paragraphs` can be an empty array for an article whose metadata loaded but whose body content did not render -- this is returned as a normal `200`, not an error. A response missing *both* metadata and body paragraphs is treated as an upstream error (parser drift or a block), not a silent empty success. - A `url` that isn't a `www.yahoo.com` URL under `/lifestyle/` returns `400`. `www.yahoo.com` hosts several unrelated verticals (news, finance, sports, ...), so both the hostname and the `/lifestyle/` path prefix are required. Example response: ```json { "code": 200, "msg": "OK", "data": { "url": "https://www.yahoo.com/lifestyle/article/water-bottles-bag-charms-and-analog-everything-100-back-to-school-trends-kids-actually-care-about-in-2026-133000932.html", "title": "Water bottles, bag charms and analog everything: 100 back-to-school trends kids actually care about in 2026", "description": "Going back to school used to be simple: buy the stuff on the list.", "author": "Erin Donnelly", "published_at": "2026-08-11T13:30:00Z", "updated_at": "2026-08-11T13:30:00Z", "section": "Yahoo Lifestyle", "image_url": "https://s.yimg.com/lo/mysterio/api/example/bts-hub-header.png", "keywords": ["college students", "school supplies", "water bottle"], "provider": "Yahoo Life", "paragraphs": [ "Tiny humans, huge shopping list. The littlest schoolers are messy, filled to the brim with emotions." ] } } ```
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 |
| 404 | Not Found | #/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": {
"url": "https://www.yahoo.com/lifestyle/article/water-bottles-bag-charms-and-analog-everything-100-back-to-school-trends-kids-actually-care-about-in-2026-133000932.html",
"title": "Water bottles, bag charms and analog everything: 100 back-to-school trends kids actually care about in 2026",
"description": "Going back to school used to be simple: buy the stuff on the list.",
"author": "Erin Donnelly",
"published_at": "2026-08-11T13:30:00Z",
"updated_at": "2026-08-11T13:30:00Z",
"section": "Yahoo Lifestyle",
"image_url": "https://s.yimg.com/lo/mysterio/api/example/bts-hub-header.png",
"keywords": [
"college students",
"school supplies",
"water bottle"
],
"provider": "Yahoo Life",
"paragraphs": [
"Tiny humans, huge shopping list. The littlest schoolers are messy, filled to the brim with emotions."
]
}
}Request schema
No body schema
Response schema
#/definitions/yahoolife.articleResponseDoc
| Field | Type | Required | Enum | Bounds | Example | Description |
|---|---|---|---|---|---|---|
| code | integer | No | 200 | |||
| data | yahoolife.ArticleResponse | No | ||||
| data.author | string | No | ||||
| data.description | string | No | ||||
| data.image_url | string | No | ||||
| data.keywords | array | No | ||||
| data.paragraphs | array | No | ||||
| data.provider | string | No | ||||
| data.published_at | string | No | ||||
| data.section | string | No | ||||
| data.title | string | No | ||||
| data.updated_at | string | No | ||||
| data.url | string | No | ||||
| 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-life/article" \
-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