The task is a bit tricky.
It turns out you can find price-history.json in the response.
The request url looks like this: https://basket-04.wbbasket.ru/vol611/part61105/61105868/info/price-history.json
dt is likely a timestamp that is in Unix timestamp format, which is a standard way to represent seconds since the Unix epoch (January 1, 1970, 00:00:00 UTC). In this case, the JSON response provides a series of price data points, each associated with a timestamp. Based on this assumption, let's convert this to a human readable format:
basket, vol and part are different for different items. According to this response:
vol = SKU devided by 100000
part is a part of SKU as well
basket is an internal WB folder. It looks like there are 10-20 or those in total.
So we could iterate over baskets, put the correct vol and part and potentially find the correct price-history.json file.
AFAIU, the images have very similar structure.
The task is a bit tricky. It turns out you can find
price-history.json
in the response. The request url looks like this:https://basket-04.wbbasket.ru/vol611/part61105/61105868/info/price-history.json
You get a reponse that looks like this:
dt
is likely a timestamp that is in Unix timestamp format, which is a standard way to represent seconds since the Unix epoch (January 1, 1970, 00:00:00 UTC). In this case, the JSON response provides a series of price data points, each associated with a timestamp. Based on this assumption, let's convert this to a human readable format:Main caveat
basket
,vol
andpart
are different for different items. According to this response:vol
= SKU devided by 100000part
is a part of SKU as wellbasket
is an internal WB folder. It looks like there are 10-20 or those in total.So we could iterate over baskets, put the correct
vol
andpart
and potentially find the correctprice-history.json
file. AFAIU, the images have very similar structure.