This is really neat. We used Apiary at my last company to document our APIs and the added benefit is that it did just this, generated and tracked a mock endpoint. Really cool stuff.
I've found these tools particularly useful if you've got your team divided up into frontend vs backend/platform. We would discuss and mock up the endpoint to unblock the API consumers while the actual service is built.
a simple example is when developing against a third party api, and want to validate the behavior of your code and see what the HTTP request looks like, swap the API endpoints with mockbin urls and check, even mock the response with a Bin and build your client "offline" without hitting API throttling rate limits or exceeding your quotas for paid APIs, and much more :)
Would be cool if this could generate into a framework to run the mock locally for tests. So you would run a local server instead of mocking the network calls and returning json on a method level, you would actual hit a server.
Or is that bad? Curious to hear other takes on it.
Either for testing an SDK or the network layer of app itself.
Now what we REALLY need is the ability to mock SOAP endpoints.
Semi-relatedly: I've never seen YAML over the web before, mostly just in config files and such. Is that common? Are there any examples of use out there?
Does this tool also have the ability to record responses from API endpoints for future use?, or do I have to already have the response object available?
Also, someone added Mockbin on Docker: https://registry.hub.docker.com/u/tomdesinto/mockbin/