Table of Contents |
---|
Purpose
This WS is designed to return rule engine rule details.
Key points
This is a REST method used by MIS.
Only authenticated and authorized employee with appropriate scope can get rule engine rule details.
Specification
Page Properties | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||
|
Logic
Get data from rule_engine_rules collection (Mongo DB):
rule_engine_rule by id
Render a response according to specification.
Input parameters
Input parameter | Values | Type | Description | Example |
---|---|---|---|---|
id |
|
Request structure
See on Apiary
Authorize
Verify the validity of the access token
in case of error - return 401 (“Invalid access token”)
Verify that token is not expired
in case of error - return 401 (“Invalid access token”)
Check user scopes in order to perform this action (scope = 'rule_engine_rule:read')
in case of invalid scope(s) - return 403 (“Your scope does not allow to access this resource. Missing allowances: rule_engine_rule:read”)
Headers
Content-Type:application/json
Request data validation
Validate rule engine rule
Check that rule engine rule with such ID exists in the system (is_active = true)
In case of error - return 404 "Rule with id <rule_id> is not found", where rule_id - id of rule from request
Processing
API paragraph not found
Response structure
See on Apiary
Expand | ||
---|---|---|
| ||
|
Post-processing processes
API paragraph not found
HTTP status codes
Page Properties | ||||||
---|---|---|---|---|---|---|
| ||||||
|
...