Connect Ozon

EasyChat brings Ozon buyer chats and product workflows into one operator workspace. Questions, reviews and returns do not become ordinary messages; operators see only the actions available for the current workflow.

What You Need

• An active Ozon seller account.
• Seller API Client-Id and Api-Key.
• For the complete EasyChat workflow: Admin, Chat, Question, Review, Returns and Company roles.
• An Ozon plan that allows chat API methods.
• A working main EasyChat cron job and public HTTPS.

Under the current Ozon rules, chat methods may require Premium Plus or Premium Pro. A technically valid key may access products while chat access remains unavailable without the required plan.

Create The Key

1. Open Ozon Seller API settings.
2. Click Generate key, give it a clear name such as EasyChat, and choose external service or application use.
3. Select Admin for full access. Do not select only Admin read only: read-only access cannot let EasyChat configure notifications automatically or send workflow replies.
4. If Ozon shows these as separate roles, also select Chat, Question, Review, Returns and Company.
5. Copy the key immediately. Ozon shows it only once.

Use a dedicated key for EasyChat and never send it in chats, email or support tickets. Automatic notification setup requires full Admin access. Admin read only is safer for read-only use, but notifications must then be configured manually in Ozon and EasyChat relies on fallback reconciliation.

See Ozon’s official developer notice about Seller API keys and their lifetime for the current key rules.

After you paste a key, EasyChat also shows its expiration date. During the last 30 days it gives a quiet reminder to rotate the key in advance; after expiration the warning becomes urgent. The same state is shown on the account card, the Ozon tab and the sidebar.

Connect The Account

1. Open EasyChat → Integrations.
2. Select the Ozon tab in the common channel row. You stay on the Integrations screen and see Ozon accounts only.
3. Enter Client ID and API key.
4. Click Check and connect.
5. Keep only the required workflows enabled.

EasyChat validates credentials before storage, encrypts the key locally and tries to enable Ozon notifications. When notifications are unavailable, the account card clearly says Fallback sync is active and cron continues to reconcile changes through Seller API.

Use the same form at the top to connect another Ozon account. Connection and workflow changes are saved immediately, so the common Save integrations button is not needed on this tab. The channel summary, secure connection form and account list follow one clear top-to-bottom sequence, so the current status and next action stay visible without opening another screen.

Workflows

• Buyer chats: text, eligible attachments and read state.
• Product questions: replies and available processing states.
• Reviews: reply, edit and processing only when allowed by the API.
• Returns: reasons and resolution options come from the server, so EasyChat never invents an unsupported action.

To create a new conversation, an operator enters a posting number. Ozon does not allow an arbitrary new buyer chat without an order context.

Notifications And Reconciliation

An Ozon notification is only a wake-up signal. EasyChat never treats it as the complete message payload: it reloads current history, compares identifiers and prevents duplicates. Periodic reconciliation remains enabled in case an event is missed.

Ozon may place platform notifications and bot messages in the same buyer-chat stream. EasyChat labels them as Ozon notifications or Ozon bot and keeps them read-only. Ozon buyer is reserved for actual customer messages.

When Ozon sends a bot step with no text and no attachment, EasyChat shows a neutral Bot step without displayable content marker instead of an empty bubble. This means Ozon itself supplied a scenario step without content; EasyChat did not remove or replace an image. If Ozon marks the event as an image but does not provide its URL, EasyChat reports that missing image content separately.

During connection EasyChat verifies the callback with Ozon’s TYPE_PING. The response includes the required result flag, service version and name, and UTC processing time with milliseconds. No separate manual notification setup is needed after saving the key.

Run A Two-Way Check

1. Send a buyer message from Ozon.
2. Verify that a conversation marked Ozon appears.
3. Reply from the web panel and verify delivery.
4. Open the same conversation on Android and send another reply.
5. Check an image or file when supported by the account.
6. Open the conversation and verify that read state is synchronized.

To start a conversation, use New → Ozon and enter a real posting number. EasyChat checks for an existing chat and serializes the start operation on the server. Fast repeated taps or two operators acting at once cannot open a second conversation or send the first message twice.

Security And AI

Client-Id and Api-Key stay encrypted on the installation server and are not sent to central EasyChat. Technical notifications never appear as buyer messages, never invoke AI and consume no AI tokens. Initial history is also imported without automatic replies or unnecessary push alerts.

Common Situations

• The key works but chat is unavailable. Check the Chat role and Ozon plan.
• Notifications were not enabled automatically. Make sure the key has full Admin, not Admin read only, and verify public HTTPS.
• Fast notifications were not enabled. Verify public HTTPS; fallback polling continues to work.
• A chat cannot be started. Verify the posting-number format and that it belongs to this seller account.
• A return action is unavailable. The claim state or API-key permissions do not allow it.
• An action reports an unknown outcome. Do not submit the decision again. EasyChat first reconciles the current state with Ozon and only then safely enables another action.
• Starting a chat was interrupted or its outcome is unknown. Do not start it again. EasyChat looks for the actual chat by posting number and opens the reconciled conversation without sending the first message again.
• A message is delayed. Check the main cron job and the account’s last sync time.

Quick Checklist

• Client-Id and Api-Key pass validation.
• Full Admin plus Chat, Question, Review, Returns and Company roles are selected.
• The Ozon plan allows the required messaging and workflow methods.
• The account status is Connected.
• The main cron job runs regularly.
• Incoming and outgoing messages are verified in Ozon, web and Android.
• A specialized action runs only after operator confirmation.