Skip to main content
POST
Preview a draft rule set
Shows what a set of scenarios would have done to the team’s recent prospects, before you save it. Nothing is saved and nobody is enrolled.

Reading the result

Here 16 of the last 186 prospects would not have been enrolled, and 19 would have been enrolled with a warning. A rule listed in unmeasured reads a CRM field that has not been fetched for these prospects yet, so the count says nothing about it.

Good to know

  • Only enabled rules with enrollment in scope are measured. Step rules are not.
  • Preview uses CRM data already stored and makes no CRM calls.
  • Preview checks the shape of each rule but not whether its action fits its scope. Create and update check both, so a rule that previews can still be refused on save.

Authorizations

x-api-key
string
header
required

Team-scoped API key generated in the Salesfinity dashboard under Settings → Connections → API & Webhooks. A missing or invalid key returns HTTP 403.

Body

application/json
user_id
string
required

The team member this call acts as. Must be an active member of the team the API key belongs to.

Example:

"507f1f77bcf86cd799439011"

rules
object[]

The draft scenarios to measure, up to 100. Not saved. Only enabled rules with enrollment in scope are measured.

Maximum array length: 100

Response

What the draft would have done.

sampled
integer
required

Prospects evaluated: the distinct contacts behind the 200 most recent enrollments.

available
integer
required

Enrollments the team has ever had, so a thin sample is visibly thin.

verdicts
object
required

How many sampled prospects each verdict would have applied to.

by_rule
object[]
required

Per measured rule, in policy order. A prospect can match several rules.

examples
object[]
required

Up to 5 prospects who would not simply have been allowed.

unmeasured
object[]
required

Rules that could not be measured, with why.

crm_reads
object[]
required

The CRM fields the policy will read per prospect once live.