Yahoo Search Local API

Endpoint facts

Method

GET

API path

/yahoo-search/local

Auth

apiKey

Credits

3 credits/request

Platform

Yahoo Search

Response schema

#/definitions/yahoosearch.localResponseDoc

Overview

Returns Yahoo's local-business-search results for a query: name, category, price range, address, phone, open status, rating, and review count. Location is resolved from the query text itself, the same way a user would type into Yahoo's own local search box (e.g. "pizza near seattle wa"), not a separate coordinate parameter. Results are fetched from Yahoo's own server-rendered local-search page. 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

3 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

- `id` is Yahoo's own internal listing id, carried in case a caller wants to distinguish repeat listings. Yahoo's list view does not link out to the business's own website -- there is no `url` field. - `rating` is a 0-5 integer star count (Yahoo's own list view does not expose a finer-grained decimal rating). - A query with no local-business intent (or no matches) returns a genuine empty `results` array, not an error. Example response: ```json { "code": 200, "msg": "OK", "data": { "query": "pizza near seattle wa", "results": [ { "position": 1, "id": "36383310", "name": "Serious Pie Downtown", "category": "Pizza", "price_range": "$$", "address": "2001 4th Ave", "phone": "(206) 838-7388", "open_status": "Closed", "rating": 4, "review_count": 4870, "image_url": "https://s.yimg.com/fz/api/res/example.jpg" } ] } } ```

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