Understand verification terms before you build policy around them.
Technical and operations teams use the same words differently. This glossary defines how phoneveriflo uses important data-quality, API, cache, and workflow terms.
Core data terms
Use these definitions consistently across UI, docs, exports, and support.
E.164
An international phone-number representation beginning with + and country code. Formatting alone is not validation.
Normalized input
A cleaned representation used for matching, deduplication, and supported verification workflows.
Exact duplicate
The same normalized value appearing more than once in the relevant preflight scope.
External ID
A customer-supplied row or record identifier used to reconcile results back to the source system.
Verification and freshness terms
Make time and uncertainty explicit.
Fresh check
A request the phoneveriflo job sends for new processing rather than serving an eligible phoneveriflo cache entry.
Cache hit
A reusable result found under the configured service/schema/scope and still inside its TTL.
Checked at
The timestamp when the underlying result was originally produced.
TTL
Time-to-live: how long an eligible cached result may be reused under the configured policy, capped at 90 days in this application.
Network metadata terms
Carrier and line-type fields are metadata returned by supported lookup services; they are not identity or ownership proof.
API workflow terms
Idempotency prevents accidental duplicate writes; a webhook is a signed server-to-server event; a job is the first-party asynchronous unit of work; a normalized result is the customer-facing schema independent of the upstream provider.
Questions about glossary
Is E.164 the same as a valid phone number?
No. It describes formatting/representation, not reachability, ownership, or current service status.
Does cached mean inaccurate?
No. It means the result was originally checked earlier and is being reused within a configured TTL. The checked time should always remain visible.
What is a line type?
A network classification such as mobile or landline when returned by a supported carrier lookup.
What is idempotency?
A request-safety pattern that allows a client to retry a write without unintentionally creating duplicate work when supported by the API.
Related verification solutions
Explore related verification capabilities, documentation, and pricing.
See the job composition before you commit.
Start with a free preflight scan. Review duplicate counts, syntax formatting, cache eligibility, and the frozen maximum quote in integer micros.