POST /v1/search · engine=yandex
Yandex Search API
Yandex's own web index, strongest for Russian-language queries, through the same /v1/search call as Google. No Yandex Cloud account, folder or IAM token: add engine: "yandex".
Overview
What the Yandex Search API does
Yandex runs its own web index and map database, the strongest for Russian-language queries and for Russia and much of the CIS. Use it for Russian and CIS markets, where Yandex's index and Yandex Maps cover more than Google.
/v1/search with engine: "yandex" returns Yandex's organic web results: title, link, domain, displayed_link and snippet, up to 15 per page. country picks the Yandex region (ru, ua, kz, tr, us, de and other large markets) and page pages through results; num above one page walks Yandex's pages, 1 credit per page that returned results. There are no ads or answer boxes, and time and safe: "active" aren't available on Yandex.
What you get
-
results[]array - Organic results: position, title, link (the destination URL), domain, displayed_link, snippet, and date / published_at when the engine shows one.
-
related_searches[]array - Related queries, when the engine shows them.
-
metaobject - request_id, credits_used, cached, latency_ms, parse_quality, engine (the provider that answered) and route (each provider attempt with outcome and ms).
Request
curl https://api.serpkite.com/v1/search \
-H "Authorization: Bearer $SERPKITE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"q":"кофемашина","country":"ru","engine":"yandex"}'Response (live response, trimmed)
{
"request": {
"country": "ru",
"endpoint": "search",
"engine": "yandex",
"language": "en",
"num": 10,
"page": 1,
"q": "кофемашина"
},
"results": [
{
"domain": "wildberries.ru",
"link": "https://www.wildberries.ru/catalog/721142966/detail.aspx",
"position": 1,
"snippet": "Доп. опции кофемашины. капучинатор; одновременное приготовление двух чашек; поддержание температуры готового кофе; подогрев чашек; подсветка...",
"title": "Кофемашина капсульная и рожковая с капучинатором"
},
{
"domain": "ozon.ru",
"link": "https://www.ozon.ru/product/kofemashina-avtomaticheskaya-zernovaya-kofevarka-s-kapuchinatorom-i-kofemolkoy-20-bar-3559390167/",
"position": 2,
"snippet": "Кофемашина автоматическая зерновая, кофеварка с капучинатором и кофемолкой, 20 Бар, предсмачивание, 12 программ, регулировка высоты стакана, управление по Wi-Fi...",
"title": "Кофемашина автоматическая зерновая, кофеварка с..."
}
],
"meta": {
"request_id": "req_01J8ZK4M6Q2V7",
"credits_used": 1,
"cached": false,
"engine": "yandex",
"route": [
{
"provider": "yandex",
"outcome": "ok",
"ms": 770
}
],
"latency_ms": 795,
"parse_quality": "ok"
}
}
Every response also carries X-Credits-Used, X-Credits-Remaining,
X-Cache and X-Tokens-Estimate headers.
Run this query in the playground
One key, many engines
Yandex through SerpKite
- Same key, same envelope and the same SDK call as Google: only
enginechanges. meta.enginenames the provider that answered andmeta.routelists every attempt. A result is never relabelled.engine: "auto"keeps Google first and falls back to Yandex and the other engines only when Google fails. How fallback works- Failed, blocked and empty attempts are free; you pay only for the provider that answered.
Everything Yandex serves on SerpKite
-
Yandex Search API
POST /v1/search · engine=yandex -
Yandex Maps API
POST /v1/maps · engine=yandex -
Yandex Places API
POST /v1/places · engine=yandex -
Place Details
POST /v1/place · engine=yandex
See all engines on the multi-engine search page or in the providers reference.
engine=auto answered by Yandex (illustrative)
{
"request": {
"endpoint": "search",
"engine": "auto",
"q": "кофемашина"
},
"meta": {
"engine": "yandex",
"route": [
{
"provider": "google",
"outcome": "blocked",
"ms": 2140
},
{
"provider": "yandex",
"outcome": "ok",
"ms": 640
}
]
}
}Reference
Parameters
The parameters /v1/search accepts, in the JSON body or the query string.
| Name | Type | Default | Description |
|---|---|---|---|
q
required
|
string | – | The search query. Required. Up to 2,048 characters. |
engine
|
string | string[] | "yandex" for this page. "auto" tries Google first and falls back to other engines; a list such as ["google", "yandex"] limits the route to those engines. | |
country
|
string | us | Country to search from, as a two-letter ISO code (us, gb, de, in…). Defaults to the country a location ends in. |
language
|
string | en | Interface language, as a language code with an optional region (en, de, pt-BR, zh-TW…). |
num
|
integer | 10 | Results per call, 1–100. Up to 10 returns one page of 10 (1 credit); above 10 on search and news fetches whole pages as a depth bundle, and 100 costs 7 credits instead of 10. On images a page holds up to 100 images and num (default all) is how many of them come back. |
page
|
integer | 1 | Results page, 1–10. Each page is billed separately. |
include_domains
|
string[] | – | Only results from these sources, up to 20: a domain (example.com, subdomains match), a path prefix (github.com/org) or a TLD (.gov). Compiled to site: operators and enforced on the results. Search, news, images, videos. |
exclude_domains
|
string[] | – | Drop results from these sources, up to 20, same formats as include_domains. Search, news, images, videos. |
format
|
string | json | Response format. markdown is LLM-ready prose; compact is JSON with only the fields agents need. Values: json, compact, markdown. |
fields
|
string | – | Comma-separated projection, e.g. results.title,results.link,knowledge_graph. Cuts tokens. |
max_age
|
integer | – | Accept a cached result up to this many seconds old. Cache hits cost 50% of the credits. |
Full reference, error codes and headers are in the /v1/search reference. Queue up to 100 requests at half price with POST /v1/batches.
Use cases
What people build with the Yandex Search API
Russian and CIS SEO
Check where a site ranks on Yandex for Russian-language keywords, by region.
Local data for Russia
Yandex Maps lists organisations, phones, hours and ratings across Russia and the CIS.
Agents that read Russian
Give an agent Yandex results as JSON or Markdown for Russian-language research.
Pricing
Yandex Search API pricing
Cost per call
1 credit
per page of results
- From $0.60 per 1,000 calls at volume.
- Credits never expire. No subscription.
- Failed, empty and blocked calls are refunded.
- 2,500 free credits = 2,500 calls, then 1,000 credits a month.
For reference: Serper lists Google searches at $1.00 per 1k on its entry tier and $0.30 at its best tier, and its credits expire after 6 months. SerpKite credits cost $1.00 to $0.60 per 1k.
| Pack | Price | Per 1k credits | Per 1k calls | Calls per pack |
|---|---|---|---|---|
| Starter | $10 | $1.00 | $1.00 | 10,000 |
| Growth | $50 | $0.80 | $0.80 | 62,500 |
| Pro | $300 | $0.60 | $0.60 | 500,000 |
FAQ
Yandex Search API: common questions
Keep exploring
Related APIs and integrations
Start building
Start with the Yandex Search API
2,500 free credits, then 1,000 every month. No credit card.