Hi all,
When looking around, it seems there is a mainstream pattern when it comes to naming API.
Most of the API is provided under an "API" subdomain, and then a version (v1, v2 or date - whatever) is added to the URL, for i.e., api.mydomain.com/v1/employers to get all employers.
However, when using ORDS to provide API for let's say, my APEX application, the URL gets very unnecessarily long, for i.e., api.mydomain.com/ords/<SCHEMA>/<MODULE>/<TEMPLATE>
So, if I have a RESTful to expose a list of employers, I have to have a minimum of 4 levels for example api.mydomain.com/ords/myuniqueschema/myuniquemodule/employers
Would there be a way to setup ORDS or maybe deploy it in such a way I could have more control in this naming structure?
Thanks in advance