Skip to main content
POST
Create a fraud-control rule

Authorizations

Authorization
string
header
required

Body

application/json

Body of a POST /v2/blocks request.

filter_type
enum<string>
required

Which events list the fraud-control rule belongs to. WHITE is the permitted events list. BLACK is the blocked events list. A BLACK match changes an event only where something checks it: quality rules, prehandler actions, and campaign expressions that check fraud-control rules. Each check takes one value and one list type. The client's fraud-control rules are checked before Extole's global fraud-control rules, WHITE before BLACK within each, and the first fraud-control rule that matches that value wins. So when a client WHITE fraud-control rule and a global BLACK fraud-control rule both match the value, the WHITE one wins, and when a client BLACK fraud-control rule and a global WHITE fraud-control rule both match it, the BLACK one wins.

Available options:
BLACK,
WHITE
list_type
enum<string>
required

What the fraud-control rule matches. USER_AGENT matches a substring of the event user-agent header (regex is not supported). EMAIL_DOMAIN matches the profile email domain on the event (for example example.com). NORMALIZED_EMAIL matches the provider-normalized profile email. Whether plus-address variants of the same mailbox match depends on the email provider. CIDR matches the event IP with CIDR notation (for example 192.168.1.0/24); overlapping CIDRs are separate fraud-control rules, not duplicates.

Available options:
CIDR,
EMAIL_DOMAIN,
NORMALIZED_EMAIL,
USER_AGENT
value
string
required

Value to match for the chosen list_type. For CIDR, use CIDR notation such as 203.0.113.0/24. The value is stored lowercased, and a NORMALIZED_EMAIL value is stored provider-normalized. Creating a fraud-control rule whose filter type, list type, and stored value match an existing fraud-control rule returns block_duplicate, even when the submitted text differs.

Response

Successful response

A fraud-control rule on a permitted or blocked events list.

block_id
string
required

Server-assigned identifier of the fraud-control rule.

client_id
string | null
required

Client that owns the fraud-control rule, when it is client-scoped.

created_date
string
required

RFC 3339 or RFC 9557 date-time with a numeric UTC offset and an optional IANA time-zone suffix in square brackets. Precision up to milliseconds.

Pattern: ^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d{1,3})?(Z|[+-](?:[01][0-9]|2[0-3]):[0-5][0-9])(\[[^\]]+\])?$
Example:

"2025-10-24T02:00:00-07:00"

filter_type
enum<string>
required

Which events list the fraud-control rule belongs to. WHITE is the permitted events list. BLACK is the blocked events list. A BLACK match changes an event only where something checks it: quality rules, prehandler actions, and campaign expressions that check fraud-control rules. Each check takes one value and one list type. The client's fraud-control rules are checked before Extole's global fraud-control rules, WHITE before BLACK within each, and the first fraud-control rule that matches that value wins. So when a client WHITE fraud-control rule and a global BLACK fraud-control rule both match the value, the WHITE one wins, and when a client BLACK fraud-control rule and a global WHITE fraud-control rule both match it, the BLACK one wins.

Available options:
BLACK,
WHITE
list_type
enum<string>
required

What the fraud-control rule matches. USER_AGENT matches a substring of the event user-agent header (regex is not supported). EMAIL_DOMAIN matches the profile email domain on the event (for example example.com). NORMALIZED_EMAIL matches the provider-normalized profile email. Whether plus-address variants of the same mailbox match depends on the email provider. CIDR matches the event IP with CIDR notation (for example 192.168.1.0/24); overlapping CIDRs are separate fraud-control rules, not duplicates.

Available options:
CIDR,
EMAIL_DOMAIN,
NORMALIZED_EMAIL,
USER_AGENT
source
string
required

Who created the fraud-control rule: Extole when Extole created it, user specified when a client user created it.

user_id
string | null
required

My Extole user who created the fraud-control rule, when known.

value
string
required

Matched value for the fraud-control rule's list_type.