Live data from Hacker News

Show HN: API Parrot – Automatically Reverse Engineer HTTP APIs

apiparrot.com

51–60 of 122 posts

Re: Show HN: API Parrot – Automatically Reverse Engineer HTTP APIs

#52
post #38

How does it compare to mitmmitmproxy2swagger? https://github.com/alufers/mitmproxy2swagger

The first and immediate difference for me is the ability to recall the name. I can recall Postman/Insomina fine, and now for API Parrot. I'm never going to be able to recall mitmproxy2swagger. Unfortunately, names matter.

Thanks 1a527dd5.

Re: Show HN: API Parrot – Automatically Reverse Engineer HTTP APIs

#54

Very sad half the comments are asking for MacOS app. The rise of development on MacOS for server development when the final target is Linux will cause long term harm to the newer generation of engineers

How about a real-world example of the harm you're clutching your pearls over?

Besides, most devs doing web development on Macs are also using Docker, which is always Linux.

Re: Show HN: API Parrot – Automatically Reverse Engineer HTTP APIs

#55
If only there would be something with schema like XML that people would use for the APIs ;) You could generate diagrams from WSDL and even generate client code from that.

There is also bunch of JSON schema stuff nowadays.

But yeah for a lot of people schema of API contracts feels like too much work and too much hassle.

JSON serialization doesn’t throw errors for new properties quickly added on sending side and receiving side can ignore stuff - well as long as API semantics allow but that’s generally going to be a hassle always even with LLMs somehow autofixing your „schema”.

Re: Show HN: API Parrot – Automatically Reverse Engineer HTTP APIs

#56
post #38

How does it compare to mitmmitmproxy2swagger? https://github.com/alufers/mitmproxy2swagger

The first and immediate difference for me is the ability to recall the name. I can recall Postman/Insomina fine, and now for API Parrot. I'm never going to be able to recall mitmproxy2swagger. Unfortunately, names matter.

I often forget the name of things, sometimes even the big ones. GitHub search is one of the primary ways I rediscover them. "reverse-engineer API" returns mitmproxy2swagger as the third result, and this is how I found it last time I needed it.

It is a bit frustrating when a project on GitHub doesn't have good tags or searchable keywords, making it harder to find.

Re: Show HN: API Parrot – Automatically Reverse Engineer HTTP APIs

#58

Earlier quoted context omitted.

Why? I mostly code on Mac and deploy on Linux (or FreeBSD). Never really encountered a situation where programming a web app on Mac has caused issues when deploying to the server.

What about issues with CPU architecture?

AWS Graviton is ARM.

My experience is that having a team with mixed platforms has helped reduce deployment woes, with the rare platform-specific bugs getting worked out beforehand.

Re: Show HN: API Parrot – Automatically Reverse Engineer HTTP APIs

#59

Earlier quoted context omitted.

The first and immediate difference for me is the ability to recall the name. I can recall Postman/Insomina fine, and now for API Parrot. I'm never going to be able to recall mitmproxy2swagger. Unfortunately, names matter.

Thanks 1a527dd5.

Ha! Nicely played. That was out of purely laziness. I don't like using one handle across sites, so I take the first 8 chars of (New-Guid).ToString() and then dump it in my password manager.

Re: Show HN: API Parrot – Automatically Reverse Engineer HTTP APIs

#60

Feedback: add a newsletter form to get notification when you will release the MacOSX version

Thank you for your suggestion!

I've added a newsletter sign-up form at the bottom of the webpage: https://apiparrot.com/#newsletter

Feel free to subscribe to receive notifications when we release the MacOSX version.

Post reply on HN