POST /rule-instances
endpoint is used to create a new rule instance. A rule instance can be thought of as a live entity, that runs checks for for transactions. Rule instances use Rule
templates as the blueprint.
Every rule instance has an associated ruleId
of the rule from which it is derived. The details of the rule and the required parameters is found by GET /rules
endpoint.
Once a rule instance is created, flagright generates an ID for the rule instance and also stores related metadata like:
id
- unique identifier for the rule instancerunCount
- how many times the rule instance was runhitCount
- how many times a rule was hitcreatedAt
& updatedAt
- timestampsThey are generated and maintained by the flagright system and are not updatable by the API.
Rule filters. A key-value json object corresponding to the json schema returned by /rule-filters-schema endpoint.
Model for rule action if a rule is hit. This is returned in the API response and can be configured on Console by operational accounts like a Compliance Analyst
Rule filters. A key-value json object corresponding to the json schema returned by /rule-filters-schema endpoint.
Model for rule action if a rule is hit. This is returned in the API response and can be configured on Console by operational accounts like a Compliance Analyst