Mitmproxy acts as a middleman. Typically you’ll run it on another device on the same network.
app > proxy > server
Which means every time the app makes a GET request (for example) the proxy can log the url/ip as well as the parameters passed to the server.
Then, to get the data yourself, you use a web client like Curl (or Requests in Python) and send the same headers/auth/parameters as the app did. But now instead of returning it to the app, it’s in a format you can store/manipulate.
Mitmproxy acts as a middleman. Typically you’ll run it on another device on the same network. app > proxy > server
Which means every time the app makes a GET request (for example) the proxy can log the url/ip as well as the parameters passed to the server.
Then, to get the data yourself, you use a web client like Curl (or Requests in Python) and send the same headers/auth/parameters as the app did. But now instead of returning it to the app, it’s in a format you can store/manipulate.