ANI-Based Authentication allows customers to send a phone number through our API, after which we query our database and return relevant information associated with that ANI in pre-defined fields. Businesses use this data to verify identities, validate account ownership, reduce fraud risk, and support critical decision-making processes based on their specific industry needs and use cases.

The LRN ONLY API allows you to dip into the database to get the Local Routing Number (LRN) for any number in the USA. 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.
API Call Response: LRN
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.
API Call Response: ANI, LRN, COC Type, Carrier Type, OCN, City, State, Ported Status, Ported Date.
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.
API Call Response: ANI Type, LRN Type, LERG Type
The CNAM LOOKUP API will retrieve information for a specific ANI from the CNAM central database to provide the name identification of the calling party.
API Call Response: CNAM
The INSIGHT LOOKUP API is the most informational API call of them all. You send us the ANI and we return information to you from several databases: LRN, CNAM, and LERG.
API Call Response: CNAM, ANI, LRN, COC Type, Carrier Type, OCN, Carrier, City, State, Ported Status, Ported Date, Time Zone
ANI type intelligence is used to identify the carrier and phone line type, such as mobile, landline, fixed VoIP, non-fixed VoIP, toll free, and more. Let me explain how this group of validations work.
You will send us the ANI and ANI2 information from your live call. We will look up the NPA-NXX from the LERG to get the assigned line type for that NPA-NXX. If that line type matches the ANI2 information sent to us from the call stream, the data is considered a match and the appropriate validation code of 0 is sent back to you. If the data does not match, then a validation code of 1 is sent back to you. You can use that information to determine the call treatment in your business.

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)
The VALIDATE BY ANI ENHANCED 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.
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)
The VALIDATE BY LRN ENHANCED 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.

Two-Factor Authentication (2FA) is a security method requiring two distinct forms of identification to access an account: a password (something you know) and a second factor like an SMS code or email code. It dramatically improves account security by blocking unauthorized access even if your password is stolen
Two-Factor Authentication (2FA) allows you to add an extra layer of identity protection to your service or systems to ensure users are who they say they are.
We use cookies to analyze website traffic and optimize your website experience. By accepting our use of cookies, your data will be aggregated with all other user data.