Yahoo Entertainment Article API

Endpoint facts

Method

GET

API path

/yahoo-entertainment/article

Auth

apiKey

Credits

2 credits/request

Platform

Yahoo Entertainment

Response schema

#/definitions/yahooentertainment.articleResponseDoc

Overview

Returns a single Yahoo Entertainment article's full content: title, description, author, publish/update time, section, image, keywords, original publisher, and body paragraphs. Accepts a canonical www.yahoo.com/entertainment/ article URL, such as one returned by the home or category story streams. 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.

Authentication

Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.

Billing

Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.

Credit cost

2 credits/request

Charged response

Successful 2xx responses

Infrastructure behavior

This endpoint is executed through Crawlora's managed scraping infrastructure.

• Proxy strategy: managed automatically where needed
• Browser rendering: enabled for supported targets that require rendered HTML or JavaScript execution
• Browser cluster: supported dynamic workloads can be routed through distributed browser instances
• Retry behavior: automatic retry/fallback may be used depending on endpoint type
• Challenge handling: challenged pages or unusable upstream HTML are detected and surfaced clearly when they cannot be used
• Billing: credits are charged only for successful 2xx responses
• Observability: responses include request context where available

Browser cluster behavior

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.

Response behavior

- `provider` is the original outlet the story is syndicated from when applicable, otherwise `"Yahoo Entertainment"`. - `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` whose host isn't `www.yahoo.com`, or whose path isn't under `/entertainment/`, returns `400` -- Yahoo Entertainment lives on the shared `www.yahoo.com` domain alongside unrelated verticals such as `/news/`, `/finance/`, and `/sports/`. Example response: ```json { "code": 200, "msg": "OK", "data": { "url": "https://www.yahoo.com/entertainment/articles/childs-play-french-artist-saypes-051719401.html", "title": "Child's play: French artist Saype's giant ephemeral frescoes takeover Swiss alpine resort", "description": "The latest works in a series of experimental and ephemeral paintings by French land artist Saype are currently on display on the high slopes of Swiss alpine resort Villars-sur-Ollon.", "author": "Tokunbo Salako", "published_at": "2026-08-14T05:17:19Z", "updated_at": "2026-08-14T05:17:19Z", "section": "Yahoo Entertainment", "image_url": "https://s.yimg.com/lo/mysterio/api/example/saype-hero.jpg", "keywords": ["Swiss ski resort", "French artist", "French land artist"], "provider": "Euronews", "paragraphs": [ "The latest works in a series of experimental and ephemeral paintings by French land artist Saype are currently on display." ] } } ```

Error behavior

Crawlora does not silently return bad data when the upstream page cannot be used.

When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.

Related