QuickMocker

Requests log / interception
Endpoints management
Homepage

Inspiration

Worked on the applications both (client and server) that required existing web services (API) which were still in development by other software engineers or 3rd parties. There are obviously a lot of existing tools/services that provide similar fake API functionality, but they had limitations. For instance a local tool called Mockoon was pretty good, but because it is a local tool we had difficulties while sharing the web services between different developers and making sure all is up to date. But what is more important because this is a local tool it does not have a public IP/DNS, thus there was problems while doing integration with the 3rd parties and particularly with the server callbacks requests (webhooks). We also tried online tools like Beeceptor, but the functionality was pretty limited. First of all the endpoints could intercept only 1 HTTP method and a URL could be only some static text. We needed something more flexible, for instance allow URL path to be a Regular Expression, which can match multiple patterns / routes.

What it does

QuickMocker is an online API mocking tool for creating fake API, dummy API, API for tests, stub API. It has following features:

create your projects and public subdomains (e.g. mydomain.api.quickmocker.com)
mock API endpoints with custom response data
intercept and debug requests in a "live mode"
allow fake endpoints to have multiple HTTP methods
make dummy API endpoint URL as a Regular Expression
prioritize endpoints with a simple drag&drop (in case your endpoint have a similar URL pattern, you might need to set a priority for endpoint)
100 random or faker shortcodes (dynamic response values) for response templating
forward requests to any URL including your localhost URL that is very helpful for webhooks integration
proxy requests to any external URL
restrict fake API endpoints using IP address or authorization header

Challenges I ran into

There were several challenges. First it was due to selected technologies. There's a separate article about it: https://medium.com/@nostop8/serving-cached-angular-universal-ssr-web-app-through-apache-proxy-e8fe2e4b3fff There were a lot of troubles with the payment integration, mainly legal and due to existing payment providers in the region. The optimal option was Fondy for us and for now it seems to be the best possible option.