Route is a URL pointer and a parent to the Response. Multiple routes represent multiple API endpoints that you can use to imitate your API behavior.


The fields available when defining a route are Name, Description, Route URL and Authorization. The fields are pretty self explanatory.


Authorization field represents the requirement for the clients Authorization header to contain the value that is set here. If the field is empty there is no precondition. This field is at the Route level and you can use this to protect a specific Route easily.

Route URL

With the Route URL you define the actual path of the URL that you will use when targeting this route. You can get pretty creative here, and register routes with long strings, for example /my-awesome/route/path/

Path Parameters

We support path parameters for your route, you can specify them by using colon notation /path/:pathParameter


We cache responses for a given request criteria, if you encounter any issues, you can reset the cache by clicking on the Clear Cache button.