Check numbers before you send with Twilio
Twilio sends what your code tells it to send. Put a 1lookup.dev call in front of that: before your server asks Twilio to send an SMS or place a call, look the number up with the REST API and decide whether to proceed.
curl -X POST https://api.1lookup.dev/v1/phone-validation \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"phone_number":"+15125550142"}'Connect Twilio in 4 steps
The two services do not connect to each other. Your backend calls 1lookup.dev first and Twilio second. That keeps the logic in one place, and results are cached for 7 days, so repeat messages to the same number do not trigger a new charge.
- 1
Create a 1lookup.dev API key and store it with your other server secrets.
- 2
In the code path that sends a message or starts a call, POST the destination number to https://api.1lookup.dev/v1/phone-validation first.
- 3
Read valid and line_type from the response and continue to Twilio only when your rules pass.
- 4
Log the lookup result with the message record so you can review skipped numbers.
What to build with Twilio
Send SMS only to mobiles
Call Phone Validation before each first message. If line_type is not mobile, skip the SMS and fall back to a call or an email.
Confirm a number is live before a verification code
For international signups, run HLR Lookup to check that the number is reachable on its network before you spend on a one-time code.
Transcribe recorded calls
When Twilio reports that a call recording is ready, send a URL for the recording file to Audio Transcription and store the transcript with speaker labels.
Twilio is a trademark of its owner. This guide describes how to connect using our MCP server and REST API. 1lookup.dev is not affiliated with or endorsed by Twilio.
Run your first lookup in two minutes
Create a key, pick a plan and call any product in the catalog. Plans start at $29 a month.