External Applications Calling Rules (REST)
- 25 Oct 2021
- 1 Minute to read
- Print
- DarkLight
This documentation version is deprecated, please click here for the latest version.
External Applications Calling Rules (REST)
- Updated on 25 Oct 2021
- 1 Minute to read
- Print
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback
Overview
A Rule can be made into a REST web service that supports either HTTP GET or POST methods. REST calls to a Rule require either (1) a valid user session ID, or (2) a valid user authentication ID. The REST Service API shows instructions for calling the Flow, as well as the output. The Actions menu for the Flow provides REST service call URLs that are already populated with the necessary parameters.
Calling a rule using REST
- Enable the Rule to be called using REST from the Rule Designer.
- In the Flow Properties panel, select the Allow REST API Calls Check-Box.
- Select one of the following Action > Run [Advanced]options:
- Run Using REST.
- View Integration Details.
- If retrieving a URL, paste the URL into a browser. NOTEBe aware that credentials will be unencrypted unless HTTPS is used, or unless the Get REST URL With Encrypted Credentials option is used to call the service.
- To view the Service Call API for the Flow, from the Rule Designer, click the View Integration Details link.
- The Service Call API opens, displaying instructions for getting the session ID, how to call the service using Get and Post methods, and the results of the service call.
Was this article helpful?