FAQ

Frequently Asked Questions

349

Publication date: 29.08.2025

content

1. Introduction to the WB API

1.1. What is the WB API and how does it help you work with Wildberries?

API (short for Application Programming Interface) is an interface that allows software to automatically exchange data with Wildberries.

Put simply, the WB API lets you integrate your online store, warehouse, ERP/WMS/OMS/CRM, or another system with Wildberries—to automate operations and scale your business.

Why use the WB API:

  • Process automation: sales, stock levels, prices, and analytics update automatically—no manual entry.
  • Faster integration: the API lets you implement solutions faster and at lower cost.
  • Compatibility with record systems: the WB API acts as a bridge between the marketplace and your IT infrastructure.

1.2. What integration approaches exist?

There are two main approaches to working with the WB API:

  • Build it yourself: maximum flexibility, control, and alignment with your processes. You create your own application, scripts, or a module for your accounting system to exchange data directly with Wildberries via the API. This is a good choice if you have an IT specialist and need bespoke solutions.
  • Prebuilt solutions from the catalog: a fast start with no development. You connect the WB API using vetted services from the official Catalog of ready-made business solutions. This is convenient if you don’t want to spend resources on setup and maintenance—everything works “out of the box.”

Which should you choose?

Base the decision on your business goals and technical resources.

  • If flexibility matters ➞ choose a custom integration.
  • If speed and simplicity matter ➞ choose a prebuilt catalog solution.

1.3. What are the components of the WB API, and what is an endpoint?

An endpoint is a specific URL through which you access a particular WB API function. Endpoints are grouped into categories by task. Together, these categories make up the WB API.

Examples of WB API categories:

  • Content — manage product cards, prices, and stock.
  • Orders — retrieve and manage orders and shipments.
  • Statistics — access sales and product analytics.
  • Advertising — manage advertising campaigns on the platform.

2. Authorization and Security

2.1. What is a token and why do you need one?

A token is a unique access key for working with the WB API. It’s required to authorize requests that your application sends to Wildberries services. Without a token, access to your store data isn’t possible, so it’s important to keep it secure and not share it with third parties unless necessary.

2.2. How do I create a token?

You can create a token in your Wildberries seller account:

  • Go to «👤 Profile → API Integrations»
  • Click «➕ Create token», and specify the necessary access scopes
  • Save the generated token in a secure place—it’s shown only once at creation

2.3. Who can create a token?

The owner of the Wildberries seller account can create a token (after first creating the seller account).

2.4. What token types exist, and how do they differ?

Several token types exist:

  • Read-only token (read) — allows data retrieval only (e.g., analytics).
  • Read-write token (write) — allows modifying data (e.g., updating prices and stock).

2.5. How many tokens can I create?

You can create up to 20 tokens per store.

2.6. What is OAuth 2.0, and when should I use it?

OAuth 2.0 is a secure and convenient authorization protocol that allows services to access your account without sharing your password or API key.

We recommend using OAuth 2.0 to connect partner services from the Wildberries solutions catalog. OAuth is more convenient and secure than a regular token because you can revoke access for a specific application at any time without replacing the token for other integrations. In addition, a service receives only the data necessary for its operation with this token.

2.7. Which token category is required for a specific API method?

The required token category is shown in the notes for the section where the method is described.

You can also review the list of token categories for all methods in the WB API documentation.

We recommend creating a separate token for each group of tasks or endpoint to keep your data secure.

2.8. How do I reissue or revoke a token?

You can reissue (create a new) or revoke (delete) a token in «👤 Profile → API Integrations» in your seller account.

Do this if a token is lost, compromised, or the store owner has changed.

After reissuing, the old token will stop working, and access will be possible only with the new token.

2.9. How long is a token valid, and how can I track it?

A regular (non-OAuth) token expires after 180 days. OAuth tokens renew automatically. Technically, an OAuth 2.0 access token is valid for 12 hours, and the refresh token for up to 30 days.

You can check token status and expiration in «Settings → API Integrations» in your account.

3. Catalog of Ready-Made Solutions

3.1. What is the catalog of ready-made solutions, and how do I use it?

The Catalog of ready-made solutions is the official list of vetted services and applications from Wildberries partners, designed to integrate your business with the marketplace without building your own solutions. To use the catalog:

  • Go to «Catalog of ready-made solutions»
  • Choose a category or use search to find a suitable service
  • Open the service page and contact the provider to connect

3.2. What are the benefits of the catalog?

The catalog provides:

  • Fast integration without development
  • Guaranteed compatibility with Wildberries
  • Support and consultation from solution providers
  • Many services release regular updates and new features

3.3. How do services differ, and how do I choose the right one?

Services in the catalog differ by functionality, cost, integrations with various systems, and level of support. To choose the right service:

  • Define your tasks and required features (e.g., order management, analytics, integration with 1C);
  • Use catalog filters to find suitable options;
  • Compare reviews, pricing, and capabilities of several services before connecting.

3.4. How do I apply to add my service to the catalog?

To add your service to the catalog of ready-made solutions:

  • Fill out the application form on the dedicated page
  • Provide a detailed description, technical documentation, and contact information
  • After moderation and review, your service will be published

4. Useful Cases and Practical Recommendations

4.1. How do I set up integration with 1C via the WB API?

To set up integration with 1C via the WB API:

  • Create a token with the required scopes (content, orders, analytics) in your Wildberries seller account
  • Use a prebuilt module or extension for 1C from the solutions catalog, or develop your own integration based on the WB API documentation
  • Map fields and data between your 1C configuration and Wildberries (product cards, stock, prices, orders)
  • Test the integration in the sandbox environment before launching to production

Read more about integrating 1C and Wildberries in a separate article

4.2. How do I migrate product cards to Wildberries from other marketplaces?

To migrate product cards from other marketplaces:

  • Prepare an export file with product data (e.g., XLS, CSV, or XML) from your current platform
  • Adapt the data to Wildberries requirements (product descriptions, attributes, images)
  • Use the WB API or a prebuilt catalog solution to upload product cards to Wildberries automatically
  • Verify the uploaded data in the sandbox, then run the upload in production

5. Documentation, Examples, and Support

5.1. Where can I find official information about the WB API?

Official documentation, sample requests, method descriptions, and other key information about the WB API are available at dev.wildberries.ru. You’ll find everything you need for quick integration and effective API usage.

5.2. What SDKs and libraries are available, and where can I get them?

There are currently no official SDKs or libraries from Wildberries. However, the developer community actively creates unofficial libraries in popular languages (e.g., Python, PHP, JavaScript), which can be found on GitHub or via a web search. Before using third-party solutions, make sure they are up-to-date and reliable.

5.3. Where can I see integration examples and case studies?

Examples of integrations and real-world case studies are available on dev.wildberries.ru in the “Cases” section. You’ll find clear scenarios and step-by-step instructions for implementing and configuring the API for different business tasks.

5.4. How do I contact technical support: creating a ticket and what information to provide?

To contact technical support:

  1. Sign in to your Wildberries seller account.
  2. Go to the “Technical Support” section.
  3. Create a new ticket and include:
  • A description of the problem;
  • API request and response examples (preferably in JSON);
  • The date and time the issue occurred;
  • The endpoints and tokens used;
  • Screenshots or other materials that help explain the problem.

The more detailed the description, the faster you’ll receive help.

5.5. Do you run webinars on working with the WB API?

Information about upcoming events, recordings of previous webinars, and additional materials can be found in the “Events” section at dev.wildberries.ru.

6. WB API Tools and Additional Resources

6.1. What are guides, and what problems do they help solve?

Guides are detailed step-by-step instructions that help you quickly master new features, avoid common mistakes, and solve specific tasks when working with the WB API. For example:

  • setting up integration with ERP systems (1C);
  • creating and updating product cards;
  • automating order processing.

List of instructions by documentation section:

📖 Links to guides are also provided in the WB API documentation—in blocks with a book icon.

6.2. What is the Developer Account, and why is it needed?

The Developer Account is a special section of the Wildberries site where you can receive notifications about technical changes and API updates.

6.3. What is the WB API Community?

The Community is a platform for communication and knowledge-sharing among developers and sellers using the WB API. Here you can ask questions, get expert advice, and learn about current issues and community-driven solutions.

Read more about the community in a separate article.

6.4. What is API Status, and how do I use it?

API Status is a monitoring tool for the status of services and the WB API. It allows you to quickly check:

  • current API and service availability;
  • the presence of technical issues and their resolution times;
  • scheduled maintenance.

You can use API Status via this link.

6.5. Token decoding

Token decoding is the process of extracting information from a token to verify its parameters (e.g., access rights and expiration). Remember that a token contains confidential information and should only be decoded in a secure environment.

You can decode a token via this link.

6.7. What is the sandbox, and what is it for?

The sandbox is a separate test environment that allows you to verify your application or integration with the WB API without risking your real business data. It’s used for debugging and testing functionality before launching in production.

6.8. How do I work with the sandbox?

To work with the sandbox:

  • Create a separate token for the sandbox in your account;
  • Use special test endpoints (as listed in the API documentation);
  • Differences from production include fake data and the ability to safely perform operations such as creating orders or changing prices.

Examples of requests and endpoints can be found in the official WB API documentation at dev.wildberries.ru

6.9. What limitations apply in the sandbox?

The sandbox has the following limitations:

  • Rate limits on the number of requests per unit of time;
  • Use of fake (non-real) data to prevent real interaction with your customers or store data;
  • No ability to perform real financial or inventory operations.