This proxy lets you offer to your customers capabilities that are not implemented in your API, without the need of adding a single line of code to it. In combination with API Policies and API Gateway, you can improve your security, enrich incoming messages, add troubleshooting features like logging, etc.
The proxy is a Mule application and as such, it can be only deployed to a Mule runtime.
Only the resources provided in your spec are the ones that will be handled and sent to the backend service.
Note: If your API is already a Mule based application, then instead of using a proxy, you can just include the autodiscovery capability to it.
Validation against your RAML (0.8/1.0) spec. This includes:
If your RAML spec specifies optional parameters with a default value, and the request does not provide that parameter, the proxy will add it.
|Response status code||Reason|
|400||Bad request (Validation result)|
|404||Not found (The resource/method could not be found in the RAML spec)|