A tool for automatically converting mitmproxy captures to OpenAPI 3.0 specifications. This means that you can automatically reverse-engineer REST APIs by just running the apps and capturing the traffic.
First you will need python3 and pip3.
$ pip install mitmproxy2swagger
# ... or ...
$ pip3 install mitmproxy2swagger
Then clone the repo and run
mitmproxy2swagger as per examples below.
To create a specification by inspecting HTTP traffic you will need to:
Capture the traffic by using the mitmproxy tool. I personally recommend using mitmweb, which is a web interface built-in to mitmproxy.
Web server listening at http://127.0.0.1:8081/
Proxy server listening at http://*:9999
To configure your client to use the proxy exposed by mitm proxy, please consult the mitmproxy documentation for more information.
Save the traffic to a flow file.
In mitmweb you can do this by using the “File” menu and selecting “Save”:
Run the first pass of mitmproxy2swagger:
$ mitmproxy2swagger -i <path_to_mitmptoxy_flow> -o <path_to_output_schema> -p <api_prefix>
Please note that you can use an existing schema, in which case the existing schema will be extended with the new data. You can also run it a few times with different flow captures, the captured data will be safely merged.
<api_prefix>is the base url of the API you wish to reverse-engineer. You will need to obtain it by observing the requests being made in mitmproxy.
For example if an app has made requests like these:
The likely prefix is
Running the first pass should have created a section in the schema file like this:
# Remove the ignore: prefix to generate an endpoint with its URL
# Lines that are closer to the top take precedence, the matching is greedy
You should edit the schema file with a text editor and remove the
ignore:prefix from the paths you wish to be generated. You can also adjust the parameters appearing in the paths.
Run the second pass of mitmproxy2swagger:
$ mitmproxy2swagger -i <path_to_mitmptoxy_flow> -o <path_to_output_schema> -p <api_prefix> [--examples]
Run the command a second time (with the same schema file). It will pick up the edited lines and generate endpoint descriptions.
Please note that mitmproxy2swagger will not overwrite existing endpoint descriptions, if you want to overwrite them, you can delete them before running the second pass.
--exampleswill add example data to requests and responses. Take caution when using this option, as it may add sensitive data (tokens, passwords, personal information etc.) to the schema.
Capture and export the traffic from the browser DevTools.
In the browser DevTools, go to the Network tab and click the “Export HAR” button.
Continue the same way you would do with the mitmproxy dump.
mitmproxy2swaggerwill automatically detect the HAR file and process it.
See the generated html file here.