Migrate from Twilio Lookup to VeriRoute Intel

Why Developers Switch from Twilio Lookup

Twilio Lookup v2 covers the basics: LRN, CNAM, and carrier identification via a familiar REST API. For teams running low volumes it is convenient. For teams running millions of lookups per month — or for teams that need messaging provider identification for A2P routing decisions — it has two hard limits:

• Cost at scale. At $0.005/lookup, a contact center scrubbing 500,000 records pays $2,500. The same scrub on VRI costs $250 — a $2,250 saving on a single run.
• Missing messaging provider ID. Twilio Lookup returns the carrier of record. It does not tell you which company is actually delivering SMS to that number today. For A2P routing, compliance audits, and deliverability optimization, carrier-of-record is insufficient.

Pricing Comparison

Feature Comparison

Side-by-Side Code Examples

The two APIs share the same REST model — different base URL, different auth header format.

curl -X GET "https://lookups.twilio.com/v2/PhoneNumbers/+15555550123?Fields=line_type_intelligence,caller_name" \
  -u "TWILIO_ACCOUNT_SID:TWILIO_AUTH_TOKEN"

curl -X POST "https://api-service.verirouteintel.io/api/v1/lrn" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "phone_number": "15555550123",
    "include_enhanced_lrn": true,
    "include_cnam": true,
    "messaging_lookup": true
  }'

import requests

phone = "+15555550123"
response = requests.get(
    f"https://lookups.twilio.com/v2/PhoneNumbers/{phone}",
    params={"Fields": "line_type_intelligence,caller_name"},
    auth=("TWILIO_ACCOUNT_SID", "TWILIO_AUTH_TOKEN")
)
data = response.json()

carrier = data["line_type_intelligence"]["carrier_name"]
line_type = data["line_type_intelligence"]["type"]
caller_name = data["caller_name"]["caller_name"]

print(f"Carrier: {carrier}")
print(f"Line Type: {line_type}")
print(f"Caller Name: {caller_name}")

import requests

response = requests.post(
    "https://api-service.verirouteintel.io/api/v1/lrn",
    json={
        "phone_number": "15555550123",
        "include_enhanced_lrn": True,
        "include_cnam": True,
        "messaging_lookup": True
    },
    headers={"Authorization": "Bearer YOUR_API_KEY"}
)
data = response.json()

carrier = data["enhanced_lrn"]["carrier"]
carrier_type = data["enhanced_lrn"]["carrier_type"]
caller_name = data.get("cnam")
messaging_provider = data["messaging"]["provider"]   # No Twilio equivalent

print(f"LRN: {data['lrn']}")                         # No Twilio equivalent
print(f"Carrier: {carrier}")
print(f"Carrier Type: {carrier_type}")
print(f"Caller Name: {caller_name}")
print(f"Messaging Provider: {messaging_provider}")    # No Twilio equivalent

const axios = require('axios');

const phone = '+15555550123';
const response = await axios.get(
  `https://lookups.twilio.com/v2/PhoneNumbers/${phone}`,
  {
    params: { Fields: 'line_type_intelligence,caller_name' },
    auth: { username: 'TWILIO_ACCOUNT_SID', password: 'TWILIO_AUTH_TOKEN' }
  }
);

const { line_type_intelligence, caller_name } = response.data;
console.log('Carrier:', line_type_intelligence.carrier_name);
console.log('Line Type:', line_type_intelligence.type);
console.log('Caller Name:', caller_name.caller_name);

const axios = require('axios');

const response = await axios.post(
  'https://api-service.verirouteintel.io/api/v1/lrn',
  {
    phone_number: '15555550123',
    include_enhanced_lrn: true,
    include_cnam: true,
    messaging_lookup: true
  },
  { headers: { Authorization: 'Bearer YOUR_API_KEY' } }
);

const { lrn, enhanced_lrn, cnam, messaging } = response.data;
console.log('LRN:', lrn);                           // No Twilio equivalent
console.log('Carrier:', enhanced_lrn.carrier);
console.log('Carrier Type:', enhanced_lrn.carrier_type);
console.log('Caller Name:', cnam);
console.log('Messaging Provider:', messaging.provider); // No Twilio equivalent

Response Field Mapping: Twilio → VRI

What You Gain with VeriRoute Intel

• 10x lower LRN cost. $0.0005 vs $0.005. At 10 million lookups per month, that is $45,000 saved annually — budget that compounds as volume grows.
• Messaging provider identification. Know which company is actually routing SMS to any US number — Twilio, Bandwidth, Sinch, Syniverse, or others. No equivalent in Twilio Lookup at any price point. Critical for A2P routing, compliance, and deliverability diagnosis.
• Spam and reputation scoring. Built-in risk scoring surfaces numbers associated with high complaint rates, fraud patterns, or known spam campaigns. Replace a separate reputation API with a single VRI call.
• GraphQL option. Query only the fields you need in a single request and reduce response payload for high-throughput pipelines.

Step-by-Step Migration Checklist

Most codebases complete this migration in one to two days. The endpoint and auth header are different; the REST request/response model is the same.

1. Sign up for VeriRoute Intel. Create a free account at verirouteintel.com/register. 10 free lookups are included with no credit card required.
2. Copy your API key from the dashboard. Your API key appears under Account → API Keys immediately after registration.
3. Review the VRI API reference. The VRI API docs document all request parameters, response fields, error codes, and rate limits. Spend 15 minutes here before writing code.
4. Map Twilio Lookup response fields to VRI response fields. The field names differ. Use the field mapping table above to update every reference in your codebase. Key mappings: caller_name.caller_name → cnam; line_type_intelligence.type → enhanced_lrn.carrier_type; line_type_intelligence.carrier_name → enhanced_lrn.carrier.
5. Update the API endpoint URL in your codebase. Replace https://lookups.twilio.com/v2/PhoneNumbers/ with https://api.verirouteintel.com/v1/lookup.
6. Update authentication headers. Twilio uses HTTP Basic Auth (Account SID + Auth Token). VRI uses a Bearer token: replace your Basic auth header with Authorization: Bearer YOUR_VRI_API_KEY.
7. Update response parsing logic. Use the field mapping from Step 4 to update every place your code reads the lookup response. If you use data classes or DTOs, update those models first; the rest of the code will surface type errors automatically.
8. Test with a sample of 50–100 numbers. Run your updated integration against a representative sample. Compare the VRI output against stored Twilio output for the same numbers to validate correctness.
9. Run parallel comparison for 48 hours. Route live traffic through both APIs simultaneously and compare results. Log any discrepancies. VRI may return richer data for ported numbers where Twilio returns the original carrier.
10. Cut over fully to VRI. Remove the Twilio Lookup integration. Verify error monitoring shows no unexpected failures. Decommission unused Twilio API keys.

Frequently Asked Questions

Related Articles