Executing decision services with decision runtime

You use the decision runtime to execute decisions and manage resources remotely.

Selecting decision services for execution
A client application can choose which version to execute a decision service. Your client application does not need to be changed or aware of the decision ID of the decision service to be executed.
Calling decision services
Your client application calls an endpoint through the decision runtime REST API to execute a decision service. The client calls the decision service by using the standard HTTP GET and POST commands that the web browsers use when they interact with remote servers.
Execution trace for decision runtime
An execution trace shows an actual graph or tree of information that represents the execution of a decision service. You can display an execution trace by specifying the executionTraceFilters parameter in the request body when your application calls a decision service with the decision runtime REST API.
Swagger UI for decision runtime API
The decision runtime REST API is accessible from the Swagger UI facility.

Parent topic: Executing decision services