

Solving Your Adventure Piece By Piece Interactive Social Media App 🚀 Launches September 🚀
You can see that the front-end told the back-end that you’re trying to login with your email and password. The back-end came back saying your login was accepted and told your browser to set a cookie called the “jwt-authorization" cookie (think of this like a temporary login key). Now the front-end can use this key to access the information that only you should be able to see. I went ahead and wrote a stockx library in Python that shows you how you can interact with stockx wi…
The first step of this process is to actually go onto stockx.com and open up the login page. We’ll want to actually log in but first we want to make sure we can see what happens when we log in. There’s a lot of ways to do this, but I find the easiest way is to hit F12 (or whatever button) to open the inspection pane for your browser. I’ll be using Chrome. We’ll want to open up the “Network” tab and hit the “Preserve Logs” checkbox just to be safe. This just ensures that a redirect doesn’t wipe the request from the log of requests. Now we’ll login like we normally do. You’ll see a bunch of stuff happen in the Network tab when you do that, but somewhere in the mess you’ll find a request that looks something like this:
…o worry about a physical browser because we know what the front-end is trying to tell the back-end. Packages like Python Requests allow you to make these requests very easily. Most (good) sneaker bots don’t even think about a browser or a website. That just takes extra resources and time that aren’t worth thinking about. We go directly to the back-end and tell it what we’re trying to do in the format that it expects.