Yandex Search API for web results
Search Yandex over HTTP and receive titles, links, and snippets as structured JSON — a third general index, especially useful for Russian-language and CIS coverage, through the same request shape as Google and Bing.
Endpoint
Results arrive in the same JSON shape as every other engine, so switching between them changes one field.
Clean titles, without the scraping artefacts.
The result description as Yandex renders it.
Set `time_range` and matching results include `published_date` as a UTC timestamp. Without it, the field is omitted.
Useful for
Russian and CIS web / Cross-checking / AI answers
A third general index behind the same call
Set `search_service` to `yandex` and the results come from Yandex. The endpoint, the authentication, and the response shape are the same as every other engine, so it drops into an existing Google- or Bing-backed code path unchanged.
Coverage Google and Bing rank differently
Yandex is the default search engine across much of the Russian-speaking web. Running it alongside Google is a coverage strategy, not a redundant call.
UTC timestamps when freshness matters
With `time_range` set to `day`, `week`, `month`, or `year`, results that expose a date carry `published_date` as an ISO-8601 UTC timestamp such as `2026-08-30T08:00:00Z`.
Search and page content in one call
`crawl_results` fetches the top N results and returns each as markdown, the same as on every other engine.
Standard Search parameters
`max_results` up to 50, plus `include_sites`, `exclude_sites`, `time_range`, and `language`.
What is a Yandex search API?
A Yandex search API is an HTTP interface that returns Yandex web results as structured data. Yandex is the primary general-purpose search engine in Russia and a significant index across the CIS, with its own ranking and a heavier mix of Russian-language pages than Google or Bing return for the same query. Search1API exposes Yandex as one of the search services on its Search endpoint, returning titles, links, and snippets in the same JSON shape it returns for its other engines. For an agent pipeline its value is a third independent web ranking, and a first-class path into pages a Google-only search under-represents.
Typical workflow
Search Yandex over HTTP and receive titles, links, and snippets as structured JSON — a third general index, especially useful for Russian-language and CIS coverage, through the same request shape as Google and Bing.
Send a query with `search_service` set to `yandex`.
Compare the result set against a `google` or `bing` query for the same terms.
Set `time_range` when you need `published_date`, and `crawl_results` when the answer needs page content rather than links.
One request, an independent ranking
A single call searches Yandex and returns results in the standard shape, so a third opinion on a query costs one credit and no new code.
bash
Best for
Queries where Russian-language or CIS sources are part of the answer.
Cross-checking a Google or Bing result set that looks thin or one-sided.
AI assistants that assemble an answer from more than one ranking.
Pipelines that want a third general engine on the same contract.
FAQ
Does Yandex have an official search API?
Yandex publishes XML and commercial search products under its own terms. Search1API covers the agent case by offering Yandex as one of the engines on its Search endpoint, billed in Search1API credits with no Yandex account to provision.
How does it differ from Google or Bing?
Yandex maintains its own index and ranking, with stronger coverage of Russian-language and CIS pages. The same query returns a different set of pages and a different order. Running it with Google is a coverage strategy rather than a redundant call.
When does a result include published_date?
When you set `time_range`. Matching results that expose a date include `published_date` as a UTC timestamp. Without `time_range`, Yandex omits the field.
Can I get page content with the results?
Yes. Set `crawl_results` to the number of top results you want fetched, and each page retrieved successfully includes a `content` field with the page text as markdown. Pages that cannot be retrieved are returned without `content` and are not charged.
What does a Yandex search cost?
One credit per search, and one additional credit for each page retrieved successfully through `crawl_results`. At the base top-up rate of $1 for 1,000 credits, that is $1 per 1,000 searches. Signup includes 100 free credits with no credit card.
Which other engines are supported?
The same Search endpoint accepts `google`, `bing`, and `duckduckgo`, plus vertical sources such as `reddit`, `x`, and `github`, and the Chinese-language engines `baidu`, `bingcn`, `360`, `quark`, `wechat`, and `bilibili` — 18 in total on one contract.