Landline SMS lookup
Landline SMS lookup: find the landlines that can receive texts
Find out whether a US or Canadian landline can receive text messages and, if it can, which messaging provider serves it. About 7% of the landlines we check can. Without this check they look like any other landline and drop out of your SMS sends.
- +1 credit, landlines only
- Mobiles never charged
- Works on CSV uploads
| Number | The lookup says | Do this |
|---|---|---|
| (415) 555-0102 | Mobile | Text it |
| (415) 555-0176 | Landline, messaging enabled | Text it |
| (212) 555-0144 | Landline, messaging not enabled | Call it |
Fictional 555 numbers. Only the two landlines use the extra credit.
- ~32% of numbers we look up are landline or VoIP
- ~7% of landlines we check can take a text
How the check works
- Step 1
Turn it on
Add
"landlineSmsLookup": trueto aPOST /v1/lookuprequest, or tick "Landline SMS lookup" on a bulk CSV upload. - Step 2
We check landlines only
The normal lookup runs first, live carrier dip included. If the number is a landline, we also run the messaging lookup. Mobiles skip it: no
dipMessaging*fields and no extra credit. - Step 3
Read the answer
For an SMS-capable landline,
dipMessagingEnabledis"true", the provider fields are filled in, andsmsEligiblecomes back"true".
The five dipMessaging fields
| Field | Example | Meaning |
|---|---|---|
dipMessagingLookup | "true" | Present only when landlineSmsLookup: true is set and the lookup actually ran, i.e. the number is a landline: "true". Absent for mobile numbers (the lookup does not apply and is not charged) and when the add-on is not requested. |
dipMessagingEnabled | "false" | Returned only when landlineSmsLookup: true is set. "true" if landline messaging is enabled for this number. Only meaningful alongside dipMessagingLookup: "true". |
dipMessagingProvider | "Google (Grand Central) - SVR" | Name of the messaging provider serving this landline number. Populated only when the landline messaging lookup returned a positive match. |
dipMessagingRefId | "us_acme" | Messaging provider's reference ID for this number. |
dipMessagingCountryCode | "US" | Two-letter country code of the messaging provider. |
The base field smsEligible is "true" for an active mobile, or for a landline this check confirmed as SMS-capable. Its inverse, doNotSms, marks numbers that can't take a text.
Example request and response
A response excerpt for a text-enabled landline, with the carrier, deliverability and location fields left out for space.
Request
curl --request POST \
--url 'https://api.checkthatphone.com/v1/lookup' \
--header 'Authorization: Bearer YOUR_API_KEY' \
--header 'Content-Type: application/json' \
--data '{"phone": "(415) 555-0176", "landlineSmsLookup": true}' credits_used: 2 is one credit for the lookup and one for the landline SMS check. The same request for a mobile number shows credits_used: 1 and no dipMessaging* fields.
Highlighted fields in the response: dipMessagingLookup, dipMessagingEnabled, dipMessagingProvider, smsEligible.
{
"success": true,
"credits_used": 2,
"data": {
"subscriber": "4155550176",
"dip": "success",
"dipCarrierType": "landline",
"dipMessagingLookup": "true",
"dipMessagingEnabled": "true",
"dipMessagingProvider": "Google (Grand Central) - SVR",
"dipMessagingRefId": "us_acme",
"dipMessagingCountryCode": "US",
"smsEligible": "true",
"error": "false"
}
} Routing on the result
Being able to receive a text is not the same as consent to receive one. Your consent records still decide who you can message, and the TCPA litigator scrub can run in the same call.
| If the response shows | Field | Do this |
|---|---|---|
| Mobile | dipCarrierType = mobile | Text as usual. No extra credit was charged. |
| Landline that can take texts | dipMessagingEnabled = truedipMessagingProvider | SMS-capable: it can go on the SMS list. |
| Landline that can't | dipMessagingEnabled = false | Route it to a voice queue or leave it out of the SMS send. |
Pricing
The landline SMS lookup adds one credit per lookup, only when the number is a landline. Mobiles pay the base credit and nothing more. On a 10,000-number list with 2,000 landlines, the add-on adds 2,000 credits, for 12,000 in total.
- Free $0/mo 500 lookups included Hard cap, no overage
- 1K $5/mo 1,000 lookups included Then $0.005 each
- 10K $30/mo 10,000 lookups included Then $0.003 each
- 100K $100/mo 100,000 lookups included Then $0.001 each
- 500K $450/mo 500,000 lookups included Then $0.0009 each
Failed lookups are free. Annual billing is 15% off. Above 500,000 lookups a month, ask for a volume quote. Every detail is on the pricing page.
Landline SMS lookup: common questions
What is a text-enabled landline?
A landline number with messaging enabled through a messaging provider, so it can receive SMS while voice calls still go to the landline. The lookup reports whether that is the case (dipMessagingEnabled) and which provider handles the texts (dipMessagingProvider).
How many landlines can receive SMS?
About 7% of the landlines we check are SMS-capable. Without the check, those numbers look like any other landline.
Am I charged for mobile numbers?
No. The check only runs on landlines. For a mobile number the dipMessaging* fields are left out and no extra credit is charged.
Does it work on a whole list?
Yes. Tick "Landline SMS lookup" when you upload a CSV from the dashboard; the result file then includes the five dipMessaging* columns. See bulk phone validation.
Do I still get the voice carrier?
Yes. The voice carrier comes from the live carrier dip (dipCarrier) on every lookup. The messaging provider is a separate field (dipMessagingProvider).
Find the landlines on your list that take texts
The Free plan includes 500 lookups a month, hard-capped. Paid plans start at $5 a month.