DIDLogic pricing: phone validation API
Is DIDLogic yours? Write to us about this page. We invite selected tool providers to our WhatsApp group.
78% complete: 7 of the 9 key fields we checkSee the 9 fields
$0.00per 1,000 phonesWe haven't run DIDLogic through our phone validation API benchmark yet.This plan is free. 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: Promo one of DIDLogic's 4 plans
Call:
POST / DIDLogic's only callAPI: Phone validation API DIDLogic's only API
About this item
- Live. DIDLogic 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, Risk.
- Nothing to pay.
- One call. You send
numberstoPOST /. The call returns a job. You fetch the answer once the job is done.api/ v2/ hlr - Who can get it: with conditions. Keep data: no API terms. Use data: no API terms.
DIDLogic: phone validation API alternatives
DIDLogic alternatives: every phone validation API provider ranked
We list other providers' plans closest to this plan in price per 1,000 phones. Each plan in the table gives live data.
| This planDIDLogic, free | Foxentry, free trial, POST /phone/validate, Validate phone number (extended) | HLR Lookups, free, 100 free lookups, POST /hlr-lookups | seven.io, free test credit, GET /api/lookup/hlr | HLR Lookup, free, 200 free credits, POST /batches/{id}/sourcejson, Bulk uploads via API | Decision Telecom, free | |
|---|---|---|---|---|---|---|
| $ per 1,000 phones | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 |
| Completeness | 78% | 56% | 56% | 78% | 89% | 56% |
| Billing | free | free | free | free | free | free |
| Pay | $0 | $0 | $0 | $0 | $0 | $0 |
| Enough for | not published | not published | 100 results, once | not published | 200 results, once | not published |
| Freshness | live | live | live | live | live | live |
| Who can get it | anyone with an account, its API key comes through the account manager and the account decides which parts of the API are open to it | anyone who signs up and creates an API project | new accounts | new accounts of traders: the customer assures that he is a trader and that the short messages are sent as part of his business | new accounts with a business email address | anyone of legal age to form a binding contract, through a test account its managers create on request |
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
- Owner, not in the answer
| $ per 1,000 phones | $0.00 |
|---|---|
| Billing | free |
| Aggregators | none |
|---|
| Also pays for | from the same budget: Send SMS message · Create risk check |
|---|
| $ per 1,000 | $0.00 |
|---|
| Their pitch | Use HLR lookups to check number validity and risk checks to identify spam flags before adding numbers to your calling workflow. |
|---|
| Freshness | live |
|---|---|
| What it checks | numbering plan, carrier, line in service |
| Keep data | no API terms |
| Use data | no API terms |
| Pay | $0 |
|---|
| Batch | 1,500 |
|---|
| Answer | by polling |
|---|
| You send | numbers |
|---|---|
| Method | POST |
| Path | /api/v2/hlr |
| Plan | Promo |
|---|---|
| Who can get it | anyone with an account, its API key comes through the account manager and the account decides which parts of the API are open to it |
The 16 fields the plan's answer can hold
phone number, valid, lookup status, phone type, carrier, MCC, MNC, ported, risky, country, error code, price, task ID, log ID, processed at, created at