Search

Seller API Test Environment

Use the test scope of the service to set up the integration.
For authorization you need to use the token with the Test scope type.

The data in the test scope is randomly generated and does not belong to real sellers.
The using of the test scope does not carry the risk of unintentional disclosure of information.

Seller API Test Environment

Use the test scope of the service to set up the integration.
For authorization you need to use the token with the Test scope type.

The data in the test scope is randomly generated and does not belong to real sellers.
The using of the test scope does not carry the risk of unintentional disclosure of information.

Promotion

To access the test environment, use https://advert-api-sandbox.wildberries.ru instead of https://advert-api.wildberries.ru.
Campaigns will be deleted 30 days after the last modifications.
Deleted campaigns (-1 status) will be removed after 3 minutes.
A maximum of 50 campaigns can be created.
The maximum number of requests is the same as in the main API.

Statistics are generated only for campaigns of type 8 — automatic campaign and 9 — Auction.
To generate statistics:

  • the campaign must be in status 9— on display
  • type 8 campaign must have a positive bid
  • type 9 campaign must have a positive bid in the catalog
  • the campaign budget must be positive

    Ypu can create product cards in the content sandbox and use created nomenclatures in the promotion sandbox.

Top-up test balance{{ /adv/v1/test/update/balance }}

Описание метода

Updates test balance, account and bonuses

Authorizations:
HeaderApiKey
Request Body schema: application/json
balance
integer

Account top-up amount, ₽

net
integer

Balance top-up amount, ₽

bonus
integer

Bonuses top-up amount, ₽

Responses

Request samples

Content type
application/json
{
  • "balance": 1000,
  • "net": 1000,
  • "bonus": 1000
}

Response samples

Content type
application/json
{
  • "balance": 9100,
  • "net": 8000,
  • "bonus": 10000
}

Marketplace DBS

To access the test environment, use https://marketplace-api-sandbox.wildberries.ru instead of https://marketplace-api.wildberries.ru.

You can create product cards in the content sandbox and use the generated product card barcodes in the marketplace sandbox.

For the order retrieval code in the confirmation of receipt and rejection of receipt methods, you can use any combination of characters.

Create a test DBS assembly order{{ /api/v3/test/dbs/orders/make }}

Описание метода

The method allows you to create a test DBS assembly order.

A single request creates assembly orders for products from one customer's cart. They share a single transaction ID — orderUid, which is included in the responses of methods for retrieving new and completed assembly orders.

An assembly order could be created if:

  1. All product barcodes from the request have inventory in DBS warehouses.
  2. The inventory in the warehouse is greater than or equal to the amount in the request.
  3. The price of the product size containing the barcode is not zero.
Authorizations:
HeaderApiKey
Request Body schema: application/json
required
required
Array of objects [ 1 .. 10 ] items

Array of product barcodes and product inventory for the assembly order

Responses

Request samples

Content type
application/json
{
  • "orders": [
    ]
}

Response samples

Content type
application/json
Example
{
  • "code": "IncorrectParameter",
  • "message": "Incorrect parameter"
}

Marketplace FBS

To access the test environment, use https://marketplace-api-sandbox.wildberries.ru instead of https://marketplace-api.wildberries.ru.

You can create product cards in the content sandbox and use the generated product card barcodes in the marketplace sandbox.

Regular expressions are used for:

  • Supplies IDs — ^WB-GI-SAND-[0-9]+$
  • Boxes IDs — ^WB-TRBX-SAND-[0-9]+$

Create a test FBS assembly order{{ /api/v3/test/fbs/orders/make }}

Описание метода

The method allows you to create a test FBS assembly order.

A single request creates assembly orders for products from one customer's cart. They share a single transaction ID — orderUid, which is included in the responses of methods for retrieving new and completed assembly orders.

An assembly order could be created if:

  1. All product barcodes from the request have inventory in FBS warehouses.
  2. The inventory in the warehouse is greater than or equal to the amount in the request.
  3. The price of the product size containing the barcode is not zero.
Authorizations:
HeaderApiKey
Request Body schema: application/json
required
required
Array of objects or null (MakeOrder) [ 1 .. 10 ] items

Responses

Request samples

Content type
application/json
{
  • "orders": [
    ]
}

Response samples

Content type
application/json
Example
{
  • "code": "IncorrectParameter",
  • "message": "Incorrect parameter"
}

Close supply{{ /api/v3/test/fbs/supplies/{supplyId}/close }}

Описание метода

The method closes the FBS supply and marks all assembly orders as requiring re-shipment

Authorizations:
HeaderApiKey
path Parameters
supplyId
required
string^WB-GI-SAND-[0-9]+$

Supply ID

Responses

Response samples

Content type
application/json
Example
{
  • "code": "IncorrectParameter",
  • "message": "Incorrect parameter"
}

Notify that the order has been accepted by the buyer{{ /api/v3/test/fbs/orders/{orderId}/receive }}

Описание метода

Method transfers the assembly order to the status sold — received by the buyer.

Authorizations:
HeaderApiKey
path Parameters
orderId
required
integer <int64> >= 1

Assembly order ID

Request Body schema: application/json
required
code
required
string

Order retrieval code. In the test environment, you can use any combination of characters.

Responses

Request samples

Content type
application/json
{
  • "code": "string"
}

Response samples

Content type
application/json
Example
{
  • "code": "IncorrectParameter",
  • "message": "Incorrect parameter"
}

Notify that the buyer has declined the order{{ /api/v3/test/fbs/orders/{orderId}/reject }}

Описание метода

Method transfers the assembly order to the status canceled_by_client — declined upon receipt.

Authorizations:
HeaderApiKey
path Parameters
orderId
required
integer <int64> >= 1

Assembly order ID

Request Body schema: application/json
required
code
required
string

Order retrieval code. In the test environment, you can use any combination of characters.

Responses

Request samples

Content type
application/json
{
  • "code": "string"
}

Response samples

Content type
application/json
Example
{
  • "code": "IncorrectParameter",
  • "message": "Incorrect parameter"
}