webTradeEligibility cookie and its purpose

[igor]

Hi👋! I am not sure why does steam need webTradeEligibility cookie? (for steamcommunity)
In case of sessionId, steamLoginSecure, steamCountry it's clear for me that without the ones steam would not allow me to fetch their data not many time (~20 reqs per min (not sure of that😅)).

In general: does steamcommunity use only three of these I mentioned above or steamcommunity.com domain uses: webTradeEligibility, timezoneOffset, cookieSettings, browserid, steamDidLoginRefresh in addition mentioned ones?

This question had happened because of my regular steam response errors with cookies (sessionId, steamLoginSecure, steamCountry) using axios (some times with different web proxies).
link I used these cookies with:
https://steamcommunity.com/market/listings/730/${SkinName}/render/?query=&start=0&count=10&country=UA&language=russian&currency=18

steamcommunity.com/market/listings/730/AK-47 | Neon Revolution (Field-Tested)/render/?query=&start=0&count=10&country=UA&language=russian&currency=18
In addition to that I was sure that steam sends response errors because of my multiple reqs or mb there was something on their server side so tried to reproduce the same response errors but using my browser with logged account and the link above, all of that testing left me currious because the responses were perfect, by "perfect" I mean I had no errors at all and response was always "{"success":true,...". And again why does it happen?

Thx in advance.

Edited 17 hours ago by igor

[Dr. McKay]

I believe webTradeEligibility is basically just a cache of your trading eligibility status for display purposes on the market.

Rather than run the backend checks to generate this message every time you load the page, they just run the check once and then set the cookie for display. The backend checks still get run when you attempt to actually complete a purchase or trade though; you can't bypass restrictions just by fudging the cookie.