WB API: an overview for your business

What the WB API is

The WB API is the programmatic interface to your Wildberries seller account. The day-to-day work your team does by hand in the seller portal — listing products, setting prices, processing orders, running promotions, replying to buyers — your own software can do through the API, automatically and across your whole catalog at once.

You don't have to be a developer to benefit from it. The usual split: the business decides what to automate, a developer or an integration partner builds it, and this portal gives them what they need — the documentation, the change history, and hands-on guides.

---

What you can automate

Think in outcomes, not endpoints:

• Keep every price and stock level right — update prices and discounts across hundreds of items in one pass, and keep inventory current, instead of editing cards one at a time.
• Ship every order on time — pick up new orders as they come in and run each one through assembly and handover to delivery.
• See how you're selling — pull live sales, orders, and stock into your own dashboards and reports.
• Promote at scale — launch campaigns, manage bids and budgets, and track what actually pays off.
• Answer buyers fast — handle reviews, questions, chats, and return requests from your own tools.
• Close the books — bring balances and financial reports straight into your accounting.

Most sellers start with prices and orders — the two areas where manual work hurts first. The full set, method by method, is in The WB API call map.

---

A day it saves

A seller with 400 items reprices for a sale. By hand, that's 400 edits in the portal — an afternoon, and a few slips along the way. Through the API it's one upload: submit the new prices, then read back which ones applied and which were held (a cut so steep the item lands in price quarantine, say). The same job drops from an afternoon to a couple of minutes — and you know exactly what went through.

---

Is this for you?

The API earns its keep when volume or speed outgrows manual work — typically when you have many items, sell across several channels, repeat the same actions every day, or need to react to orders quickly. A handful of items changed now and then is fine to manage in the portal.

And you don't have to build it at all: if you'd rather not develop in-house, ready-made services already connect to the WB API on your behalf. Either way, the API is a programmatic view of your seller account — it works within the same Wildberries rules, not around them.

---

How access works

1. A Wildberries seller account. The API is a view of your account, so the account comes first. Registering from outside Russia is covered in Become a WB seller from abroad.
2. An API token. Your team creates it in the seller account settings and picks which data categories it may touch. Give each token only the categories it needs — that keeps every integration's access to the minimum required.
3. Requests with the token. From there it's ordinary HTTPS requests that carry the token — the mechanics are in Authorization.

---

What the first week looks like

A first integration usually comes together in about a week, not a quarter: with the account and token in hand, a developer checks the connection, pulls your product cards to confirm real data is flowing, and automates the first real job — typically a price update and an order poll. From there you add areas one at a time.

Hand your developer Your first request in 15 minutes to make the first call, then The WB API call map — it lays out the rest in order.

---

Where things are on this portal

• Documentation — the reference for every method: parameters, request and response formats, error codes, and limits.
• Swagger — an interactive view of the API where a developer can send test calls straight from the browser.
• Release Notes — API changes, announced as they ship: what changed and who's affected. When a method is being replaced, the entry names the replacement and the deadline, so a regular look keeps your integration ahead of surprises.
• Guides and announcements — hands-on guides written to be handed to a developer, plus product announcements.