As a developer, I often have trouble reproducing errors at the client end. https://intercept.rest lets me debug and monitor API requests and responses. It is similar to the Network tab in Chrome Developer Tools but works for any API: mobile apps, webhooks, frontend etc.
After I shared it with a close circle of friends, they found it incredibly useful and even found new use cases, I never imagined. Been a long time lurker here and have found several such tools that made my life easier. So, wanted to share this here and keen to hear if you folks find it useful too.
Some of the Use cases (Look forward to other use cases for this tool):
- Reproduce error requests at client side, helps to debug faster. – Easily switch between mock, dev, staging and production – You can even record requests and run load tests to see how your server behaves when 100,000 hit it – debug/monitor webhooks. – Share requests with the backend team for debugging.
If you would like to take it for spin, DM me at https://twitter.com/intercept_rest , I can hook you up with credits.
Also made a blog post on how this tool could be used to monitor network requests in real time. https://medium.com/intercept-rest/how-to-monitor-network-req...
Let me know what you think :) Happy Developing!
I've used Charles extensively in the past for this sort of testing, and particularly on mobile apps (it's not clear if/how mobile apps are supported with this).
Edit: Ah, "Now you just need to replace the original endpoint with interceptor’s URL inside the app." – so it sounds like this is basically a proxy at the HTTP level in the target app, rather than a network traffic interceptor at the network level on the system.
intercept.rest monitor only request sent by your client to your server and it is easier to setup (just change the API endpoint), works both locally and in staging/production etc.
Some use cases are :-
- When you give an app to the client for testing and you wanted to monitor the API calls and its responses for debugging purposes.
- It can also be used to debug webhooks,
- You can also choose to share all the data with your team members without additional setup.
* How did you measure that your development work was accelerated 10x faster? Or is that just a hyperbole? I think this matters because otherwise you are making claims that are not justified.
* When I visit the website, it autoplays some voice and it put me off immediately.
For us, while user create an app using our platform we have no access to the client-server, It was a hell to debug. We built this tool a couple of weeks back. For us reproducing the error at checkout page will take a while(without tool). (Choose product -> Add to cart -> enter address -> Choose payment gateway).
We build this to overcome all those and in one click we can reproduce that. The beauty is that we can reproduce the same request caused by the client while testing the app.
[0] https://proxie.app/
However, besides not being native, I really missed the scripting ability that Fiddler has. This is another major motivation for me to build this tool.
What's your stack?
Is the persisted request/response information encrypted in any way? Any chance of a locally hosted version being available?
What is your growth strategy? Who are your competitors? How long have you been working on this product?
I'm running a startup appmaker.xyz as fulltime. This is a simple tool that we build for our usecase
It helped in coordination between the backend and mobile app teams and even let us catch some potential bugs in the API.
Good to see this on Show HN!
Your Early feedback helped us immensely to improve this tool.
- There's a typo on the sign up - it says "Sing Up to Get Started"
- There does not seem to be any forgot/reset password functionality
We are super early. And Build as an internal tool to get feedback. We are sure to move fast and work on the suggestion you mentioned.
Hope this helps
Thanks
Our tool is similar to that. But our tool will monitor and forward requests to the original URL and reply the response (a proxy for your API with monitoring ). So your endpoint will work as expected and you can monitor that for debugging purposes.
one use case is that when any client reports any bugs regarding API/network requests, you can easily reproduce that without getting any inputs from the user.
We have software to detect such violations. In addition, seasoned HN users figure out what's going on and react quite aversely, as you demonstrated. Once such a ring has been identified, if the story is still on the front page, users will flag it (as happened here) or moderators will penalize it. Plus we often ban the accounts and site involved.
This case seems to have been at least in part an honest mistake. More importantly, the tool seems to be of some interest to the community. Because the most important thing on HN is to have interesting things to discuss, I'm going to reduce the penalty on this post and let the discussion continue.
I hope everyone realizes that this is a rare outcome. The more common outcome is that we ban the accounts and sites involved. So please don't do this!
Is this your github https://github.com/Livin21 ? I see this person is from Cochin, India [1]. I then see the facebook page linked to on your website [2] mentions your founder [3] who happens to be from Kochi [4] which is the same city [5].
This is quite odd, no?
[1] https://imgur.com/a/tBCmKGY
[2] https://imgur.com/a/RZgKg9Y
[3] https://imgur.com/a/fbMnrrh
[4] https://imgur.com/a/9sn4LSs
[5] https://en.wikipedia.org/wiki/Kochi
Sometimes, when I've worked on a small tool I want to share with others, I've found that telling people about it at local meetups is the easiest and quickest way to get people to try it out.
Maybe something similar happening here?
Or they just happen to work in the same building, or same coworking space, etc.
Thanks for creating an awesome tool.