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.
...
The Alterian CX platform allows users to create their own rule (or rule group) APIs based of easy building blocks in an easy to use low code interface take a look at Journey Orchestration for full documentation on creating rules. Once a rule has been created it will appear in the Rule API documentation where it can be tested and executed through the swagger user interface.
...