There are 2 core API areas available to Journey Orchestration, the first API ‘Dynamic Decision Engine API’ is used to drive the product UI and the second is the rule API.
The APIs provided are all REST based and are self documented using swagger, the APIs are accessible from the side menu but also from https://dde.alterian.net/docs/
Dynamic Decision Engine API
Users generally wont need to access this part of the API, there are however a few areas which may be of use for example the info APIs allow users to generate reports against the system and the rule API allow access to the programmatic management of rules and data grids.
Published Rule API
The Alterian CX platform allows users to create their own rule APIs 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.
Published rules can appear as both POST and GET although generally POST is the most common. For a POST rule when the API is invoked data is passed in the body of the POST message. Authentication can be enabled where necessary with an API key in the header of the request. Take a look at Calling a CX Rule via the API for more information.