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 users. This documentation is primarily concerned with the Rule API.
The APIs provided are all REST based and are self-documented using swagger, the APIs are accessible in swagger from a shortcut in the side menu.
Published Rule API
The Alterian CX platform allows users to create their own rules in an easy to use low code interface using Templates as building blocks. More information on building Rules within Journey Orchestration can be found in the Journey Orchestration section.
Once a rule has been created it will appear in the Journey Orchestration API where it can be executed and tested through the swagger user interface.
The Rule API interface can be accessed through the link at the bottom of the documentation page or directly from https://dde.alterian.net/docs/rules.html
Rules are separated by client (if you have access to more than one client) and the target (dev, test, prod) they are saved and are listed alphabetically within these groupings.
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.
Calling a CX Rule via the API contains more information on the authentication process.
Application API
Users generally won't 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.