a1-yandex-kit-promotionslisted

Manage promotions in a Yandex KIT store over its REST API: discounts, promo codes, promocode groups (shared codes and single-use coupon batches) and gifts. Use when creating or updating discounts, promocodes, promocode groups or gifts, or when binding them to products, categories or collections.
ztemerbekov/a1-yandex-kit-skills · ★ 2 · AI & Automation · score 71

Install: claude install-skill ztemerbekov/a1-yandex-kit-skills

# A1 Yandex KIT — Promotions ## Communication Before producing any user-facing message, read and apply [`../a1-yandex-kit/references/merchant-communication.md`](../a1-yandex-kit/references/merchant-communication.md) completely. Covers the promotions domain of the Yandex KIT e-commerce API — tags: Скидки, Промокоды, Группы промокодов, Подарки. Promotions are created first and then bound to objects: discounts, promocodes and promocode groups to variants, categories or collections via their `.../objects/add` and `.../objects/remove` endpoints (a promocode-group request carries either variants or categories+collections, not both), gifts to variants via `POST`/`DELETE /v1/gifts/{id}/variants`. Промокоды and Группы промокодов are separate models: a promocode is one standalone code, while a group holds the discount rules plus its codes — type `SINGLE` (one shared code) or `MULTIPLE` (single-use coupon codes managed via `/v1/promocode_groups/{group_id}/codes`). End-of-life differs per kind — **only discounts can be archived** (`ArchiveDiscount`/`UnarchiveDiscount`, status `ACTIVE`/`INACTIVE`/`ARCHIVED`; archived discounts stop applying but stay restorable). Promocodes and gifts have no archive endpoints and only two statuses, `ACTIVE`/`INACTIVE` — pause them by PATCHing `status` to `INACTIVE` via `UpdatePromocode`/`UpdateGift`. Promocode groups also report `ACTIVE`/`INACTIVE`, but `UpdatePromocodeGroup` is a full PUT replace with **no `status` field** — every field is required, so