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
The ANI TYPE VALIDATIONS are 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 s
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.