REST resources

Developers can use the REST service to execute rulesets. As in hosted transparent decision services, rulesets are identified by their signature. Short ruleset paths and canonical ruleset paths are both supported.

The primary artifact for a REST service is the resource. Each resource is represented as a unique resource identifier (URI), and every resource has an HTTP method that clients use to request the execution of a ruleset and receive the response. WADL and OpenAPI formats can be used to describe the signature of the REST service that can be called to execute the ruleset.

Remember that each ruleset has a unique canonical ruleset path in the following form: /{RuleApp name}[/{version}]/{ruleset name}[/{version}]. Also, execution paths can differ from deployment paths. When the execution path does not specify the version number, the execution process considers the last enabled version of the RuleApp and ruleset.