Sinch pricing: phone validation API
Is Sinch yours? Write to us about this page. We invite selected tool providers to our WhatsApp group.
44% complete: 4 of the 9 key fields we checkSee the 9 fields
Contact usWe haven't run Sinch through our phone validation API benchmark yet.Sinch gives this plan's price on request. We rank 888 plans for phone validation APIs by price. Half the plans cost $3.376 per 1,000 phones or less.Botoi's $199 monthly plan is the cheapest paid plan per 1,000 phones: as little as $0.0066. Botoi's $199 monthly plan covers up to 1,000,000 phones a day.Data247, Foxentry and HLR Lookups are the best phone validation API providers in the Datacircle benchmark.
Plan: Contact sales Sinch's only plan
Call:
POST / v2/ projects/ {projectId}/ lookups Sinch's only callAPI: Phone validation API Sinch's only API
About this item
- Freshness. We don't know how fresh this plan's data is.
- 4 of the 9 key fields we check. Type, Carrier, Porting and roaming, Place.
- No public price. You ask Sinch for one.
- One call. You send
projectIdandnumbertoPOST /. You can also sendv2/ projects/ {projectId}/ lookups featuresandrndFeatureOptions.contactDate. - Who can get it: with conditions. Keep data: with conditions. Use data: with conditions.
Sinch: phone validation API alternatives
Sinch alternatives: every phone validation API provider ranked
We list other providers' plans with no public price.
| This planSinch, contact us | HLR Lookups, contact us, Postpaid account, POST /mnp-lookups | CallerAPI, contact us, Enterprise transparency $40,000+, GET /api/network-lookup/{phone} | Addressfinder, contact us | Trestle, contact us, Enterprise, GET /2.0/real_contact, Real Contact API, full | iDenfy, contact us | |
|---|---|---|---|---|---|---|
| Completeness | 44% | 44% | 44% | 44% | 44% | 44% |
| Billing | contact | contact | contact | contact | contact | contact |
| Enough for | not published | not published | 50,000,000 calls a month | not published | not published | not published |
| Freshness | unknown | live | live | live | stored | unknown |
| Who can get it | anyone with a Sinch Build Dashboard account and a use case Sinch approves, Canadian numbers also need a CLNPC license | verified businesses, subject to approval | anyone who agrees terms with CallerAPI sales ("Exact terms are set in your agreement") | anyone verifying data for their business purposes, one Addressfinder account per business | companies, with a business email address | anyone who books a demo with its sales team |
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-02.
- developers.sinch.com/_bundle/docs/number-lookup-api-v2/api-reference/number-lookup-v2.yaml?download
- developers.sinch.com/docs/number-lookup-api-v2/api-reference/errors
- developers.sinch.com/docs/number-lookup-api-v2/api-reference/number-lookup-v2/numberlookupv2
- developers.sinch.com/docs/number-lookup-api-v2/getting-started/
- developers.sinch.com/docs/number-lookup-api-v2/overview
- developers.sinch.com/docs/number-lookup-api-v2/terms-and-conditions
- sinch.com/phone-numbers/number-lookup-api/
Product details
The key fields this plan's answer can hold, then each filled column in its row on the sheet.
- Number, not in the answer
- Formats, not in the answer
- Validity, not in the answer
- Type
- Carrier
- Porting and roaming
- Place
- Risk, not in the answer
- Owner, not in the answer
| Billing | contact |
|---|
| Aggregators | none |
|---|
| Their pitch | Increase security, reduce costs, and optimize data travel. There’s no point in sending messages to outdated numbers – check first and send with confidence. |
|---|
| Countries | Worldwide |
|---|---|
| What it checks | numbering plan, carrier |
| Keep data | Upon termination of the Service for any reason, [...] Customer agrees to destroy all copies of the Number Lookup Data in its possession and certify to Sinch as to such destruction. |
| Use data | Sinch grants Customer, and Customer accepts from Sinch, a personal non-transferable and non-exclusive, term-based license and Right-To-Use (“RTU”) the Services, the Number Lookup Data, and any modified or enhanced data derived therefrom, solely for the following purposes: (i) to validate a consumer's identity for the purpose of averting fraudulent transactions, (ii) performing identity verification, (iii) authenticating commercial transactions initiated by a consumer with Customer, (iv) optimizing Customer's use of telecommunications services, including reducing costs of telecommunications, complying with applicable telecommunications rules, selecting a telecommunication service or service provider, (v) determine the validity of a TN, and (vi) billing. [...] Customer will not use the Services or Number Lookup Data (a) for marketing purposes or market analysis, (b) to resell or provide the Number Lookup Data to any third party, (b) to create a consumer report or allow use by a consumer reporting agency for the purpose of creating a consumer report, (c) for verifying credit worthiness or eligibility, insurance, or employment, (d) to augment or create a consumer segmentation database, or (e) for any other purpose(s) not specifically set forth in Section 2.1. Customer must submit an application that sets forth a true, accurate, and complete description of Customer's intended use case(s) for the Services (the “Use Case”), which complies with the Right to Use and Restrictions set forth above. [...] Customer agrees: (i) to not use the Service or Number Lookup Data for illegal purposes, (ii) not to interfere or disrupt networks connected to the Service, and, (iii) to comply with all applicable laws and regulations. |
| Per second | 10 |
|---|---|
| Batch | 1 |
| Answer | in the call |
|---|
| You send | projectId, number. Optional: features, rndFeatureOptions.contactDate |
|---|---|
| Method | POST |
| Path | /v2/projects/{projectId}/lookups |
| Plan | Contact sales |
|---|---|
| Who can get it | anyone with a Sinch Build Dashboard account and a use case Sinch approves, Canadian numbers also need a CLNPC license |
The 13 fields the plan's answer can hold
E.164 number, country code, line type, carrier, mobile country code, mobile network code, ported, ported date, SIM swapped, SIM swap period, VoIP probability, disconnected, trace ID