Hi all - happy to get feedback.

Also, someone added Mockbin on Docker: https://registry.hub.docker.com/u/tomdesinto/mockbin/

Getting a strange SSL error "SSL connection failed" on your apiembed.com iframe

cannot seem to replicate ... we're behind Cloudflare, so you could be seeing an older version of the page, we had the SSL issue earlier and fixed it.

It's a broken proxy between me and your site. Sorry!

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.

Thanks. Let us know if you need some particular additional feature.

I can see this is a cool tool but does anyone have any real world examples of how this would be used?

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.

I use something like this to test webhooks and demonstrate that the service behind it is working.

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 :)

hi - we have written a blog post on why/how we use this internally: http://blog.mashape.com/welcoming-mockbin-to-the-mashape-fam...

If you are developing an SPA and want to do front end first.

That's a ton of use cases!

Anyone else get their well-timed email with a link to the "/newest" page for this submission? Interesting strategy :D

I guess this can be seen as negative, I was curious if this was something y'all see a lot. Opinions?

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.

we're adding proxy functionality to it this week.

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?

I'm adding SOAP to the backlog: https://github.com/Mashape/mockbin/issues/12

as for YAML, I think its best for human readability, rather than actual usage in libraries.

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?

it does not, plenty of other tools to capture HAR response objects: http://ahmadnassri.github.io/har-resources/

Thanks for the link

A simpler alternative is http://httpbin.org (but the more the merrier!)

not quite the same, this is for creating custom mocked endpoints, while httpbin is pre-defined utility endpoints

Any plans to add websocket support?

yes! already brainstorming roadmap ideas: https://github.com/Mashape/mockbin/issues