Show HN: Mitmproxy2swagger – Automagically reverse-engineer REST APIs
1–10 of 87 posts
Re: Show HN: Mitmproxy2swagger – Automagically reverse-engineer REST APIs
#2I have used it already on two apps and the results are good enough to write an alternative client or quickly automate some stuff.
Re: Show HN: Mitmproxy2swagger – Automagically reverse-engineer REST APIs
#3Re: Show HN: Mitmproxy2swagger – Automagically reverse-engineer REST APIs
#4Re: Show HN: Mitmproxy2swagger – Automagically reverse-engineer REST APIs
#5Wanted to show off my little project which helps whith reverse engneering APIs used by various apps. It takes HTTP traffic capturewd by mitmproxy and generates an OpenAPI specification for a given REST API. I have used it already on two apps and the results are good enough to write an alternative client or quickly automate some stuff.
Re: Show HN: Mitmproxy2swagger – Automagically reverse-engineer REST APIs
#6Re: Show HN: Mitmproxy2swagger – Automagically reverse-engineer REST APIs
#7[1]: https://github.com/captn3m0/ideas#openapi-specification-gene...
Re: Show HN: Mitmproxy2swagger – Automagically reverse-engineer REST APIs
#8Re: Show HN: Mitmproxy2swagger – Automagically reverse-engineer REST APIs
#9Wanted to show off my little project which helps whith reverse engneering APIs used by various apps. It takes HTTP traffic capturewd by mitmproxy and generates an OpenAPI specification for a given REST API. I have used it already on two apps and the results are good enough to write an alternative client or quickly automate some stuff.
does it capture route/server rendered pages too?
Re: Show HN: Mitmproxy2swagger – Automagically reverse-engineer REST APIs
#10Very interesting! Would this also be able to determine what kind of auth (header tokens, cookies, etc) the APIs require or is that something you still need to detect manually?