There are two core APIs available for users of Journey Orchestration, the first is the application API. This API is primarily concerned with driving the product. It provides resources to the user interface and integration points with the rest of the platform. The second API is the Rule API and is concerned with exposing endpoints and integrations to the rules created by the users. This documentation is primarily concerned with the Rule API.
...
Users generally wont need to access this part of the API, there are however a few areas which may be of interest for example the info APIs allow users to generate reports against the system and the rule APIs allow access to the programmatic management of rules and data grids.
...
Clicking the Try it out button will allow users to edit the example data and invoke the rule
...
Executing the rule in the API help also provides further invoke information such as a curl string and request URL.
...
After the invoke response information is also available.
...
If the rule is designed to return data to the calling system this will also appear in the response area of the help
...