Skip to main content
POST
curl

Authorizations

x-api-key
string
header
required

Your application's API key, from Developers -> API keys in the Business Console. The primary key has full access. A named key can be scoped: none, read or write per resource, limited to some workflows or to approved sessions, to a list of IP addresses, and to an expiry date. 401 means the key is missing, wrong, revoked or expired; 403 means the key has no access to this resource or action, or the request came from an address outside its IP list; 404 on a session route means the session is outside the key's workflows or statuses. A key without media access receives image, video and PDF URLs as null, and a key without sessions write receives session links and tokens as null. See https://docs.didit.me/console/api-keys.

Body

application/json

Hypothetical rule configuration to evaluate against recent transactions. Read-only and free: nothing is created or modified. Send the same conditions, aggregation, evaluation_mode AND scope as the rule you intend to activate. Omitted conditions, aggregation and scope add no constraints of their own; dropping scope can include directions or transaction types the saved rule skips. Omitted evaluation_mode defaults to ALL (which can reduce matches for an ANY rule), and omitted period_days defaults to 90 days, not unlimited history.

conditions
object[]
aggregation
object[]
evaluation_mode
enum<string>
default:ALL
Available options:
ALL,
ANY
scope
object

Which transactions the rule applies to. Only these three keys are accepted.

period_days
integer
default:90
Required range: 1 <= x <= 365

Response

200 - application/json

Backtest statistics.

evaluated
integer

Transactions evaluated (most recent first, capped).

matched
integer

Transactions the configuration would have matched.

affected_entities
integer

Distinct subjects (by vendor_data) among the matches.

period_days
integer