class Stytch::Fraud::Rules

def initialize(connection)
  @connection = connection
end

The type of this field is nilable +String+.
The timestamp when the rule expires. Values conform to the RFC 3339 standard and are expressed in UTC, e.g. `2021-12-29T12:33:09Z`.
expires_at::
The type of this field is nilable +String+.
Combination of signals associated with a specific network commonly known as TLS fingerprinting.
network_fingerprint::
The type of this field is nilable +String+.
Combinations of signals to identify an operating system and architecture.
hardware_fingerprint::
The type of this field is nilable +String+.
Combination of signals to identify a browser and its specific version.
browser_fingerprint::
The type of this field is nilable +String+.
Cookie-less way of identifying a unique user.
visitor_fingerprint::
The type of this field is nilable +String+.
Combination of VisitorID and NetworkFingerprint to create a clear identifier of a browser.
browser_id::
The type of this field is nilable +String+.
The cookie stored on the user's device that uniquely identifies them.
visitor_id::
The type of this field is +Integer+.
The HTTP status code of the response. Stytch follows standard HTTP response status code patterns, e.g. 2XX values equate to success, 3XX values are redirects, 4XX are client errors, and 5XX are server errors.
status_code::
The type of this field is +RuleAction+ (string enum).
The action that will be returned for the specified fingerprint or ID.
action::
The type of this field is +String+.
Globally unique UUID that is returned with every API call. This value is important to log for debugging purposes; we may ask for this value to help identify a specific API call when helping you debug an issue.
request_id::
An object with the following fields:
== Returns:

The type of this field is nilable +String+.
An optional description for the rule.
description::
The type of this field is nilable +Integer+.
The number of minutes until this rule expires. If no `expires_in_minutes` is specified, then the rule is kept permanently.
expires_in_minutes::
The type of this field is nilable +String+.
The network fingerprint we want to set a rule for. Only one fingerprint or ID can be specified in the request.
network_fingerprint::
The type of this field is nilable +String+.
The hardware fingerprint we want to set a rule for. Only one fingerprint or ID can be specified in the request.
hardware_fingerprint::
The type of this field is nilable +String+.
The browser fingerprint we want to set a rule for. Only one fingerprint or ID can be specified in the request.
browser_fingerprint::
The type of this field is nilable +String+.
The visitor fingerprint we want to set a rule for. Only one fingerprint or ID can be specified in the request.
visitor_fingerprint::
The type of this field is nilable +String+.
The browser ID we want to set a rule for. Only one fingerprint or ID can be specified in the request.
browser_id::
The type of this field is nilable +String+.
The visitor ID we want to set a rule for. Only one fingerprint or ID can be specified in the request.
visitor_id::
The type of this field is +RuleAction+ (string enum).
The action that should be returned by a fingerprint lookup for that fingerprint or ID with a `RULE_MATCH` reason. The following values are valid: `ALLOW`, `BLOCK`, `CHALLENGE`, or `NONE`. If a `NONE` action is specified, it will clear the stored rule.
action::
== Parameters:

Rules are applied in the order specified above. For example, if an end user has an `ALLOW` rule set for their `visitor_id` but a `BLOCK` rule set for their `hardware_fingerprint`, they will receive an `ALLOW` verdict because the `visitor_id` rule takes precedence.

Set a rule for a particular `visitor_id`, `browser_id`, `visitor_fingerprint`, `browser_fingerprint`, `hardware_fingerprint`, or `network_fingerprint`. This is helpful in cases where you want to allow or block a specific user or fingerprint. You should be careful when setting rules for `browser_fingerprint`, `hardware_fingerprint`, or `network_fingerprint` as they can be shared across multiple users, and you could affect more users than intended.

def set(
  action:,
  visitor_id: nil,
  browser_id: nil,
  visitor_fingerprint: nil,
  browser_fingerprint: nil,
  hardware_fingerprint: nil,
  network_fingerprint: nil,
  expires_in_minutes: nil,
  description: nil
)
  headers = {}
  request = {
    action: action
  }
  request[:visitor_id] = visitor_id unless visitor_id.nil?
  request[:browser_id] = browser_id unless browser_id.nil?
  request[:visitor_fingerprint] = visitor_fingerprint unless visitor_fingerprint.nil?
  request[:browser_fingerprint] = browser_fingerprint unless browser_fingerprint.nil?
  request[:hardware_fingerprint] = hardware_fingerprint unless hardware_fingerprint.nil?
  request[:network_fingerprint] = network_fingerprint unless network_fingerprint.nil?
  request[:expires_in_minutes] = expires_in_minutes unless expires_in_minutes.nil?
  request[:description] = description unless description.nil?
  post_request('/v1/rules/set', request, headers)
end