RexaThe short answer
Numverify answers a narrower question than a Do-Not-Call check: is this number valid, and is it a mobile, a landline or a VoIP line. Rexa runs it platform-side on a single key, so there is nothing for you to connect or pay for. Line type is the field that matters most, because several calling rules and most list-hygiene decisions turn on it.
Last reviewed
What does the check return?
Rexa calls the vendor’s validate endpoint with the number and an ISO country code, and persists two fields: whether the number is valid, and the line type where the vendor supplies one — mobile, landline or VoIP.
The vendor also returns carrier and location information. Rexa does not currently store those, so do not build a process that expects them to be available on a session record.
How does this differ from the Do-Not-Call check?
They answer different questions and are implemented as separate vendor interfaces rather than one combined provider. A Do-Not-Call check tells you whether you are permitted to call the number. A validity check tells you whether calling it is worth the attempt at all.
The separation is also practical: validity checking can be toggled independently of DNC, and the screening gate short-circuits — a number already blocked by DNC is never sent for validity lookup.
Why does line type matter?
Because rules and economics both depend on it. In several jurisdictions the obligations attached to calling a mobile differ from those attached to a landline, and your own list hygiene usually treats an unexpectedly high share of VoIP numbers as a signal about where the list came from.
This page describes what the platform records, not what the law requires of you. Treat line type as an input to your own policy, and take legal advice on the policy itself.
What is there to set up?
Nothing. As with Do-Not-Call screening, the vendor key is held at platform level rather than per account, so validity checking is available without any tenant configuration.
Frequently asked questions
- Does a valid result mean the call will connect?
- No. Validity means the number is well formed and allocated, which rules out a large class of bad list data but says nothing about whether the line is in service today or whether anyone will pick up. Treat it as a filter, not a prediction.
- Can I bring my own Numverify key?
- No. The credential is platform-level, held once for the whole platform rather than per account. The trade is the same as with Do-Not-Call screening: no vendor contract and no per-check charge for you, but no direct vendor access either.
- Is line type stored on the record?
- Yes, whenever the vendor returns one — mobile, landline or VoIP — alongside the validity flag and the time of the check. Carrier and location are returned by the vendor but deliberately not persisted.
Scope, limitations, and sources
A "valid" result is a vendor opinion at a point in time, not a promise that the number will ring or that a person will answer — it says the number is well formed and allocated, nothing more. Carrier and location come back from the vendor but are not persisted, so they are not available downstream. The key is platform-level, so you cannot bring your own Numverify account, read its quota, or query the vendor directly through Rexa. A vendor outage is classified as retryable rather than silently treated as a pass. Nothing on this page is legal advice, and line type on its own does not establish that a call is permitted.
Sources
- Do-Not-Call screening, calling windows, consent handling and audit evidence. rexa.ai (accessed )
- The per-minute rate, what it includes, and how bring-your-own telecom is billed. rexa.ai (accessed )
Spotted something out of date or wrong? Tell us on the contact page and we will correct it and update the review date.