TMT ID pricing: phone validation API, POST / v3/
Is TMT ID yours? Write to us about this page. We invite selected tool providers to our WhatsApp group.
POST / v3/ one of TMT ID's 2 callsAbout this item
- Live. TMT ID checks the phone number you send when you call the API.
- 7 of the 9 key fields we check. Number, Validity, Type, Carrier, Porting and roaming, Place, Owner.
- No public price. You ask TMT ID for one.
- One call. You send
numbertoPOST /. You set thev3/ Content-Typeheader to "application/json". You can also senddpointsandkyc_. The call returns whether the number is valid.challenges - Who can get it: customers that agree a contract and are approved on their customer and use case. Keep data: no API terms. Use data: no API terms.
TMT ID: phone validation API alternatives
TMT ID alternatives: every phone validation API provider ranked
We list other providers' plans with no public price. These plans come closest to this plan in number of key fields. Each plan in the table gives live data.
| This planTMT ID, contact us, Contract, POST /v3/ | Veriphone, contact us, Need more?, GET /v3/verify, /v3/verify, full | Didit, contact us | Loqate, contact us | Neutrino API, contact us | |
|---|---|---|---|---|---|
| Completeness | 78% | 78% | 78% | 78% | 78% |
| Billing | contact | contact | contact | contact | contact |
| Freshness | live | live | live | live | live |
| Who can get it | customers that agree a contract and are approved on their customer and use case | anyone | Enterprise customers who sign an Order Form referencing the Master Services Agreement | anyone | anyone paying by Visa, Mastercard or SWIFT |
Sources
From each provider's own pricing page and docs, and from what providers tell us. We read this row from these pages on 2026-11-04.
Product details
The key fields this plan's answer can hold, then each filled column in its row on the sheet.
- Number
- Formats, not in the answer
- Validity
- Type
- Carrier
- Porting and roaming
- Place
- Risk, not in the answer
- Owner
| Billing | contact |
|---|
| Aggregators | none |
|---|
| Their pitch | Verify and validate customers globally using their phone number |
|---|
| Freshness | live |
|---|---|
| Countries | Worldwide |
| What it checks | numbering plan, carrier, line in service, messaging apps |
| Keep data | no API terms |
| Use data | no API terms |
| Batch | 1 |
|---|
| Answer | in the call |
|---|
| You send | number, Content-Type header "application/json". Optional: dpoints, kyc_challenges |
|---|---|
| Method | POST |
| Path | /v3/ |
| Plan | Contract |
|---|---|
| Who can get it | customers that agree a contract and are approved on their customer and use case |
The 51 fields the plan's answer can hold
number, status, status message, transaction ID, line type, enhanced line type, network name, network MCC, network MNC, network SPID, network LRN, network OCN, origin network name, origin network MCC, origin network MNC, origin network SPID, origin network OCN, ported, ported date, ported date type, porting history, subscriber present, is roaming, roaming MCC, roaming MNC, last deactivation, deactivation history, SIM swap risk, SIM swap date, device swap risk, port fraud risk, TMT score, online presence, age verification, age threshold, first name match score, last name match score, middle name match score, name match score, date of birth match score, street number match score, street match score, unit number match score, city match score, province match score, postcode match score, country match score, address match score, email match score, call forwarding, market segment