Search the full catalog of all 162 Yandex KIT API operations by keyword. Matches operationId, URL path, tag and Russian summary/description (the API docs are in Russian, so Russian keywords like "категории" work too). Any operation found here can be executed with kit_request; use get_operation_schema to inspect its parameters and body shape first.

Get full metadata for one KIT API operation by operationId: HTTP method, path, path/query parameters, request content type, pagination info, and the fully dereferenced JSON schemas of the request body and response. Call this before kit_request or any create/update tool to learn the exact body shape.

Escape hatch that executes ANY of the 162 Yandex KIT API operations by operationId, including operations without a dedicated tool. WARNING: this performs REAL calls against the live store — write operations (create/update/delete/archive) take effect immediately and there is no sandbox. Workflow: search_operations -> get_operation_schema -> kit_request. The request body is validated against the OpenAPI schema before sending (set validate=false to skip).

Get information about the current store (id, slug, b2c_url). Operation: GetStore.

Get the user that owns the API token. Operation: GetCurrentUser.

Get the list of geographic regions (countries, regions, cities). Each region has an id, a name and a parent region id, forming a hierarchy. Operation: GetRegions.

List products of the store (paginated). A product groups one or more variants (SKUs) and links them to categories.

Get a single product by its ID, including its category bindings.

Create a new product. Requires category_ids (array of category UUIDs, at least one). Call get_operation_schema("CreateProduct") for the exact request shape.

Update an existing product (plain JSON PATCH, not merge-patch). Passing category_ids fully replaces the product's category list. Call get_operation_schema("UpdateProduct") for the exact request shape.

List variants (sellable items / SKUs) of the store, with optional filters (paginated). By default the API returns variants of all statuses except ARCHIVED. Known KIT API defect: ARCHIVED is silently stripped from the status filter, so archived variants cannot be listed (only read by ID via get_variant); the tool detects this and fails with STATUS_FILTER_IGNORED, ARCHIVE_READ_UNSUPPORTED or MIXED_ARCHIVED_FILTER_UNSUPPORTED (for filters mixing ARCHIVED with other statuses) instead of returning the wrong catalog slice.

Get a single variant by its ID (name, SKU, pricing, stocks, media, status).

Create a new variant (sellable item) under an existing product. Required: name and product_id. media holds images and at most ONE video: a video entry is accepted only when the same media list also carries at least one image, and its video_id must already be READY (upload_video / upload_video_from_url, then poll get_video). Call get_operation_schema("CreateVariant") for the exact request shape (pricing, stocks, media, ...).

Update an existing variant via JSON Merge Patch: send only the fields to change (e.g. pricing or stocks). No field of UpdateVariantRequest is nullable, so null values are rejected by validation before any call — to clear a price, use bulk_update_prices (its price/manual_discount_price accept null). media is an exception to merge-patch granularity: sending it REPLACES the whole list, so resend the existing images alongside anything you add. At most ONE video per variant, and a video is accepted only when the same list carries at least one image — sending a video alone wipes the images and fails. stocks replaces the whole list too. Call get_operation_schema("UpdateVariant") for the exact request shape — but ignore its prose for stocks: upstream the spec pasted the media wording there, while the field still takes VariantStock entries (per-warehouse quantities).

Update prices of up to 5000 variants in one synchronous, atomic request — the fast path for syncing a whole catalog instead of calling update_variant per item. If a single item is invalid (variant unknown or archived, variant listed twice, price malformed, discount price above the base price) the whole request is rejected with 400 and NOTHING is applied; the response errors list names every offending variant. Both price fields are optional per item: omit a key to keep the current value, or send null to reset it (resetting price works only on unpublished variants). Changing price recomputes the promo price; promo membership is refreshed in the background afterwards.

Archive a variant (soft delete: status becomes ARCHIVED, item is hidden from the storefront but restorable) or unarchive it (status becomes HIDDEN; publish it afterwards via update_variant).

List product categories of the store (paginated). The API requires a status filter; defaults to ACTIVE when not provided.

Get a single product category by its ID.

Create a new product category. Required: title. Optional: slug, parent_id, display_sequence, is_hidden_in_menu, file_id, seo_title, seo_description. Call get_operation_schema("CreateCategory") for the exact request shape.

Update an existing category via JSON Merge Patch: send only the fields to change. Only parent_id and file_id accept null (parent_id: null makes the category top-level, file_id: null removes the image); null on any other field is rejected by validation. Call get_operation_schema("UpdateCategory") for the exact request shape.

Archive a category (soft delete: hidden from the storefront, restorable) or unarchive it. If the category is the only one of a product with non-archived variants, archiving requires archive_variants=true.

List orders of the store (paginated), newest first.

Get a single order by its ID, including line items, delivery chunks, payment and status.

Confirm an order. The order must be in the WAIT_FOR_CONFIRMATION status. No request body is required.

Cancel an order. Whether cancellation is possible depends on the order's current status. The optional owner reason is retained only in the MCP conversation/tool log; the KIT CancelOrder endpoint has no reason field, so it is not sent to or stored by the KIT API. No request body is required.

Mark the delivery of an order as fully completed. Intended for pickup and the store's own delivery when delivery automation is off — with automation on, the platform moves the order itself. No request body is required.

Write «Честный знак» (Chestny ZNAK) marking codes onto order items, or remove them. Each order item is a single unit and takes exactly one code; item IDs come from get_order under delivery_chunks[].items[].id. Pass the code in full, including the crypto tail; pass marking_code null to remove a previously written code. Atomic: if any code fails the server-side check the whole request is rejected and nothing is written.

List additional services (addons) attached to an order by the order ID.

List customers of the store (paginated).

Get a single customer by their ID.

Update a customer (plain JSON PATCH). Updatable fields: note, first_name, last_name, email. Call get_operation_schema("UpdateCustomer") for the exact request shape.

List order IDs of a customer by their customer ID (paginated).

List gift cards of the store (paginated), with optional status and purchase-date filters.

Get a single gift card by its ID, including status, balance and purchase info.

List discounts of the store filtered by status (paginated). The status filter is required by the API.

Get a single discount by its ID (title, value, dates, status, binding mode).

Create a new discount. Required: title, discount_value ({value, type: PERCENT|VALUE}), discount_dates ({start_date, optional end_date}), status (ACTIVE|INACTIVE) and binding_mode (ALL_VARIANTS|SELECTED_VARIANTS). Call get_operation_schema("CreateDiscount") for the exact request shape.

Update an existing discount (plain application/json PATCH): send only the fields to change (title, discount_value, discount_dates, status, binding_mode). Call get_operation_schema("UpdateDiscount") for the exact request shape.

Archive a discount (soft delete: status becomes ARCHIVED, the discount stops applying but stays restorable) or unarchive it (returns it to a non-archived status).

Attach objects to a discount or detach them. Supported object types: product_variant_ids (variant UUIDs), category_ids (category UUIDs), collection_ids (collection UUIDs). Per request pass EITHER product_variant_ids OR categories/collections — the API does not mix variants with categories/collections.

List promocodes of the store filtered by status (paginated). The status filter is required by the API.

Get a single promocode by its ID (code, title, discount value, dates, type, usage limits).

Create a new promocode. Required: code, title, discount_value ({value, type: PERCENT|VALUE}), promocode_dates ({start_date, optional end_date}) and type (ORDER|PRODUCTS). Optional: binding_mode, minimum_order_amount, max_usage, max_discount_amount, one_time_use, first_order_only, show_in_pdp. The live API rejects codes containing lowercase letters even though the spec documents no format constraint — use uppercase Latin letters and digits (e.g. WELCOME5). Call get_operation_schema("CreatePromocode") for the exact request shape.

Update an existing promocode (plain application/json PATCH): send only the fields to change (code, title, discount_value, promocode_dates, status, binding_mode, limits). Call get_operation_schema("UpdatePromocode") for the exact request shape.

Attach objects to a promocode or detach them. Supported object types: product_variant_ids (variant UUIDs), category_ids (category UUIDs), collection_ids (collection UUIDs). Per request pass EITHER product_variant_ids OR categories/collections — the API does not mix variants with categories/collections.

List all webhooks of the store (not paginated). Each webhook has a URL, a list of subscribed event types and a status.

Get a single webhook by its ID (URL, subscribed events, status).

Create a new webhook. The url must use HTTPS (HTTP is rejected). Allowed events: ORDER_STATUS_CHANGED, ORDER_PAYMENT_STATUS_CHANGED, ORDER_DELIVERY_STATUS_CHANGED. NOTE: ORDER_STATUS_CHANGED will stop firing for the receipt-technical statuses CREATING_INITIAL_RECEIPT and CREATING_FINAL_RECEIPTS — key new integrations on ORDER_PLACED and COMPLETED instead (the statuses themselves stay readable via get_order). IMPORTANT: the response contains the signing secret — it is shown ONLY ONCE, store it securely. Call get_operation_schema("CreateWebhook") for the exact request shape.

Update an existing webhook: change url (HTTPS only), the subscribed events, or set deactivate=true to switch the webhook to INACTIVE. Call get_operation_schema("UpdateWebhook") for the exact request shape.

Permanently delete a webhook by its ID. This cannot be undone.

Trigger webhook validation: the API sends a POST with event WEBHOOK_VALIDATE to the webhook URL. With activate=true, the webhook becomes ACTIVE if the server replies HTTP 2xx with body {"message": "validated_store_{store_id}"} (store_id: see get_store).

List warehouses of the store (paginated). The API requires a status filter; defaults to ACTIVE when not provided.

Get a single warehouse by its ID (title, slug, status).

Create a new warehouse. Required: title. The URL slug is generated automatically from the title and cannot be changed later. Call get_operation_schema("CreateWarehouse") for the exact request shape.

Update an existing warehouse via JSON Merge Patch: send only the fields to change; setting a field to null removes it. The slug cannot be changed after creation. Call get_operation_schema("UpdateWarehouse") for the exact request shape.

Archive a warehouse (soft delete: status becomes ARCHIVED, warehouse can no longer be used for stock) or unarchive it (status becomes ACTIVE again).

List collections of the store (paginated). A collection is a curated set of product cards: STATIC (filled manually via manage_collection_cards) or DYNAMIC (filled by filters).

Get a single collection by its ID (title, slug, status, type, SEO fields).

Create a new collection. Required: title, status (ACTIVE|INACTIVE) and collection_type (STATIC|DYNAMIC; DYNAMIC also takes a dynamic_filter). Call get_operation_schema("CreateCollection") for the exact request shape.

Update an existing collection (plain JSON PATCH; only the provided fields are changed). The collection type itself cannot be changed. Call get_operation_schema("UpdateCollection") for the exact request shape.

Permanently delete a collection by its ID. This cannot be undone.

Add product cards to a STATIC collection or remove them from it. Requires product_card_ids (array of product card UUIDs).

Upload a file (e.g. an image for a variant or collection) via multipart/form-data. Files are deduplicated by content: uploading identical bytes returns the existing file. Max size 100 MB. Provide exactly one source: file_path or content_base64.

Get metadata of a previously uploaded file by its ID (name, size, URL).

List product characteristics (paginated).

Get one product characteristic by ID.

Create a product characteristic. Call get_operation_schema("CreateCharacteristic") for the exact request shape.

Update a product characteristic. Call get_operation_schema("UpdateCharacteristic") for the exact request shape.

List product characteristic groups (paginated).

Get one product characteristic group by ID.

Create a product characteristic group. Call get_operation_schema("CreateCharacteristicGroup") for the exact request shape.

Update a product characteristic group. Call get_operation_schema("UpdateCharacteristicGroup") for the exact request shape.

List the color values of the store's characteristics with their hex codes (paginated). Colors are keyed by the characteristic value itself (e.g. «Красный»), not by an ID.

Set the hex code of a color characteristic value. The value must already exist among the store's characteristic values (see list_characteristic_colors) — this endpoint recolors an existing value, it does not create one. Both fields are required.

List product videos of the store (paginated), oldest upload first. The API requires a status filter; defaults to all four statuses when not provided.

Get a single video by its ID with the current processing status. Use it to poll after upload_video: the status walks UPLOADED -> PROCESSING -> READY (the content field with the player links is filled only in READY) or ends in ERROR (details in error). Poll at most once every 5 seconds — processing time scales with the video length.

Upload a product video via multipart/form-data and queue it for processing. Max size 100 MB; formats mp4, mov, webm, avi, flv. Videos are deduplicated by content: uploading identical bytes returns the existing video. The response carries the video ID — poll it with get_video until the status is READY, then attach the video to a variant through media in create_variant / update_variant (at most one video per variant, and the same media list must also carry at least one image). Provide exactly one source: file_path or content_base64.

Upload a product video by public link and queue it for processing — use it instead of upload_video when the file lives on the web rather than on this machine. Accepts a public Yandex.Disk link to a video file, a direct link to a video file, or a link to the Yandex KIT player (which returns the already uploaded video). The link must be reachable without authentication, otherwise the API answers 400. Same limits as upload_video: max 100 MB, formats mp4, mov, webm, avi, flv, deduplicated by content. The response carries the video ID — poll it with get_video until the status is READY, then attach the video to a variant through media in create_variant / update_variant (at most one video per variant, and the same media list must also carry at least one image).

List system alerts of the store (paginated), CRITICAL ones first and newest first within the same severity. The API requires a status filter; defaults to ACTIVE when not provided.

Mark an alert as resolved. Only WARNING alerts can be closed by hand: an active CRITICAL alert is rejected with 400 and clears itself once the underlying problem is fixed. No request body is required.

List store news articles (paginated).

Get one store news article by ID.

Create a store news article. Call get_operation_schema("CreateBlog") for the exact request shape.

Update a store news article. Call get_operation_schema("UpdateBlog") for the exact request shape.