Connect Yandex Market

EasyChat brings Yandex Market buyer chats, product questions and reviews into one operator queue. Each workflow keeps its own state and allowed actions, so a question or review is never treated as an ordinary chat message.

What You Need

• An active Yandex Market seller account.
• A dedicated Partner API Api-Key for the required business.
• The Communication (COMMUNICATION) permission. A read-only key can receive requests but cannot submit replies.
• A public HTTPS URL for the EasyChat installation.
• A regularly running main EasyChat cron job.

Grant only the permissions you need. Never send the Api-Key to support, include it in screenshots or place it in the callback URL.

Connect The Business

1. Open EasyChat → Integrations → Yandex Market.
2. Paste the Api-Key.
3. Click Check and connect.
4. Confirm that EasyChat resolved the correct business ID and shows the account as connected.
5. Copy the callback URL from the account card.
6. Open Partner API notification settings in Yandex Market, set this URL and enable chat, question and feedback events.

EasyChat validates the scope before storage, resolves the business ID through Partner API and keeps the key encrypted on the installation server. The callback URL has a dedicated copy action; secrets are never rendered in HTML or placed in that URL.

Operator Workflows

• Buyer chats: text, eligible images and files, history and replies from web or Android.
• New conversation: start from an order (ORDER) or return (RETURN) ID when Market allows that workflow.
• Product questions: create an answer or comment and update or delete an eligible reply owned by the seller.
• Reviews: answer, continue a thread, update or delete an eligible seller comment and skip a reaction when allowed.

Specialized actions are shown only for an eligible request state and require an explicit operator action. Fast repeated clicks do not submit a second request.

Event Delivery

A Yandex Market callback is only a targeted signal containing the identifier of the changed entity. EasyChat:

1. accepts the request only from Yandex-published networks;
2. checks that the business ID belongs to the connected account;
3. persists a safe hint before returning 200 OK;
4. retrieves the exact chat, message, question, answer, review or comment through Partner API;
5. deduplicates the result and removes the hint only after successful processing.

Periodic reconciliation always remains enabled. It recovers an event when a callback is missed, duplicated or delivered out of order. Market does not send a dedicated notification for stickers, so cron is a required part of the integration rather than an emergency fallback.

AI Auto-Reply

The AI auto-reply in buyer chats switch lives in the account card and is off by default. After an administrator explicitly enables it, AI may reply only in an ordinary buyer chat and can use the conversation history.

Questions, reviews, technical events, initial history imports and callback signals never trigger an automatic response and consume no AI tokens. For questions and reviews, an operator reviews the prepared text and explicitly confirms the action.

Run A Two-Way Check

1. Send a buyer message in Market.
2. Confirm that a conversation with the official Yandex Market label appears.
3. Reply from the web panel and verify delivery in Market.
4. Open the same conversation in Android and send another reply.
5. Check an image or file of an eligible format.
6. Create a test question and review, then perform an allowed action after reviewing the text.
7. Use New → Yandex Market, select order or return and enter a real ID from this business.
8. Check the latest successful synchronization after the next cron run.

Common Situations

• The key cannot connect. Verify the COMMUNICATION permission and that the key belongs to the intended business.
• Inbound events appear only after cron. Verify HTTPS, the callback URL and selected event types in Market.
• The callback is rejected behind a reverse proxy. Configure the web server so PHP receives the actual connection address in REMOTE_ADDR. EasyChat intentionally does not trust arbitrary X-Forwarded-For values.
• A reply is unavailable. The key may be read-only or the request state may not allow the selected action.
• A new chat cannot be opened. Check the context type, numeric ID and that it belongs to the current business.
• A sent message takes time to confirm. Market may accept a request without returning a message ID. EasyChat reconciles an exact history echo instead of inventing an external identifier.

Quick Checklist

• The Api-Key has the least-privilege COMMUNICATION scope.
• EasyChat resolved the correct business ID.
• The callback URL is saved in Market.
• The main cron job runs regularly.
• Chat, question, review and attachment workflows are verified.
• Replies are verified in web and Android.
• AI auto-reply remains off until rules and costs are reviewed separately.