API Connector Documentation
Import Wildberries Data to Google Sheets
In this guide, we’ll walk through how to pull data from the Wildberries API directly into Google Sheets, using the API Connector add-on.
We'll first get an API token from Wildberries, and then set up a request to pull in metrics to your spreadsheet.
Contents
- Before You Begin
- Part 1: Get your Wildberries API Key
- Part 2: Pull Wildberries API Data into Sheets
- Part 3: API Documentation
Before You Begin
Click here to install the API Connector add-on from the Google Marketplace.
Part 1: Get Your Wildberries API Key
- Go to your seller account, click on your profile name and select Settings → Access to API.
- Select the token type to Statistics
- Click Create a token
- Your token will now be displayed. Copy it and keep it safe; it won't be shown again.
Part 2: Pull Wildberries API Data into Sheets
You can access any of the endpoints and parameters listed in the API documentation. Note that Wildberries has made a few updates to their API (info), and now requires different version numbers in the request URL depending on the date for which you're fetching data.
Here's an example request setup showing how to fetch reporting stats from your account using the v5 API. Substitute in your API key where it says your_token.
- Open up Google Sheets and click Extensions > API Connector > Open > Create request.
- In the request form enter the following:
- Application:
Custom - Method:
GET - Request URL:
https://statistics-api.wildberries.ru/api/v5/supplier/reportDetailByPeriod?dateFrom=2024-02-01&dateTo=2024-04-30&rrdid=0&limit=100000 - OAuth:
None - Headers:
Authorization:your_token
- Application:
- Create a new tab and click Set current to use that tab as your data destination.
- Name your request and click Run. A moment later you’ll see Wildberries data populate your sheet.
Part 3: API Documentation
Official API documentation: https://openapi.wildberries.ru/statistics/api/ru/#tag/Statistika
Good afternoon! Specify how to display column headers, I have data output as a result of an API request, but without column headers, the values go immediately.
Column headers should be included automatically by default. Can you please double check a) you're in overwrite (not append) mode, and b) you haven't ticked the "Remove headers" box? Both settings are located under Output options.
Of course, in the append mode. thank you very much!
tell me what I'm doing wrong?
https://common-api.wildberries.ru/api/v1/tariffs/box?date=+++Sheet2!A1+++1) 11: Completed with errors
- We received an error from wildberries.ru (400) show response
Invalid date param
Based on the error message, looks like the date is in the wrong format. Make sure you've converted it into the YYYY-MM-DD format required by Wildberries, 1) i.e. add your date into a cell, 2) convert that cell with a function like
=text(A1,"yyyy-mm-dd"), and then 3) reference that second cell.I was trying to use Python code to send a GET-request onto Statistics category, but API returned an error similar to "TokenIsNotApplicable", but containing this text: "07e4668e-a53a3d31f8b0-UK:mMKMnhVfoTW unauthorized, rejected; 456760352e0e-77 token withdrawn; decisionPoint 1090; 03bce=277" (error 401)
I found nothing about withdrawn tokens on the internet, also sorry if the question is a little out of place, I'm loading request response on local machine and into Excel file, not in Google Sheets
I can't say for sure, but it sounds like you may not have selected the Statistics scope when you created the token. You can also try searching this file for a little more information about your error: https://openapi.wildberries.ru/statistics/swagger/api/ru/swagger.yaml (towards the bottom it gives a brief description of each error message, and for TokenIsNotApplicable it says "token scope not allowed for this API route").
We've already checked the scopes and the expire date in a dedicated/official token "decoder" provided by WB, which however can't tell if the token was actually withdrawn or not, and Statistics category actually falls in what we've got access to
And yeah, "token scope not allowed" doesn't seem to be the case if it has to do with token scopes being chosen at point of token creation... It only looks similar, but we've also fallen short on second token showing the same error, if second "coder"/tester is to trust here
Sorry, in that case I'm not sure, is it possible to check with Wildberries tech support? They've also made a lot of changes to their API recently so please also make sure you're using the right version number and so on (though the error message doesn't sound like it's related to that).
We're trying, though they've been silent for 1 day as of now, which is classics with most of techsups, to be fair... I didn't find anything in API changelog in both the link and the telegram channel posting these, so I guess all I can do is wait or look further into any possible mistakes
Nevertheless, thanks for answering this weirdly rare question, hope you have a good day 😀
Sorry I couldn’t be of more help, and have a good day as well. If you find anything out feel free to come back and leave another comment, just in case someone else is also out there searching :p
Issue resolved, we really were just that much unlucky about our tokens, now the issue is fully resolved and the program's finally working
Thanks for the update, glad it’s working now!