LRN ONLY LOOKUP
LRN ONLY LOOKUP
LRN ONLY LOOKUP
The LRN ONLY LOOKUP API returns the Local Routing Number (LRN) for any U.S. telephone number, helping carriers, communications platforms, and fraud prevention providers make accurate routing and authentication decisions. Each ported telephone number is associated with an LRN, which directs calls through the Public Switched Telephone Network (PSTN) to the correct servicing switch. Most USA carriers use LRN data to ensure correct routing and billing. You send us the ANI and we return the LRN to you if there is one.
Here is the information that we send to you.
API Call Response - The data we send you!
LRN
LRN INFO LOOKUP
LRN ONLY LOOKUP
LRN ONLY LOOKUP
The LRN INFO API allows you to get the Local Routing Number (LRN) for any number in the USA plus additional useful information related to the ANI. You send us the ANI and we return the data back to you.
Here is the information that we send to you.
API Call Response - The data we send you!
ANI, LRN, COC Type, Carrier Type, OCN, City, State, Ported Status, Ported Date.
ANI TYPE LOOKUP
LRN ONLY LOOKUP
ANI TYPE LOOKUP
This ANI TYPE LOOKUP API call delivers exactly what it sounds like. You send us the ANI and we return the ANI Type, the LRN Type, and the LERG Type. You can use the information in your decision-making.
Here is the information that we send you.
API Call Response
ANI Type, LRN Type, LERG Type
CNAM LOOKUP
INSIGHT LOOKUP
ANI TYPE LOOKUP
The CNAM LOOKUP API identifies the name associated with a telephone number, helping businesses verify caller identities, improve customer interactions, and reduce uncertainty during authentication workflows. One request. Multiple trusted telecom data sources. Complete phone number intelligence.
Here is the information that we send you.
API Call Response: CNAM
INSIGHT LOOKUP
INSIGHT LOOKUP
INSIGHT LOOKUP
The INSIGHT LOOKUP API combines CNAM, LRN, and LERG intelligence into a single response, providing the most comprehensive view available for a telephone number. . You send us the ANI and we return information to you from several databases: LRN, CNAM, and LERG.
Here is the information that we send you.
API Call Response: CNAM, ANI, LRN, COC Type, Carrier Type, OCN, Carrier, City, State, Ported Status, Ported Date, Time Zone
VALIDATE BY ANI
VALIDATE BY ANI
VALIDATE BY ANI
The VALIDATE BY ANI API call is used as a first line of defense to determine if an ANI has been spoofed. You will send us the ANI and ANI2 information from your live call. Our system then performs a series of proprietary validation checks using industry-standard routing and carrier assignment data to verify that the ANI2 information is consistent with the originating telephone number information provided.
If the data passes validation, the API will return a validation code of 0 indicating a successful match. If the information does not pass validation, the API will return a validation code of 1 indicating the data could not be verified.
API Call Response: (Result of ANI/ANI2 Validation Test – Valid 0 or Invalid 1)
VALIDATE BY LRN
VALIDATE BY ANI
VALIDATE BY ANI
The VALIDATE BY LRN API call operates similarly to the VALIDATE BY ANI API call. You will provide the ANI and ANI2 information obtained from your live call stream. Our system then performs a series of proprietary validation checks using industry-standard routing and carrier assignment data to verify that the ANI2 information is consistent with the originating telephone number information provided.
If the data passes validation, the API will return a validation code of 0 indicating a successful match. If the information does not pass validation, the API will return a validation code of 1 indicating the data could not be verified.
API Call Response: (Result of ANI/ANI2 Validation Test – Valid 0 or Invalid 1)
VALIDATE BY ANI ENHANCED
VALIDATE BY ANI ENHANCED
VALIDATE BY ANI ENHANCED
The VALIDATE BY ANI ENHANCED API is the same as the VALIDATE by ANI above but we return more information to you in the API call response.
API Call Response: (Result of ANI/ANI2 Validation Test – Valid 0 or Invalid 1), OCN, LOC_Name, LOC_State, OCN_Name, Category, OCN_State, Sub_Type.
VALIDATE BY LRN ENHANCED
VALIDATE BY ANI ENHANCED
VALIDATE BY ANI ENHANCED
The VALIDATE BY LRN ENHANCED API is the same as the VALIDATE by LRN above but we return more information to you in the API call response.
API Call Response: (Result of ANI/ANI2 Validation Test – Valid 0 or Invalid 1), OCN, LOC_Name, LOC_State, OCN_Name, Category, OCN_State, Sub_Type.
EMAIL ONE-TIME PASSCODE (OTP)
Email One-Time Passcode (OTP) is a secure authentication method that companies use as a "second" factor to verify a user's identity by sending a temporary, single-use passcode to their email address. The user must enter the correct code within a limited time period to complete the login, registration, password reset, or other protected action.
Email OTP adds an extra layer of security by confirming that the user has access to the email account associated with the application. Email OTP provides an independent verification factor that confirms the user has access to the email account associated with the transaction, adding an additional layer of security to authentication workflows.
Why Choose Authentication API?
Daily Database Updates
Access current carrier, routing, and portability information to support critical authentication and fraud-prevention decisions.
Fast API Response Times
Sub-second response times provide real-time access to carrier and phone number intelligence.
Simple REST Integration
Integrate quickly using standard REST APIs, batch processing options, or customized enterprise solutions.
Scalable API Architecture
Whether you process hundreds or millions of transactions, our infrastructure is built for reliability and growth.
Transparent Pricing
Start with prepaid access and pay only for what you use. Businesses with established usage can apply for postpaid billing options and customized pricing plans.
U.S. Telecom Intelligence Expertise
Our team understands carrier networks, number portability, routing data, and the real-world challenges of telecom authentication.