# Yandex Search API (yandex.search)

- Canonical page: https://everyinfra.com/en/yandex-api/search
- Endpoint: POST https://api.everyinfra.com/api/v1/social with {"platform": "yandex", "action": "search", "params": {...}}
- Price: $0.001389 per call ($1.39 per 1,000 requests); failed calls and empty results are not charged
- Returns: list, default 20, max 100 per call
- Mode: sync; add "mode": "async" for slow tasks

Yandex Search looks up businesses and places on Yandex Maps by `keyword`, such as museums in Saint Petersburg or coffee shops in Moscow, and returns one row per place: name, descriptive text, address, city, phone, website, business categories, rating with its review count, coordinates and whether it is open at the moment. Sales teams, franchise operators and market analysts use it to map the local businesses of a city, build lead lists of shops and clinics, or check how a chain's branches are rated against their neighbors.

This is a map search, not a web search, so `keyword` should name a kind of business or a specific place. Set the city with `location`, which defaults to Moscow, and narrow by type with `category`. `city` and `address` are passed through exactly as Yandex writes them, so standardize spellings before you group rows by city. A null `review_count` means Yandex does not show the count, not that a place has no reviews, and `is_open_now` describes the moment of the call.

## Health

- Live health (24h percent, hourly and daily trends): https://api.everyinfra.com/api/v1/social/availability?platform=yandex&action=search

## Parameters

| name | type | required | default | description |
|---|---|---|---|---|
| keyword | not declared | yes | not declared | Specifies search terms for Yandex actions, targeting local places in search and e-commerce items in market. Map listings and product catalogs query separate underlying datasets. |
| category | enum: atms / auto_repair / banks / bars_pubs / beauty_salons / burgers / cafes / car_wash / cinemas / coffee_shops / dentists / dry_cleaning / fast_food / fitness_clubs / gas_stations / government_services / grocery_stores / hookah_bars / hospitals / hotels / kindergartens / museums / none / pharmacies / pizza / restaurants / schools / shopping_malls / sports_facilities / sushi_rolls / veterinary_clinics | no | not declared | Filters place categories for the Yandex search action (e.g., restaurants, cafes, coffee_shops, hotels, or none to clear). This parameter does not apply to Yandex Market product categories and must align with the specified keyword and city. |
| lang | enum: en / kk / ru / tr / uk | no | not declared | Sets the response language for the Yandex search action, accepting ru, en, kk, tr, or uk. This controls search interface locale and does not guarantee translation of user-generated review content. |
| language | not declared | no | not declared | Sets the fallback interface language for Yandex actions, defaulting to ru for search and en for reviews. Explicitly passing lang on the search action overrides this parameter. |
| location | not declared | no | not declared | Sets the target city for the Yandex search action, defaulting to Moscow. This parameter takes city names and is distinct from numeric Yandex Market region IDs. |
| max_price | not declared | no | not declared | Sets the upper price boundary for the targeted Yandex action when used in conjunction with min_price. It does not filter by maximum user rating. Filtering uses whole numbers: decimals round up (145.98 becomes 146). |
| min_price | not declared | no | not declared | Sets the lower price limit for Yandex actions, representing product price on market and local place price tier on search. These values reflect target-platform price points rather than API usage fees. Filtering uses whole numbers: decimals round down (39.81 becomes 39). |
| sort | enum: distance / relevance | no | not declared | Controls sorting order per Yandex action. Accepts relevance or distance for search; popular or top_rated for market; and newest (default), relevance, top_rated, or lowest_rated for reviews. Values cannot be used across different actions. |
| limit | integer (1–100) | no | 20 | The most rows to return in this call, an integer from 1 to 100. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. |

## Response fields (items in `results`)

| field | meaning |
|---|---|
| id | The record's unique ID on the platform. Unique only within one platform; IDs can repeat across platforms. |
| url | Link to the record on the platform. |
| name | Name of the object itself, for account, product and business capabilities. |
| text | Body text with HTML removed, returned in full and never cut short (on a few platforms the list results themselves carry only an excerpt; the platform's field notes say so). |
| address | Full address, passed through as is. |
| city | City name in the platform's language, not normalized. |
| country | Country or region: a full name or an ISO code depending on the platform, not normalized. |
| categories | platform-native meaning |
| rating | Rating. **The scale varies by platform**: rating_scale on the same row gives the maximum (usually 5; Booking, Douban, iQIYI and NAVER use 10). Convert with rating_scale before comparing across platforms, or the comparison can come out backwards. |
| rating_scale | Maximum of rating in the same row: 5 for five-star scales, 10 for ten-point scales. Present only when the row has a rating. |
| review_count | Number of reviews, for product and business capabilities. null means not disclosed, not 0. |
| phone | Contact phone number, passed through without format normalization. |
| website | External website entered by the account or business. |
| lat | platform-native meaning |
| lng | platform-native meaning |
| is_open_now | platform-native meaning |
| platform | Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok). |

## Example

```bash
curl -X POST 'https://api.everyinfra.com/api/v1/social' \
  -H "Authorization: Bearer $EVERYINFRA_API_KEY" \
  -H 'Content-Type: application/json' \
  --data-raw '{
  "platform": "yandex",
  "action": "search",
  "params": {
    "keyword": "музей Санкт-Петербург"
  }
}'
```

```python
import os
import requests

response = requests.post(
    "https://api.everyinfra.com/api/v1/social",
    headers={"Authorization": f"Bearer {os.environ['EVERYINFRA_API_KEY']}"},
    json={
        "platform": "yandex",
        "action": "search",
        "params": {
            "keyword": "музей Санкт-Петербург",
        },
    },
    timeout=120,
)
print(response.status_code)
print(response.json())
```

## Response example

Real response to the example request above, captured 2026-10-24T18:28:34Z. `results` and `count` are real with personal information (names, handles, avatars, profile links, contact details) removed; the list keeps the first 2 of 10. `id`, `billing` and `quota` differ on every call, so only their shape is shown.

```text
{
  "id": "req_…",
  "platform": "yandex",
  "action": "search",
  "results": [
    {
      "id": "•••",
      "url": "https://yandex.com/maps/org/yusupovskiy_dvorets_na_moyke/1484458665/",
      "name": "Юсуповский дворец на Мойке",
      "text": "наб. реки Мойки, 94, Санкт-Петербург",
      "address": "Санкт-Петербург, набережная реки Мойки, 94",
      "city": "Санкт-Петербург",
      "country": "Россия",
      "categories": [
        "Музей",
        "достопримечательность",
        "культурный центр"
      ],
      "rating": 5,
      "review_count": 20295,
      "phone": [
        "•••"
      ],
      "website": "https://yusupov-palace.ru/ru?yclid=1047539603321651199",
      "lat": 59.929384,
      "lng": 30.29887,
      "is_open_now": false,
      "platform": "yandex",
      "rating_scale": 5
    },
    {
      "id": "•••",
      "url": "https://yandex.com/maps/org/muzey_yantarya_solnechnogo_kamnya/198760504469/",
      "name": "Музей Янтаря - Солнечного камня",
      "text": "Невский просп., 51, Санкт-Петербург",
      "address": "Санкт-Петербург, Невский проспект, 51",
      "city": "Санкт-Петербург",
      "country": "Россия",
      "categories": [
        "Музей",
        "магазин парфюмерии и косметики",
        "магазин бижутерии"
      ],
      "rating": 4.599999904632568,
      "review_count": 97,
      "phone": [
        "•••"
      ],
      "website": "http://www.jantarspb.ru/?yclid=14418971870541905919",
      "lat": 59.931873,
      "lng": 30.34891,
      "is_open_now": false,
      "platform": "yandex",
      "rating_scale": 5
    }
  ],
  "count": 10,
  "billing": {
    "charged": …,
    "charged_usd": …,
    "balance_after_usd": …,
    …
  },
  "quota": { … }
}
```

## FAQ

### Is this a Yandex web search API?

No. Yandex Search looks up places on Yandex Maps, the way you would search the map for museums or banks in a city, and returns place records with addresses, phone numbers, ratings and coordinates rather than web pages. Product listings from Yandex Market are a separate dataset, read with the Yandex Market capability.

### Which parameters set the city and the language?

`location` sets the city searched and defaults to Moscow; give a city name, not a numeric region code. `lang` sets the interface language to `ru`, `en`, `kk`, `tr` or `uk` and overrides `language` when you send both; `language` defaults to `ru` here. Neither one promises that text in the results comes back translated.

### How do `category` and the price filters narrow a search?

`category` keeps one type of business, such as `restaurants`, `cafes`, `pharmacies`, `museums` or `banks`, and `none` applies no category; pick one that agrees with your keyword and city. `min_price` and `max_price` set the map's own price filter for businesses, a different measure from a product price on Yandex Market and never the cost of the call. `sort` orders by `relevance` or `distance`.

## Also

- Capability catalog (no key): https://api.everyinfra.com/api/v1/social/catalog?platform=yandex
- OpenAPI: https://everyinfra.com/openapi.json · Agents guide: https://everyinfra.com/agents.md