Email validation semantics

High-value validation

A high-value validation is a usable personal email result for B2B outbound workflows, not just any syntactically valid address.

Canonical status

valid

Status language is backed by the shared validation result contract and product publish gates.

Create an API key Read API docs

Quality signals

valid
high
not role-based
not catch-all

Recommended actions

Keep the lead in send-ready segments
Use as a chargeable validation outcome
Report separately from low-value valid-looking records

What it means

GTMAPIs treats high-value validation as the email-validation outcome most useful for outbound teams: a canonical valid status with high B2B outbound quality and without role-based or catch-all signals.

Canonical status stays valid
B2B outbound quality is high
Role-based and catch-all signals are false

How the contract defines it

The public validation contract classifies high-value from result signals, not from a separate status. Every other canonical status is never high-value.

Requires canonical status valid with high B2B outbound quality
valid_role_based, risky, invalid, and unknown are never high-value
Role-based or catch-all signals disqualify an otherwise valid result

Why it matters

Raw valid counts can overstate list quality. High-value validation separates send-worthy personal addresses from results that may need suppression, caution, recovery, or manual review.

Reporting and summaries

Validation summaries count each canonical status in its own bucket and expose high_value as a separate counter distinct from valid. Comparing high_value against total is a more honest list-quality measure than the raw valid count.

high_value is a derived counter, not a sixth status
Each canonical status keeps its own summary bucket
Use high_value over total to judge list quality and spend

Related resources

Email Validation API Cost per usable lead Email validation credit policy Invalid email validation result

Common questions

Is every valid email high-value?

No. A valid result can still be role-based, catch-all, or low-quality for B2B outbound, so high-value validation is a narrower outcome.

Is high-value a separate validation status?

No. Canonical statuses are valid, valid_role_based, invalid, risky, and unknown. High-value is a classification layered on valid results with high B2B outbound quality.

How does high-value validation relate to credit charging?

Credits are reserved before execution and consumed only for chargeable high-value validations. Non-chargeable and failed paths are refunded rather than consumed.