yandex-market-api

Install

Copy the MissiaL/yandex-market-api repository into the skills folder as yandex-market-api. When working with the Market API, look methods up with scripts/lookup_endpoint.py first and show me any mutating request before sending it.

This is third-party code. Review the repository files before installing.

What it does

The skill teaches an agent to work with the Yandex Market Partner API for sellers: catalog, prices, stocks, orders, shipments, returns, reports and buyer chats. It bundles the full spec from Market's official repository and a Python script that lists sections, searches operations by Russian or English keywords and prints the parameters of a given operation. SKILL.md explains businessId versus campaignId, how warehouse groups decide which stocks API version to use, the FBY, FBS, DBS and Express models, cursor pagination and error codes, including 420 for rate limits. The agent is told to ask for confirmation before changing prices, stocks or order statuses.

Who it is for. For Yandex Market sellers and developers building integrations with the seller cabinet.

Example request

Find the method for sending stocks to Market for an FBS store and build the request without sending it

Limitations

You need an Api-Key from the seller cabinet. The API has no sandbox, so mutating calls hit the live store. Rate limits are not in the spec, only in Market's docs. The spec is a snapshot in the repository and ages until the author refreshes it; the rebuild script the README mentions is not part of the repository. No license is specified. The README has no install steps, so the skill is installed by copying the folder.

How to disable. Delete the yandex-market-api folder from the agent's skills directory.

Security check

• Following the skill, the agent can change prices, stocks and order statuses in the live store
• The API has no sandbox
• It requires the seller cabinet Api-Key

README in short

The README briefly lists the contents: SKILL.md as the entry point, the Partner API spec from Market's official repository with added section and placement model tags, a flat index of methods and a lookup script. It notes that the spec is rebuilt by an external script that needs Node.js. There are no install instructions for the skill.

SKILL.md

---
name: yandex-market-api
description: 'Use for seller integrations with Yandex Market (Яндекс Маркет): catalog, prices, stocks, orders, warehouses, returns, reports, and buyer communication. Triggers include "Yandex Market API", "API Яндекс Маркета", "остатки на Маркете", businessId, campaignId, and api.partner.market.yandex.ru.'
---

# Yandex Market Partner API

This skill helps you call the Yandex Market Partner API (`https://api.partner.market.yandex.ru`). It bundles the full OpenAPI 3.0 spec from the **official repository** (`github.com/yandex-market/yandex-market-partner-api`) — 155 paths / 165 operations.

The spec is ~1.4 MB. Don't read it whole — use the helpers described below to pull only what you need.

## Authentication — Api-Key header

The primary (and recommended) auth is a single header:

```http
Api-Key: <ключ>
```

The user creates keys in the seller cabinet: **иконка аккаунта → Настройки → API и модули → Авторизация через Api-Key**. Each key gets an access scope at creation (read-only / full / по разделам) — a read-only key gets `403` on mutating methods.

The spec also lists an **OAuth** scheme (scope `market:partner-api`) for apps acting on behalf of sellers — Yandex has been phasing it out in favor of Api-Key; only go there if the user explicitly builds a multi-seller app, and check the current official docs (`yandex.ru/dev/market/partner-api/doc/`) for the flow.

There is no sandbox host — this is the live cabinet. Test orders exist as a feature (`fake` order flags), but mutating calls hit the real store.

## businessId vs campaignId — the #1 source of confusion

Two different identifiers route every request:

- **`businessId`** — the cabinet («бизнес»). Paths like `/v2/businesses/{businessId}/...` operate on the shared catalog: offer-mappings (карточки), prices for all stores, promos, feedback, Q&A.
- **`campaignId`** — one store = one placement model inside the cabinet. Paths like `/v2/campaigns/{campaignId}/...` operate per-store: orders, stocks, store prices, shipments, outlets.

Get both from `GET /v2/campaigns` (each campaign carries its `business.id`). **`campaignId` is NOT the «номер магазина» shown in the cabinet UI** — the cabinet shows it under Настройки → API и модули → «Идентификатор кампании». Passing a shop number where a campaignId is expected yields 404/403.

Related