Home · Blog · How to connect Ozon to a bot: the Seller API key, FBS postings and reviews
How to connect Ozon to a bot: the Seller API key, FBS postings and reviews
An Ozon store can be connected to a CHBT bot in a couple of minutes: you need two values from the seller account — Client-Id and Api-Key. After that CHBT itself watches for new FBS postings and unanswered reviews and tells you about them. But the Ozon connection has honest limits: customer questions and answers to reviews do not work through it, and products are not loaded via the API yet. Here, step by step, is what you get, what is missing and how to fill the gaps.
What the Ozon connection gives
- New FBS postings. Every 10 minutes CHBT finds unprocessed postings — what needs to be assembled and shipped from your warehouse.
- Unanswered reviews. The rating, text and product of a new review go to the counter and the email digest.
- Data on request in a flow. For Ozon the Marketplace data action supports orders, stock and reviews — that is how a service bot for yourself is built.
What the connection does not give:
- Customer questions. Our Ozon connection has no questions method; the section is marked as not supported.
- Answers to reviews. You answer in the Ozon seller account.
- Correspondence with customers inside the marketplace. CHBT has no marketplace chats.
- Catalog via the API. Ozon products are not loaded from the marketplace yet — below we explain how to give the bot your range another way.
Where to get Client-Id and Api-Key
Both values come from the Ozon seller account: Settings → Seller API. Client-Id is your store’s number in the API, Api-Key is the key itself, which you create there too.
The hint in the CHBT form says which rights are needed: reading products, orders and reviews. Unlike Wildberries, Ozon key rights work through the key’s role rather than a list of category checkboxes, so CHBT does not name specific items — a wrong name is worse than none. A simple guide: the key must be able to read FBS postings and reviews.
Do not forward the key in chats and do not send it to support. Its only place is the connection form: there it is stored encrypted and not shown again.
Connecting step by step
- Open the bot → Marketplaces → Connect the site and choose Ozon.
- Paste Client-Id and Api-Key into the corresponding fields.
- If you have several Ozon stores, give each a clear name — it helps tell stores apart in the list and in flows.
- Press Connect. CHBT immediately checks the key with a light request — the list of your warehouses — and saves the connection.
If the key is not accepted, CHBT tells you right away, not an hour later. If such a store is already connected to this bot, you cannot add it a second time — the dashboard says so: “Such a store is already connected to this bot.”. Stores can be connected and disconnected by the project owner and admin.
The first poll runs automatically within minutes and looks at events from the last 3 days.
Reviews and Premium Plus
Ozon may give reviews via the API only to stores with a Premium Plus subscription. Without it, the marketplace refuses the reviews request for lack of rights — and CHBT shows that honestly instead of pretending there are simply no reviews:
- if postings arrived in the same poll, the key works, and the Reviews section gets the mark “the key does not have rights”;
- orders keep arriving, the connection is considered alive;
- no “update the key” email is sent in this situation — the key is not to blame.
If you subscribed later, press Check now on the card: on a successful answer the section returns to Works by itself. You do not need to change the key.
And once more: even with Premium Plus CHBT only reads reviews. The answer to the customer is written in the Ozon account.
Which orders CHBT sees
CHBT reads unprocessed FBS postings — that is, orders from the seller’s warehouse waiting to be assembled. The request window is built on the shipping deadline: it is always in the future relative to order creation, so CHBT also looks a few days ahead — otherwise fresh orders with long assembly times would not get into the selection.
The event contains the posting number, time, product names, quantity and price — this data goes into the email digest. Each posting is counted once; repeated polls do not duplicate it.
What is missing: FBO postings (goods in the Ozon warehouse), status changes of already assembled postings and assembly from CHBT. You assemble and ship a posting in the Ozon account. There is also no separate messenger message about new Ozon orders — such notifications currently exist only for Wildberries; for Ozon the sources are the email digest and the service bot.
The Ozon email digest
When a poll finds new postings or reviews, the project owner and admins get an email with a subject like “Ozon: 3 new orders”. Inside are blocks by section with examples (up to 5 per section) and a “What to do” line: assemble and ship the order in the Ozon account, answer the review in the Ozon account.
The email arrives only when there is something new: CHBT does not send empty daily “nothing happened” reports. If both postings and reviews arrived in one poll, they come in one email, not two.
The email arrives only if the recipient has Email notifications turned on in the account settings. A project operator does not get the digest — only the owner and admins. If you want a marketplace manager to read these emails, add them to the team as an admin.
The Ozon catalog: how to give the bot your range
Loading Ozon products via the API is not connected in CHBT yet. The store card says it directly: Products from the site are not loading yet, and right there are two ways to give the bot your range now:
- A price list file. Export products from your accounting system or spreadsheet and upload the file to the CHBT catalog.
- An online store feed. If you have your own website, connect a link to a product feed — YML, Google Merchant or CSV. Then the catalog updates by itself.
The catalog is needed for the AI seller, which answers customers about your products in Telegram, MAX, VK and on your website — it is available from the Basic plan. The reviews counter, the email digest and the service bot do not need a catalog: they work with the Ozon key on their own. What a feed is and where to get it — in the article about the YML feed.
A service bot for Ozon
With Ozon selected, the Marketplace data action answers three requests:
- Orders — “New orders: N” for unprocessed FBS postings or “No new orders.”.
- Stock — up to 15 lines: article number and warehouse data as Ozon returns them. It is a technical list, but enough for a quick “what is running out” check.
- Reviews — up to 10 lines “★rating: start of text”. Without Premium Plus this gives “Could not get marketplace data.”.
The flow is started by a keyword, and the result is inserted into a Message with a variable, for example {{mp_result}}. Lock such a flow with a Condition on a team tag — otherwise anyone who types the keyword sees the data. Step-by-step setup — in the article on a bot for a marketplace seller.
How to read the connection card
In the Read more: what this connection can do block, Ozon looks like this:
| Section | State |
|---|---|
| Orders | Works |
| Reviews | Works, or “the key does not have rights” without Premium Plus |
| Questions | Not supported |
| Chats | Not supported |
| Catalog, prices and stock | “not verified on your key” |
Works for orders and reviews right after connecting is a default value; that data actually arrives is shown by the Received for last check line. If the marketplace rejected the key entirely, the dashboard suggests checking the key and access rights, and the owner gets an “update the key” email — no more than once a day.
How the Ozon connection differs from Wildberries
| Ozon | Wildberries | |
|---|---|---|
| What to paste | Client-Id and Api-Key | Merchant API token |
| Key rights | The key’s role; reviews — with Premium Plus | Category checkboxes: Content, Statistics, Questions and reviews and others |
| Orders | Unprocessed FBS postings | New orders without cancellations |
| Reviews | Unanswered | Unanswered |
| Questions | No | Unanswered — counter and email |
| Catalog via the API | Not yet — a price list file or a feed | Cards and prices |
| Order notification in a messenger | No | The WB orders type |
What both marketplaces share: polling every 10 minutes, the email digest, the Marketplace data action in flows and an honest matrix of sections on the card. If you sell on both, connect both stores in one bot — each will have its own card. More on the Wildberries key — in the article on Wildberries API key permissions.
Common problems
- Fields mixed up. Client-Id is a short number, Api-Key is a long key. If you swap them, the marketplace will not accept the key.
- A key from another store. Client-Id and Api-Key must come from the same account.
- Empty reviews. Check the Premium Plus subscription and the “the key does not have rights” mark on the card.
- Waiting for questions. CHBT has no Ozon questions — they are read in the Ozon account.
- The key was revoked. Issue a new one and paste it via Replace key: the data and history stay.
- Want to refresh right now. Check now polls orders and reviews no more than once every 2 minutes.
A bot for a marketplace sellerWildberries API key permissionsWhat is a YML feedProduct catalog