Home · Blog · Wildberries API key: which permissions to grant and where to paste it in CHBT
Wildberries API key: which permissions to grant and where to paste it in CHBT
A Wildberries API key takes a minute to issue, and then a week goes by figuring out why reviews do not arrive or the catalog is empty. Almost always the reason is the same: the key was not given a needed access category. Here is which categories each CHBT section needs, which key type you got and what it means for data frequency, where to paste the key and how to read the marks on the connection card — from Works to “the key does not have rights”.
Where the key is issued
The seller issues the key in the Wildberries seller account: Settings → API access. When issuing it, you tick access categories — they decide which data CHBT can read.
A store can be connected in CHBT by the project owner and admin. An operator sees products and orders the same way they do, but cannot connect or disconnect stores.
You do not send us the key in a chat and do not send it to support — you only paste it into the connection form. There it is stored encrypted and is not shown again to anyone, including you.
Which categories each section needs
| Section in CHBT | Key category | What it gives |
|---|---|---|
| Catalog | Content | Product cards: variants, photos, characteristics |
| Prices and stock | Prices and discounts | The price with your seller discount |
| Orders | Statistics | New orders without cancellations — to the counter, email and notifications |
| Reviews and questions | Questions and reviews | Unanswered reviews and questions — to the counter and email |
| WB orders (FBS assembly) | Marketplace | FBS assembly tasks, supplies and stickers |
| Reports and attribution | Analytics | The section has not been verified on live keys yet |
The minimum set for a bot that sells from your cards and reports orders and reviews: Content, Prices and discounts, Statistics, Questions and reviews. If you assemble FBS orders on the WB orders page, add Marketplace.
The hint in the form and the full list
In the Wildberries connection form, under the Merchant API token field, there is a short hint: “Token: WB account → Settings → API access. Categories needed: Content, Prices and discounts, Statistics”. That is the minimum for the catalog and orders. Reviews and questions also need the Questions and reviews category — without it the reviews counter stays empty, and after the first poll the card shows “the key does not have rights”.
It is better to issue the key with all the categories you will need right away: reissuing means a new key and pasting it again. An extra category breaks nothing — CHBT uses only what its sections need.
There is a nuance with Marketplace. If the key lacks rights for prices, the dashboard hint names this category too. CHBT does not yet request stock from your warehouses for the catalog, so nothing goes missing in the catalog without it. But the WB orders page does not work without it: it says directly that the key has no Marketplace category.
Key type and why data arrives with a delay
After connecting, the card shows a Key type: line — CHBT determines it from the key itself: Basic, Test, Personal or Service. If the type cannot be recognized, the dashboard says Key type not recognized and keeps to the Basic limits: erring on the side of “ask less often” is safe.
Wildberries sets strict limits for a Basic key, and CHBT respects them:
| Data | Basic key |
|---|---|
| Orders (Statistics) | 1 request every 3 hours |
| Reviews and questions | 5 requests an hour for both parts |
| Cards (Content) | 1 request an hour, 100 cards |
| Prices and discounts | 4 requests an hour |
So with a Basic key a new order may appear in CHBT several hours later, and a large catalog takes more than a day to load. For other types the dashboard says “This key type has high Wildberries limits — data arrives with every poll”.
Do not issue a Personal key for the sake of limits
The temptation is understandable: a Personal key has higher limits. But under Wildberries rules a Personal key is meant for the seller’s own systems, and using it in cloud services is forbidden. That is why CHBT does not advise issuing it and does not offer such a replacement in the dashboard.
If order speed is critical for you, rely not on the polling frequency but on FBS assembly: the WB orders page works with the Marketplace category, which has its own, softer limit for a Basic key.
One more marketplace rule worth knowing: the limit is counted per seller, not per key. Two keys of one store share one count — issuing a second Basic key for another service will not give CHBT more requests; on the contrary, it may take them away.
Where to paste the key in CHBT
- Open the bot → Marketplaces.
- Press Connect the site and choose Wildberries.
- Paste the key into the Merchant API token field. If you have several Wildberries stores, give it a name to tell them apart in the list and in flows.
- Press Connect. CHBT immediately checks that the key is alive and stores it encrypted.
The check on connection is light: CHBT asks the marketplace whether it accepts the key, without spending your limits. If the key is not Basic, CHBT checks the rights right away too: cards, prices, reviews and questions. For a Basic key such a probe would cost the hourly card limit, so its rights are found out by the first real poll — within minutes after connecting.
How to read the marks on the card
In the Read more: what this connection can do block, each section has a state:
- Works — the section responds. For orders, reviews and questions this value is set right after connecting — it is a default, not the marketplace’s answer; whether data actually arrives is visible from the counters of the last check.
- not verified on your key — CHBT has not yet made sure the section works for you specifically. The catalog and prices stay like this until the first load. It is not a refusal and not an error.
- the key does not have rights — the marketplace refused for lack of rights: a category is missing.
- the site doesn’t give back — the marketplace has no such section. For Wildberries, chats are marked this way: the marketplace does not provide correspondence with customers.
If the key lacks rights
When a section gets “the key does not have rights”, the card shows The key lacks permissions: and names Access categories required — with a link to the API access page in the seller account. What to do:
- Issue a new key in the Wildberries account, ticking the missing categories together with the previous ones.
- On the connection card press Replace key and paste the new one. The key is replaced and the data stays: counters, event history and catalog.
- Press Check now so as not to wait for the next poll.
An important subtlety: CHBT sets “the key does not have rights” only if at least one other section answered in the same poll. If all sections refused, the problem is the key itself, not the categories.
If the marketplace rejected the key
When all sections are refused, the dashboard says “The site rejected the key (401/403). Check the key and access rights in the seller’s account”, and the owner gets an “update the key” email — no more than once a day, so as not to flood the inbox.
Common causes: the key was revoked in the Wildberries account, copied incompletely or a key from another store was pasted. The fix is the same — issue a new key and paste it via Replace key. You do not need to disconnect and reconnect the store: disconnecting deletes the keys, and that is an extra step.
If the key is fine but the marketplace asked to wait because of a limit, the card shows The site asked for a pause — this is not a key rejection. CHBT repeats the request itself when the marketplace allows.
Checklist before pasting the key
- The key was issued in the account of the store you are connecting, not a neighbouring one.
- Content, Prices and discounts, Statistics and Questions and reviews are ticked; for FBS assembly — Marketplace as well.
- The key is copied in full, without spaces or line breaks at the edges.
- If you have several Wildberries stores, each has its own key and a clear name in CHBT, and the main one is marked with the Set as main button.
- No extra Basic keys for this store are issued in other services that eat the seller’s shared limit.
- Email notifications are turned on in the account settings, so you get the email digest and the key problem email.
After connecting, wait for the first poll — it runs automatically within minutes — and open Read more: what this connection can do. If everything is ticked correctly, orders, reviews and questions will appear in the counters, and the catalog will start loading page by page.
Key security
- Storage. The key is stored encrypted and is not shown again — neither in the dashboard nor to support.
- Disconnecting. Disconnect deletes the keys but not the products: the catalog stays in the dashboard and is not unpublished.
- Who sees it. Only the project owner and admin can connect and disconnect stores.
- Revoking. If the key may have leaked, revoke it in the Wildberries account — CHBT stops receiving data, and you paste a new one via Replace key.
What CHBT does with the key: reads the catalog, prices, orders, reviews and questions, and on the WB orders page works with FBS assembly tasks on your command. CHBT does not answer reviews and questions.
Bot for WildberriesUnanswered reviews on WBWB order notificationsConnect Ozon to a bot