A1 Yandex KIT — Store

Communication

../a1-yandex-kit/references/merchant-communication.md

UpdateWarehouse

POST /v1/files

POST /v1/videos

multipart/form-data

GET /v1/alerts

ACTIVE

RESOLVED

CRITICAL

WARNING

WARNING

POST /v1/alerts/{alert_id}/resolve

CRITICAL

Authorization: Bearer <token>

https://api.kit.yandex.net

/v1/

{code, message, trace_id}

a1-yandex-kit

Workflow

npm install

1. Search for the operation you need:
   bash

   node scripts/search_docs.mjs "<query>" [--tag "<Тег>"] [--limit N]

   Matches operation ids, paths, tags and the Russian summaries/descriptions, e.g.

   node scripts/search_docs.mjs "создать склад"

   .
2. Inspect the full contract of one operation — path/query parameters plus the fully dereferenced request/response schemas:
   bash

   node scripts/search_docs.mjs --operation CreateWarehouse

3. Validate a drafted request body offline before sending anything:
   bash

   node scripts/validate.mjs --operation CreateWarehouse --body '<json>'
   # or: node scripts/validate.mjs --operation CreateWarehouse --body-file body.json

   Prints

   VALID

   (exit 0) or the list of schema violations (exit 1).
4. Execute the operation:
   • prefer the matching

     mcp-yandex-kit

     MCP tool from «Related MCP tools» below (e.g.

     get_store

     ,

     create_warehouse

     );
   • any operation without a dedicated tool: the

     kit_request

     MCP tool — it validates the body against the same schema before sending;
   • or plain HTTP:

     curl -H "Authorization: Bearer $YANDEX_KIT_TOKEN" https://api.kit.yandex.net/v1/...

     (mind the 3 rps limit).

Endpoints (23 operations)

Магазин

/v1/store

GetStore

Склады

/v1/warehouses

GetWarehouses

/v1/warehouses

CreateWarehouse

/v1/warehouses/{id}

GetWarehouseById

/v1/warehouses/{id}

UpdateWarehouse

/v1/warehouses/{id}/archive

ArchiveWarehouse

/v1/warehouses/{id}/unarchive

UnarchiveWarehouse

Пользователи

/v1/users/current

GetCurrentUser

Гео

/v1/geo/regions

GetRegions

Файлы

/v1/files

UploadFile

/v1/files/{id}

GetFileById

Редиректы

/v1/redirects

GetRedirects

/v1/redirects

CreateRedirect

/v1/redirects/{redirect_id}

GetRedirectById

/v1/redirects/{redirect_id}

UpdateRedirect

/v1/redirects/{redirect_id}

DeleteRedirectById

Новости

/v1/blogs/{blog_id}

GetBlogById

/v1/blogs/{blog_id}

UpdateBlog

/v1/blogs/{blog_id}

DeleteBlogById

/v1/blogs

GetBlogs

/v1/blogs

CreateBlog

Алерты

/v1/alerts

GetAlerts

/v1/alerts/{alert_id}/resolve

ResolveAlert

Related MCP tools

mcp-yandex-kit

search_operations

get_operation_schema

kit_request

• get_store

  — Get information about the current store (id, slug, b2c_url).

• get_current_user

  — Get the user that owns the API token.

• get_regions

  — Get the list of geographic regions (countries, regions, cities).

• list_warehouses

  — List warehouses of the store (paginated).

• get_warehouse

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

• create_warehouse

  — Create a new warehouse.

• update_warehouse

  — Update an existing warehouse via JSON Merge Patch: send only the fields to change; setting a field to null removes it.

• warehouse_action

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

• upload_file

  — Upload a file (e.g. an image for a variant or collection) via multipart/form-data.

• get_file

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

• list_blogs

  — List store news articles (paginated).

• get_blog

  — Get one store news article by ID.

• create_blog

  — Create a store news article.

• update_blog

  — Update a store news article.

• list_alerts

  — List system alerts of the store (paginated), CRITICAL ones first and newest first within the same severity.

• resolve_alert

  — Mark an alert as resolved.

search_operations

kit_request