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.
API Response: LRN
API Response: ANI, LRN, Line Type, Carrier Type, OCN, City, State, Ported Status, Ported Date
API Response: ANI Type, LRN Type, LERG Type
API Response: CNAM
API Response: CNAM, ANI, LRN, Line Type, Carrier Type, OCN, Carrier, City, State, Ported Status, Ported Date, Time Zone
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 line type 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.
API Response: (Result of ANI/ANI2 Validation Test – Valid 0 or Invalid 1)
API Response: (Result of ANI/ANI2 Validation Test – Valid 0 or Invalid 1), OCN, LOC_Name, LOC_State, OCN_Name, Category, OCN_State, Sub_Type.
API Response: (Result of ANI/ANI2 Validation Test – Valid 0 or Invalid 1)
API Response: (Result of LRN/ANI2 Validation Test – Valid 0 or Invalid 1), OCN, LOC_Name, LOC_State, OCN_Name, Category, OCN_State, Sub_Type.
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.