Yandex Reviews API

Q: What do the likes and dislikes on a review tell me?

like_count and dislike_count record how other Yandex users reacted to a review: many likes suggest a view other customers share, and many dislikes suggest they dispute it. Use them to weight reviews when you summarize sentiment. When like_count or comment_count is null, Yandex is not showing that figure, and it should not be read as zero.

POST

API health

24h health: Normal

Healthy / normal
Available
Limited
Mostly down

Last 24 hours

Last 30 days

Collect reviews of a business on Yandex Maps, up to 200 per call. Each review has text, score, date, likes and dislikes, and the owner's reply. Pass a map place link or business ID, not a Market product link. sort can put lowest_rated complaints first.

Send POST https://api.everyinfra.com/api/v1/social with platform set to yandex and action set to reviews. Price $1.39 per 1,000 requests ($0.001389 per call). Failed calls and empty results are not charged. Synchronous. For slow jobs add "mode": "async" to the body, take the job_id and poll.

Yandex Reviews reads the reviews of one business on Yandex Maps, given its map page link or numeric business ID as url. Every row holds what the reviewer wrote, the score they gave, when they posted it and their display name, plus how many users liked or disliked the review, the owner's reply, and the business's name, ID, overall rating and review count. Chains with branches on the map, agencies managing local reputation and analysts use it to follow sentiment branch by branch and see how owners answer criticism.

Choose the order with sort: newest for fresh feedback, lowest_rated to read complaints first, top_rated for praise or relevance for Yandex's own ranking; these values belong to reviews and differ from those of Yandex Search and Market. owner_reply shows whether and how the business answered, which matters most on low ratings. language sets the query language, English by default, and each row's language code is the platform's guess, which can be wrong. To find businesses by keyword first, use Yandex Search.

AI prompt

Please help me write a data collection script with the EveryInfra Yandex Reviews endpoint (yandex/reviews).

How the endpoint works:
- Request: POST https://api.everyinfra.com/api/v1/social with the header Authorization: Bearer <API key>. Read the key from the EVERYINFRA_API_KEY environment variable and never hard-code it.
- In the request body, set platform to yandex and action to reviews, and put the parameters inside params.
- Required parameters:
  - url: Specifies a full Yandex Map place URL or a direct businessId string for the reviews action. This parameter does not accept Yandex Market product links.
- Optional parameters:
  - language: 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.
  - sort: 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. (allowed: lowest_rated / newest / relevance / top_rated)
  - limit: The most rows to return in this call, an integer from 1 to 200. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. (default: 20)
- Returns a list of records. Main fields of each record: id, url, text, rating, rating_scale, posted_at, language, like_count, dislike_count, comment_count, author_name, owner_reply; 16 fields in total, full list at https://api.everyinfra.com/api/v1/social/catalog?platform=yandex.
- Example request body:
{
  "platform": "yandex",
  "action": "reviews",
  "params": {
    "url": "https://yandex.com/maps/org/tanuki/1036014863/reviews/"
  }
}
- Price: $1.39 per 1,000 requests; failed and empty results are not charged.
- For dozens or hundreds of targets, add "mode": "async" to the body: you get a job_id at once and poll GET https://api.everyinfra.com/api/v1/jobs/{job_id} for the result.
- On 422, fix the request using the suggested parameter names and allowed values in the error; on 429 or 503, wait for Retry-After and try again.

Before writing code, ask me which targets I need, how many, which fields, and what output format I want; then confirm the plan and the rough cost with me.

Request parameters

Name	In	Type	Required	Default	Description
`Authorization`	header	`string`	Yes	-	Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository.
`platform`	body	`string`	Yes	`yandex`	Platform identifier, fixed value.
`action`	body	`string`	Yes	`reviews`	Capability identifier, fixed value.
`url`	body.params	`string`	Yes	-	Specifies a full Yandex Map place URL or a direct businessId string for the reviews action. This parameter does not accept Yandex Market product links.
`language`	body.params	`string`	No	-	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.
`sort`	body.params	`string (enum)`	No	-	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.Allowed values`lowest_ratednewestrelevancetop_rated`
`limit`	body.params	`integer (1–200)`	No	`20`	The most rows to return in this call, an integer from 1 to 200. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge.

Code samples

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": "reviews",
  "params": {
    "url": "https://yandex.com/maps/org/tanuki/1036014863/reviews/"
  }
}'

OpenAPI definition (JSON)Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.

Response example

json

{  "id": "req_…",  "platform": "yandex",  "action": "reviews",  "results": [    {      "id": "fiG_U8XT6pO3RSY1ZJERNYEL7cZavC",      "url": "https://yandex.com/maps/org/tanuki/1036014863/",      "text": "все хорошо ",      "rating": 5,      "posted_at": "2026-09-25T19:20:48.046000+00:00",      "language": "RU",      "like_count": 0,      "dislike_count": 0,      "comment_count": 0,      "author_name": "•••",      "owner_reply": "",      "business_id": "1036014863",      "business_name": "Тануки",      "business_rating": 5,      "business_review_count": 11416,      "platform": "yandex",      "rating_scale": 5    },    {      "id": "HsGQp2Ee5wuRfg4_tAgpnWVc6q4tEMK",      "text": "Всем здоровья!\nПосетил уголок японской жизненной силы икигай!\nНамсте",      "rating": 5,      "posted_at": "2026-09-25T19:20:26.902000+00:00",      "language": "RU",      "like_count": 0,      "dislike_count": 0,      "comment_count": 0,      "author_name": "•••",      "owner_reply": "",      "business_id": "1036014863",      "platform": "yandex",      "rating_scale": 5    }  ],  "count": 20,  "billing": {    "charged": …,    "charged_usd": …,    "balance_after_usd": …,    …  },  "quota": { … }}

Response fields

Business data is in results. The table lists the fields a record can contain; values the platform does not show are never made up.

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.
`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).
`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.
`posted_at`	Publish time in ISO 8601, UTC (for example 2026-08-07T12:34:56+00:00). Non-standard strings from the platform are passed through as is, so parse defensively. null means the platform does not disclose it.
`language`	Content language code (for example zh, en) as judged by the platform; it can be wrong.
`like_count`	Likes. null means the platform or this capability does not disclose it; it is not 0.
`dislike_count`	Keeps the platform's own meaning
`comment_count`	Comments. null means not disclosed, not 0.
`author_name`	Author's display name.
`owner_reply`	Keeps the platform's own meaning
`business_id`	Keeps the platform's own meaning
`business_name`	Keeps the platform's own meaning
`business_rating`	Keeps the platform's own meaning
`business_review_count`	Keeps the platform's own meaning
`platform`	Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok).

FAQ

Which Yandex link or ID goes in `url`?

The business's Yandex Maps link, such as https://yandex.com/maps/org/tanuki/1036014863/reviews/, or only the numeric business ID it contains, 1036014863 in that link. Links to Yandex Market products point to a different dataset and do not work here.

Why are `business_rating` and `business_review_count` repeated on every row?

They describe the business as a whole, its overall score and total number of reviews on Yandex Maps, so they are the same for every review of that business. Store them once per business and use them to put a page of reviews in context; the score of each individual review is rating, read with rating_scale.

What do the likes and dislikes on a review tell me?

like_count and dislike_count record how other Yandex users reacted to a review: many likes suggest a view other customers share, and many dislikes suggest they dispute it. Use them to weight reviews when you summarize sentiment. When like_count or comment_count is null, Yandex is not showing that figure, and it should not be read as zero.

Errors and billing

401: Missing or invalid key.
402: Insufficient balance. Top up first.
422: Invalid parameter name or value. Fix it using the suggestions in the error. No charge.
429: Per-minute request limit reached. Wait for Retry-After, then try again.
503: Could not complete. The held charge is returned to your balance. If the outcome is unknown, verify it before you retry.
200 empty: No data. No charge.

Errors

Official references

Used only to check objects and terms. They do not imply authorization or endorsement of EveryInfra by the platform.

Yandex Maps: Original Reviews and UI Translations ↗
Official Yandex documentation states that reviews written in a language different from the interface language may display translations alongside an option to switch back to the original text; therefore, the language parameter in this API cannot be treated as a direct filter for the review's original written language or as a translation guarantee.
Checked 2026-09-05