If I understand you correctly, I would still use API Explorer. Identify the projection(s) for the screen(s) you are looking for in Aurena using Debug if needed, then use that to get to the related API documentation. Even if you don’t use Aurena as a client, use that to get to the API details.
Sort of depends on what your definition of ‘documentation’ is in this case. There is no text description here for what each one does, if that’s what you mean.
If you can identify the API in the Aurena debug output then you can then directly find that API in the list on the left under the projection you’re interested in. The definition in the middle pane, and the “samples” in the right pane will guide on the actions (GET, POST) etc can be used and parameter info, most of which is fairly self-explanatory.
The other thing you might find useful is to look at the actual code for any projection, which can be done by going to the following URL:
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.