# Как подключиться по 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
Connecting to the API
Connecting a service: a step-by-step path for the seller
Ways to connect to WB API: token and OAuth 2.0
Cloud service or local solution: how to tell them apart and which token to choose
WB API data categories: how to choose the right ones for your integration
How to connect to the API with a token
How to connect to the API via OAuth 2.0
How to create, refresh, or delete a WB API token
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
/
Connecting to the API
/
How to connect to the API with a token
How to connect to the API with a token
A step-by-step guide for sellers and developers
Publication date: 16.09.2026
Token-based integration is the main way to connect third-party services or your own systems to a Wildberries store. A token is a digital key that you add to the header of every API request, granting access to your store's data.
If you haven't yet decided how to connect (token or OAuth 2.0), start with the article “Ways to connect to WB API: token and OAuth 2.0”.
How token-based integration works
The seller creates a token in their WB Partners personal account (seller.wildberries.ru → Profile → API Integrations) and configures access: they choose the token type and the data categories
The seller hands the token to developers or enters it themselves in the settings of the service being connected
A single token is valid for 180 days. Once it expires, you need to reissue the token and update it in the integration; otherwise the third-party service or your information system will lose access to your store's data. For more on the general rules for working with tokens (validity, number of active tokens, owner), see the article “WB API authorization system”.
We recommend creating a separate token for each new integration — this makes it easier to manage access and disable it when needed.
Only the personal account owner can create and delete tokens. If the owner changes, tokens may stop working correctly and will need to be created again.
How to create a token: the general procedure
A token is created in your WB Partners personal account. The path: open Profile (in the top-right corner) → API Integrations → “+ Create token”.
The creation window has two tabs:
“For a service from the catalog” — if you're connecting a service from the Solutions Catalog. Select the service from the list, and the settings (data categories, access level) will be filled in automatically. If the service supports OAuth 2.0, you'll see a “Connect the simple way via OAuth 2.0” toggle.
“For a manual integration” — if you're connecting your own program or a service that isn't in the Catalog. Here you choose the token type: Base, Personal, or Test.
Which token type to choose depends on your situation:
A detailed description of each type is in the article “Ways to connect to WB API: token and OAuth 2.0”. If you're not sure which to pick, use the article “Cloud service or local solution: how to tell them apart and which token to choose”. Step-by-step instructions for creating a token are in the article “How to create, refresh, or delete a WB API token”.
How to share a token with a developer securely
After it's created, the token is shown only once — copy and save it right away. If you don't save it, you'll have to create a new one.
When sharing a token with a developer or a service:
Don't send the token over open channels — messengers, unencrypted email, comments in task trackers. Use password managers with a secure sharing feature (such as 1Password or Bitwarden) or other protected channels.
Don't hardcode the token into code stored in public repositories (GitHub, GitLab). Use environment variables or secrets.
Record who received the token and when. Keep track of which token went to which service and who it was shared with.
How to check that the connection works
Once the token has been entered into the service or program, make sure the API is reachable. To do this, you can call the connection-check method /ping:
curl -X GET "https://common-api.wildberries.ru/ping" \
-H "Authorization: YOUR_TOKEN"
A response of "OK" with status code 200 means the token works and the connection is established. If an error is returned, check the token and its data categories.
Each data category has its own domain (for example, content-api.wildberries.ru for Content). The full list of domains is in the documentation.
Security rules for working with tokens
A token is the equivalent of the password to your personal account — except this password is used by programs, not people.
Important security rules for working with tokens:
Store tokens as securely as passwords. Use password managers or secure vaults for this, rather than writing them down in text files or messengers.
Restrict access to tokens. Only the employees responsible for the API integration should have access to the token.
Record the token's expiration date. It's convenient to note this in a password manager or another secure place so you don't forget to renew the token in time.
Keep a record of every token you create. Write down which tokens you've created and which services they're used for, so you can quickly disable them when needed.
If you stop working with a third-party service or integration developer, reissue the token immediately and replace the old token with the new one in every system where it's used. After that, the old token can be deleted.
When you share an API token, you give third parties access to your store's information and your profile, which contains your personal data. Before granting access to partners, integrators, or developers: make sure you trust the recipient, and control and restrict access when needed.
For more, see the article “Seller data security when working with WB API”
What to do if token-based integration isn't working
If you run into problems with the integration:
Check that the correct token has been entered and that it hasn't expired yet. If it's outdated (180 days have passed), create a new one and update it in the service. Note that if you use a single token across several integrations, after reissuing it you need to replace it everywhere it's used.
Make sure the service is receiving data from the store in the WB Partners personal account and sending it back. You can do this as follows:
if the integration only pulls portal data, change something in that data in the seller's personal account and check whether the change reaches the service connected through the integration;
if the integration sends data to the store via WB Partners, change something in your own system and check whether the change reaches the portal.
If you run into errors in an integration that was built specifically for your needs, contact the developer of that integration.
Where to get help
If you suspect unauthorized access → in seller support, create a request in the “Personal account security” category with the subject “Unauthorized access”.
Problems with your own integration → contact the developer.
If a third-party service isn't working → contact that service's support team. Most services in the Catalog list contact details and links to connection instructions on their page.
If you suspect an outage on the WB API side → check the API status or contact Wildberries seller support: create a request in the “API Integrations” category.
What's next
After connecting, we recommend that you:
Study the documentation for the sections you need — the article “How to use the WB API documentation”
Try out requests in Swagger — the article “Swagger: interactive WB API documentation”
Test the integration in the sandbox with a Test token — the article “How the WB API sandbox works”
Keep track of API updates in the Release Notes and the Telegram channel
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