R Рука на пульсе для селлеров WB
← API-токен WB
БАЗА ЗНАНИЙ / API-токен WB

Как пользоваться документацией WB API — документация разработчиков WB

Registering and setting up your profile on the developer portal

Официальный материал WildberriesPublication date: 16.09.2026Открыть первоисточник ↗

# Как пользоваться документацией WB API

- Collection: developer.wildberries.ru

Documentation

Release Notes

Swagger

Sandbox

API Status

Community

Knowledge Base

More

Documentation

Release Notes

Swagger

Sandbox

API Status

Community

Knowledge Base

Sign In

Where to start

What is WB API

Developer portal

Overview of the WB API developer portal

How to use the WB API documentation

Swagger: interactive WB API documentation

Registering and setting up your profile on the developer portal

Connecting to the API

Authorization and security

Testing and the sandbox

Working with the API

Monitoring and updates

The WB API platform for services

Training and support

Guides

Case studies

Tool integrations

Cookbook

Home

/

Developer portal

/

How to use the WB API documentation

How to use the WB API documentation

Navigating methods, parameters, examples, and tips for working efficiently

Publication date: 16.09.2026

Where to find the documentation

The WB API documentation lives on the developer portal at dev.wildberries.ru — under the "Documentation" item in the top menu. It is split by documentation section: each section has its own page listing all of its methods. For a general overview of what the portal offers, see the article “Overview of the WB API developer portal”.

Documentation sections

The side menu of the documentation page holds 13 sections. Each section is a separate page with the full list of its methods.

For more on the data categories behind these methods and their domains, see the article “WB API data categories”.

Documentation sectionWhat it covers
GeneralAuthorization, error codes, request limits, connection check, user management
Item ManagementCreating and editing listings, media files, labels
FBS ordersOrders with the goods stored at the seller's warehouse, assembly orders
DBW ordersOrders delivered from the seller's warehouse by the Wildberries courier service
DBSOrders delivered by the seller
In-⁠store pickupOrders the buyer picks up from the seller's location
FBW suppliesSupplies to a Wildberries warehouse, warehouse management
Marketing and promotionPromotional campaigns, bids, promotion statistics
Customer communicationQuestions, feedback, buyer chat
RatesCommissions, logistics tariffs
Analytics and dataSales analytics, funnel reports, search queries
ReportsSettlement sales report, breakdowns
Documents and accountingFinancial documents, acts, invoices

How to find the method you need

If you know what task you want to solve but not which method to use:

1. Identify the section. Think about which area your task belongs to. For example, updating prices is "Item Management", while checking sales statistics is "Analytics and data".

2. Open the section in the side menu. Click the section name — it expands, and you'll see thematic blocks of methods.

3. Use search. At the top of the side menu there is a "Search" field — type a keyword (for example, "price", "card", "order"), and the documentation will show the matching methods.

4. Read the section description. At the top of every documentation page there is an overview — what this section's methods do, how they relate to one another, and which token you need for access.

How a documentation page is organized

Each section page consists of several elements.

Side menu (left) — navigation across all of the section's methods, grouped into thematic blocks. Click a method name to jump to its description.

Section description (top) — the start of the page briefly explains what tasks this section's methods solve and which token type you need for access.

Method description (main area) — detailed information about the selected method: parameters, request and response examples, error codes.

How to read a method description

Every method in the documentation is described using a single template. Let's go through the key elements.

Header and HTTP method

The header shows the HTTP method (GET, POST, PUT, DELETE, PATCH) and the endpoint path. For example:

POST /content/v2/cards/upload

This means: send a POST request to the given path, using the domain of the "Content" data category (content-api.wildberries.ru).

Token category

At the start of each section of methods, it states which token you need for access. For example: "To access the methods, use a token for the Content category." This means that when creating the token you had to select the "Content" data category.

For more on token categories, see the article “WB API data categories: how to choose the right ones for your integration”.

Request limits

For each method or group of methods, the limits on the number of requests are given — as a table broken down by token type. Format:

ParameterExampleWhat it means
Period1 minuteThe time interval
Limit300 requestsThe maximum number of requests per period
Interval200 msThe recommended pause between requests
Burst20 requestsThe maximum number of requests you can send at once without pauses

For Base and Test tokens, the limits may be lower than for Personal and Service tokens. For more on the limit system and the Token Bucket algorithm, see the article “WB API rate limits”.

Request parameters

A table describing each parameter: name, data type, whether it's required, description, and allowed values.

Request and response examples

Ready-made JSON examples that you can copy and adapt to your needs. Examples are one of the most useful parts of the documentation for getting started quickly.

Response codes

A list of possible response codes with descriptions: what each code means and what to do when an error occurs. For the full code reference, see the article “WB API error code reference”.

How to test requests from the documentation

The WB API documentation is published in OpenAPI (Swagger) format, which lets you send test requests right from the browser.

For more on working with Swagger, see the article “Swagger: interactive WB API documentation”

To test in a safe environment, use a Test token and the sandbox — a separate environment with synthetic data, where you can't affect a real store.

For more, see the article “Test token and the WB API sandbox”

Tips for working with the documentation efficiently

Start with the section description. Before reading the descriptions of individual methods, read the whole section overview — it lays out the general rules, limits, and dependencies between methods.

Watch for "guide" links. In the documentation's section descriptions you'll find blocks like: "To learn how to use the methods in business scenarios, see the guide on..." — these are links to guides with step-by-step API usage scenarios.

Check the Release Notes. If your integration has stopped working, the first thing to check is the Release Notes — the method may have been updated or replaced.

Use the /ping method for diagnostics. If your requests return errors, start by checking the connection with the /ping method for the relevant data category. This helps separate token problems from problems with a specific method.

Cross-check with the guides. If you're working with a documentation section for the first time, find the matching guide in the Guides section of the Knowledge Base. Guides show the methods in the context of a real scenario: what order to call them in, what parameters to pass, and what responses to expect.

Russia

User Agreement of the WB API Service

WB API Platform Access Agreement

WB API Price List for Third-Party Services

Personal Data Processing Policy

Cookie Policy

Cookie Settings

FAQ. Frequently Asked Questions