Find out answers to questions related to API mocking using QuickMocker (intercept and debug requests, multiple methods, RegExp in the URL path, dynamic properties or shortcodes, local forwarder vs proxy, restrictions etc).
No, you do not need to know any coding (programming) language in order to create API mock. All you need in order to create a mock endpoint is:
That's it. In case you do not have this info, you can get sample of it from your back-end or 3rd party software engineers and use it inside QuickMocker until real web services development is completed.
So, simply create your project with its own subdomain and start adding your mock endpoints.
Yes, that's one of the main features of QuickMocker. All the requests to your fake API are logged inside the Requests Log of every project separately. The records will appear in the Requests Log tab immediatelly after the request to your endpoint is executed. Each log record is an expandable panel. At first you can see request HTTP method, request URL, response status and date of the request. When you expand the panel you can see all the request and response details (headers and body for both request and response) in separate subtabs.
Yes, we support multiple request HTTP methods (e.g. GET/HEAD etc.) per endpoint. If endpoint has multiple methods, it will get label of the first method plus amount of other method (e.g. GET + 2) and will be marked with a dashed border like on the image below:
With the RegExp URL Path you can intercept requests using Regular Expressions (or so called search patterns). What does this mean? It means instead of creating multiple endpoints with a static URL path, you can define just one single endpoint that matches the required search pattern.
For instance, imagine you have an endpoint where you need to get user object, e.g. 'GET /user/‹id›'. In order to get multiple users with different IDs, you would have to define multiple endpoints with URL Path like 'user/1', 'user/2' and so on.
Using RegExp URL Path you can define one endpoint with the following path: '^user/[0-9]+$'. This URL Path will allow you to intercept any user ID.
After you create new Project our system automatically generates one RegExp endpoint for you, which intercepts all the
You may read more about regular expressions on Wikipedia.
Please note that RexExp URL path that does not have start (^) and end ($) symbols, will match the request URI at any position. E.g. if you set URL path for your endpoint to "mocker" and after that you send request to "/some-url/mocker/test" or to "/i-got-some-mocker-here", all of them will be intercepted by this endpoint. Same as you would send request just to "/mocker".
After you create a new endpoint, we automatically generate a default endpoint which intercepts all the requests to your URL and responds with the 404 status code. It looks like on the screenshot below:
Because of this any request to your project (including unexisting) will be logged. Keep this endpoint at the bottom of your endpoints list so it has the least of priority. This means it will be triggered only in case there was no other matching endpoint.
Please note: in case you remove or disable this endpoint, you won't be able to debug requests that do not match any method name / URL Path among the endpoints you defined and therefore it will be more difficult to fix your incorrect requests. Thus we recommend you to always keep this endpoint enabled in the list.
In order to make your mock endpoint look and work more dynamic, you may find useful some of our shortcodes (dynamic response properties). This will allow you to make each response unique with its own data depending on the context like URL path or current date/time. Additionally it can generate unique or random values.
Currently we support following shortcodes:
See example below:
URL Path (RegExp turned on):
Requesting following endpoint using following Method/URL:
Can produce the following response body:
Allows you to forward request you receive to your endpoint to any other URL including your local web server URL or IP address. This way you can process requests from the 3-rd parties on your development machines. This could be very handy while you develop integration with the 3-rd party web service using webhooks, which means you need to receive request from 3-rd party to your application, but you currently do not have a public (available on the Internet) URL. QuickMocker can receive this request, because it does provide you with a public URL and it can forward this request to your local application URL, which allows you to debug your code locally on your own machine during the incoming external request.
Please note that QuickMocker's Local Forwarder is working on the browser level, which means it can forward request to your app only when your Project's Reuqets Log tab is turned on. See picture below:
You can also view response from your local app in the request log record along with usual request and response in the Forwarder Response tab. See image below:
Warning! By default your browser will block requests to your app URL in case you use HTTP (non-HTTPS) protocol (you can read more this behavior here). Please disable this security feature in your browser for QuickMocker site if you want to use Local Forwarder feature with your non-HTTPS URL. For instance in Chrome you need to allow Insecure Content inside QuickMocker site settings. For all the rest browsers please read through the following article.
Yes, you can define proxy for any endpoint. When requesting your QuickMocker endpoint URL, the data will be forwarded to Proxy URL. After the response received from Proxy URL, it will returned back as it was a usual request to QuickMocker's endpoint.
You can configure default proxy URL for the project. It will be applied for all new endpoints you create. See screenshot below:
Except for this, you can change the Proxy URL for existing endpoints or override Proxy URL for new endpoints while creating or editing endpoint. See screenshot below:
Both of them have very similar priciple of a work. Still, the proxy works on the server level, but the local forwarder works on the level of your own browser. Lets see main differentce between those two:
Yes, you can easily restrict your API endpoints either using IP Address or using Authorization Header.
First of all when you create or edit project, you can define default restriction rules for its future endpoints. See screenshot below:
After that, when you create a new endpoint inside the project, by default it will get restriction rules that you've defined in the project earlier. Still, you can easily override them if there's a need. See screenshot below:
IP Address field can be a comma separated list of IP Addresses (e.g. 192.168.0.1,192.168.0.2) or IP Ranges (e.g. 192.168.0.1/24,220.127.116.11/32) or both. In case IP Address of the client does not match, the response status will be 403 (Forbidden).
Authorization Header field could be set to any text value you wish. If client's authorization header does not match the one you've defined, the response status will be equal to 401 (Unauthorized).
All of the requests that do no pass the restriction rules are still logged in the Requests Log tab of the project and you can easily debug them.