Yahoo Shopping Article API

Endpoint facts

Method

GET

API path

/yahoo-shopping/article

Auth

apiKey

Credits

2 credits/request

Platform

Yahoo Shopping

Response schema

#/definitions/yahooshopping.articleResponseDoc

Overview

Returns a single Yahoo Shopping article's full content: title, description, author, publish/update time, section, image, keywords, original publisher, and body paragraphs. Accepts a canonical shopping.yahoo.com 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 Yahoo Shopping syndicates the story from (e.g. "Yahoo Life"), separate from Yahoo Shopping itself. - `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 `shopping.yahoo.com` article URL returns `400`. Example response: ```json { "code": 200, "msg": "OK", "data": { "url": "https://shopping.yahoo.com/style/clothing/article/stylists-say-these-are-the-4-must-have-denim-trends-for-fall-175919542.html", "title": "Stylists say these are the 4 must-have denim trends for fall", "description": "Hint: Skinny jeans are still out — but the newest go-to might surprise you.", "author": "Jessica Teich", "published_at": "2026-08-06T17:59:19Z", "updated_at": "2026-08-06T17:59:19Z", "section": "Clothing", "image_url": "https://s.yimg.com/lo/mysterio/api/example/denim-hero.jpg", "keywords": ["Derek Warburton", "Katelyn Joseph", "denim"], "provider": "Yahoo Life", "paragraphs": [ "Every year when fall creeps back in, I slip into mourning over two equally major things..." ] } } ```

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