Skip to main content

Synchronous probe result returned by /v3/email-validations/estimate. Reports counts, credit sufficiency, and a list of blockers that prevent scheduling.

requestedCount
integer
read-only

Total number of contact IDs in the request body

eligibleCount
integer
read-only

Number of contacts the user can actually validate (filtered by team scope and validation-status)

creditsAvailable
integer
read-only

Email-validation credits currently available to the team

creditsRequired
integer
read-only

Credits that would be charged if the eligible contacts are scheduled in full

creditsSufficient
boolean
read-only

Whether creditsAvailable >= creditsRequired

canSchedule
boolean
read-only

Whether the request can be scheduled — equivalent to blockers.length == 0

blockers
enum<integer>[]
read-only

Reasons why scheduling is currently blocked. Empty when canSchedule is true.

Blocker codes returned by /v3/email-validations/estimate in the blockers array. The presence of any blocker (with acceptPartial = false) means the request cannot be scheduled.

ValueNameMeaning
1FeatureDisabledEmail validation feature is disabled for the team
2AddonNotPresentRequired addon is not on the subscription
3AlreadyRunningAnother email-validation job is already running for this user
4OutOfCreditsUser has no email-validation credits available
5NotEnoughCreditsAvailable credits are below the eligible-contact count (and acceptPartial = false)
6NoEligibleContactsNo accessible contacts in RequiresValidation state were found in the request
Available options:
1,
2,
3,
4,
5,
6