What is the crowd's opinion of Beeceptor?

From 3.5 billion comments

URL: https://beeceptor.com

Purpose: Intercepting hosted Rest APIs calls and mocking selectively, testing webhooks, load testing APIs without impacting downstream APIs, etc.

Technologies Used: Nodejs, WebSockets

Feedback Requested: website landing page/purpose, ease of use, usability, how it can help you as a developer and QA

Comments: For the last few months I have been hacking this. In the past, I have written a few mock endpoints or fake APIs to help our integration testing team. I thought this would be a general problem and Beeceptor is an easy way to intercept and mock. E.g. If you are validating api A, which has downstream api B, how do u test A when B misbehaves.

When sending data through AHK you do it either by GET or any of the "P" verbs (PATCH/POST/PUT), that can be easily debugged.

Of course, having a man-in-the-middle becomes a tool but you're not actually dissecting the transmission like in the case of any other TCP/UDP packages or even something as the QUIC protocol (that in a future is supposed to be wrapped with SSL or at least the spec points to that direction). So I don't see the advantage.

In any extent, end-points to dump the data will do as HTTP transmission all end as non-binary (besides file uploads). Sites like httpbin and the likes are helpful. For example, with tools like Beeceptor or pipedream you can mock APIs, proxy calls, log, filter and bounce calls with or without payloads... basically anything that comes to your mind.

So, no... I don't want to antagonize or go against the tide just for the kicks. When dealing with simple API consumption and web scrapping scenarios I don't see the usefulness of such tool as browsers have whatever is needed, AHK can easily debug with a proper editor/IDE and while testing you can have an end-point to receive the data and possible bounce it back if is ok, not that it cannot be done with AHK itself an a single line of code.

But yeah, is a tool... a nice one, just feels off in this scenario.

You can try Beeceptor.com as well. It gives proxying capabilities where you can define mocking rules. Well, this technique us about wrapping an external domain in to another.

​

The go-github library takes an argument `defaultBaseURL` where you can put Beeceptor endpoint. In the Beeceptor endpoint, add "https://api.github.com/" as Target URL. That way you can inspect the payloads as well as mock some calls.

URL: https://beeceptor.com Purpose: Intercepting hosted Rest APIs calls and mocking selectively, testing webhooks, load testing APIs without impacting downstream APIs, etc. Technologies Used: Nodejs, WebSockets Feedback Requested: website landing page/purpose, ease of use, usability, how it can help you as a developer and QA Comments: For the last few months I have been hacking this. In the past, I have written a few mock endpoints or fake APIs to help our integration testing team. I thought this would be a general problem and Beeceptor is an easy way to intercept and mock. E.g. If you are validating api A, which has downstream api B, how do u test A when B misbehaves.