Yandex Market API
API health
- 24h health
- Normal
- 24h average time
- —
- Last checked
- September 26, 2026 at 18:05 (UTC)
- Healthy / normal
- Available
- Limited
- Mostly down
Last 24 hours
Last 30 days
How health is measured
- Health = the share of calls that returned data, in percent. Empty results, failures and unknown outcomes do not count as returning data.
- Levels: 90% and above is healthy, 70% and above is available, 40% and above is limited; anything lower is mostly down.
- A period (the last 24 hours, one hour or one day) gets a score only once it has at least 50 calls. Periods with fewer calls show as normal: a few failures among a handful of calls do not mean the API is down.
- Calls include real customer calls and our own daily probe calls. Request errors (wrong parameters, no balance) are excluded.
- Average time counts only calls that completed normally: response time for sync calls, acceptance to completion for async ones.
By period
| Time (UTC) | Status | Health | Average time |
|---|---|---|---|
| 2026-09-26 18:00 - 18:59 | Normal | — | — |
| 2026-09-26 17:00 - 17:59 | Normal | — | — |
| 2026-09-26 16:00 - 16:59 | Normal | — | — |
| 2026-09-26 15:00 - 15:59 | Normal | — | — |
| 2026-09-26 14:00 - 14:59 | Normal | — | — |
| 2026-09-26 13:00 - 13:59 | Normal | — | — |
| 2026-09-26 12:00 - 12:59 | Normal | — | — |
| 2026-09-26 11:00 - 11:59 | Normal | — | — |
| 2026-09-26 10:00 - 10:59 | Normal | — | — |
| 2026-09-26 09:00 - 09:59 | Normal | — | — |
| 2026-09-26 08:00 - 08:59 | Normal | — | — |
| 2026-09-26 07:00 - 07:59 | Normal | — | — |
| 2026-09-26 06:00 - 06:59 | Normal | — | — |
| 2026-09-26 05:00 - 05:59 | Normal | — | — |
| 2026-09-26 04:00 - 04:59 | Normal | — | — |
| 2026-09-26 03:00 - 03:59 | Normal | — | — |
| 2026-09-26 02:00 - 02:59 | Normal | — | — |
| 2026-09-26 01:00 - 01:59 | Normal | — | — |
| 2026-09-26 00:00 - 00:59 | Normal | — | — |
| 2026-09-25 23:00 - 23:59 | Normal | — | — |
| 2026-09-25 22:00 - 22:59 | Normal | — | — |
| 2026-09-25 21:00 - 21:59 | Normal | — | — |
| 2026-09-25 20:00 - 20:59 | Normal | — | — |
| 2026-09-25 19:00 - 19:59 | Normal | — | — |
| 2026-09-26 | Normal | — | — |
| 2026-09-25 | Normal | — | — |
| 2026-09-24 | Normal | — | — |
| 2026-09-23 | Normal | — | — |
| 2026-09-22 | Normal | — | — |
| 2026-09-21 | Normal | — | — |
| 2026-09-20 | Normal | — | — |
| 2026-09-19 | Normal | — | — |
| 2026-09-18 | Normal | — | — |
| 2026-09-17 | Normal | — | — |
| 2026-09-16 | Normal | — | — |
| 2026-09-15 | Normal | — | — |
| 2026-09-14 | Normal | — | — |
| 2026-09-13 | Normal | — | — |
| 2026-09-12 | Normal | — | — |
| 2026-09-11 | Normal | — | — |
| 2026-09-10 | Normal | — | — |
| 2026-09-09 | Normal | — | — |
| 2026-09-08 | Normal | — | — |
| 2026-09-07 | Normal | — | — |
| 2026-09-06 | Normal | — | — |
| 2026-09-05 | Normal | — | — |
| 2026-09-04 | Normal | — | — |
| 2026-09-03 | Normal | — | — |
| 2026-09-02 | Normal | — | — |
| 2026-09-01 | Normal | — | — |
| 2026-08-31 | Normal | — | — |
| 2026-08-30 | Normal | — | — |
| 2026-08-29 | Normal | — | — |
| 2026-08-28 | Normal | — | — |
Use the market action on Yandex. Accepts these parameters: max_price, min_price, city, region, sort, and keyword. Returns these fields: category, title, rating_scale, and review_count.
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.
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 | market | Capability identifier, fixed value. |
keyword | body.params | Not declared | Yes | - | 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. |
city | body.params | enum | No | - | Specifies the target city slug (e.g., moscow, saint_petersburg) for the Yandex market action. Must match an allowed enum value and cannot be substituted for location on map searches.Allowed valueschelyabinskkazankrasnodarkrasnoyarskmoscownizhny_novgorodnovosibirskomskpermrostov_on_donsaint_petersburgsamaraufavolgogradvoronezhyekaterinburg |
max_price | body.params | Not declared | No | - | 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. |
min_price | body.params | Not declared | No | - | 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. |
region | body.params | Not declared | No | - | Accepts a numeric city region code for the Yandex market action, defaulting to 213 (Moscow). This is an internal region identifier, not an RU country code. Providing an explicit city parameter overrides this setting. |
sort | body.params | enum | No | - | Controls sorting order per Yandex action. Accepts relevance or distance for search; popular or top_rated for market; and newest (gateway default), relevance, highest, or lowest for reviews. Values cannot be used across different actions.Allowed valuespopulartop_rated |
limit | body.params | integer (1–100) | No | 20 |
Code samples
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": "market",
"params": {
"keyword": "ноутбук"
}
}'[OpenAPI definition (JSON)]Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.
Response example
There is no real sample for these example parameters yet: this shows the response shape and fields from the contract, with … as placeholders. It is not the result of a real call.
{
"id": "req_…",
"platform": "yandex",
"action": "market",
"results": [
{
"id": …,
"url": …,
"title": …,
"price": …,
"currency": …,
"rating": …,
"rating_scale": …,
"rating_count": …,
"review_count": …,
"purchase_count": …,
"category": …,
"shop_name": …,
"shop_rating": …,
"stock": …,
"is_available": …,
"image_url": …,
"platform": …
}
],
"count": …,
"billing": { … },
"quota": { … }
}Response fields
Business data is in results. The table lists the fields a record can contain; values the source does not provide are never made up.
| Field | Meaning |
|---|---|
id | The record's unique ID on the source platform. Unique only within one platform; IDs can repeat across platforms. |
url | Link to the record on the source platform. |
title | Title. null when the platform has no titles (for example text-only posts). |
price | Price as a number without a currency symbol; see currency. |
currency | Currency code of the price (for example CNY, USD). If price is present but currency is null, do not assume a currency. |
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. |
rating_count | Number of people who rated. null means not disclosed, not 0. |
review_count | Number of reviews, for product and business capabilities. null means not disclosed, not 0. |
purchase_count | Keeps the platform's own meaning |
category | Category name in the source platform's own taxonomy, not normalized across platforms. |
shop_name | Keeps the platform's own meaning |
shop_rating | Keeps the platform's own meaning |
stock | Keeps the platform's own meaning |
is_available | Keeps the platform's own meaning |
image_url | Image link. Capabilities with several images may return an image_urls array. |
platform | Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok). |
Errors and billing
- 401
- Missing or invalid key. Authentication runs before parameter checks, so unauthenticated requests never see the parameter schema.
- 422
- Wrong parameter name or value. The error lists the parameters and allowed values this capability accepts and the closest match; it happens before any charge.
- 402
- Insufficient balance. Top up first.
- 429
- Per-minute request limit reached. Wait for Retry-After and try again.
- 503
- Could not complete right now. Any charge for the call goes back to your balance automatically, and the billing receipt in the response states the actual outcome, including when it is not yet known. Do not resend blindly.
- 200 empty
- The request completed without data and is not charged (billing.reason = empty_result_refunded).
Official references
Used only to check objects and terms. They do not imply authorization or endorsement of EveryInfra by the platform.
- Yandex Market: Delivery Conditions Depend on City and Product ↗
Official Yandex Market delivery terms tie shipping methods, schedules, and fees directly to the city and specific product, with exact conditions shown on product and checkout pages; this serves to clarify that initial product search prices do not constitute a guaranteed final delivery total or delivery commitment.
Checked 2026-09-05