Search Yandex web results API

Endpoint facts

Method

GET

API path

/yandex/search

Auth

apiKey

Credits

3 credits/request

Platform

Yandex

Response schema

#/definitions/yandex.searchResponseDoc

MCP tool

yandex_search

Overview

Returns normalized organic Yandex web results for a query: title, destination URL, display URL, and snippet, with page-based pagination. Advertisements are not returned. Yandex challenges a portion of requests with a captcha; the service retries across browser profiles and returns 503 if every attempt is challenged, so callers should retry on 503. Results are localized by Yandex to the egress location. 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

- Yandex challenges a share of requests with a captcha, decided per request from the egress address and TLS identity. The service retries up to three times across different browser profiles on fresh connections and never tries to solve the captcha; if every attempt is challenged it returns `503`, and the call can simply be retried. - Yandex localizes results to the egress location, so the same query can return a different region's ranking across calls. - `description` is omitted for rows where Yandex shows no snippet (for example some social profiles); `display_url` is Yandex's host breadcrumb. - A response page with no organic results and no captcha marker is reported as `503` (parser drift), never as an empty success. - `pagination.next_page` is present only when Yandex offers a next page and `page` is below `10`.

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