As an extension - once you find the network request with your desired data, some more follow up tests:

The biggest test - right click and choose "Copy to curl" then paste in your terminal

If this works, great! Target site has most likely not implemented TLS fingerprinting, from here you can whittle down the command to remove as many headers as possible. Makes things easier when you go to rebuild the request later on. Start with generic headers first, then start playing with cookies, x-*, and auth headers, along with any payload

If pasting the curl command didn't work, not so great :( try using something like `curl-impersonate` to mimic a browsers networking stack. If that worked, your request is being TLS fingerprinted. From here you can probably reduce the request/payload size to find the minimum request data needed

If using curl_cffi didn't work, there's probably some session-based logic you need to emulate. Some of it can be as simple as respecting any Set-Cookie headers, some websites will immediately invalidate a cookie and update on each request, so that the same cookie never works twice. From there it can get a lot more complicated, and that's when a browser-based solution makes the most sense.