Skip to main content
GET
Phone Intelligence API
It’s very simple to use: you only need to submit your API key and a phone number, and the API will respond with enriched intelligence data including carrier details, line type, location, messaging gateways, registration info, risk scoring, and breach history.

Getting started

REST

The Phone Intelligence API, like all of Abstract’s APIs, is organized around REST. It is designed to use predictable, resource-oriented URL’s and to use HTTP status codes to indicate errors.

HTTPS

The Phone Intelligence API requires all communications to be secured TLS 1.2 or greater.

API Versions

All of Abstract’s API are versioned. The Phone Intelligence API is currently on Version 1.

Your API Key

Your API key is your unique authentication key to be used to access Abstract’s Phone Intelligence API. Note that each of Abstract’s API has a unique API key, so you will need different keys to access the Phone Intelligence and Email Reputation APIs, for example. To authenticate your requests, you will need to append your API key to the base URL.

Base URL

Validation endpoint

Abstract’s Phone Intelligence API simply requires your unique API key and the phone number you’d like to check:
This was a successful request, so the valid phone number and details associated with it are returned below:

Request parameters

String
required
Your unique API key. Note that each user has unique API keys for each of Abstract’s APIs, so your Phone Validation API key will not work for your IP Geolocation API, for example.
String
required
The phone number to validate and verify.
String
The country’s ISO code. Add this parameter to indicate the phone number’s country, and the API will append the corresponding country code to its analysis. For instance, add country=US to indicate that the phone number is from the United States.

Response parameters

The API response is returned in a universal and lightweight JSON format.
String
The phone number submitted for analysis.
Object
The object containing the international and national formats of the submitted number.
String
The international format of the submitted phone number (e.g. “+1…”).
String
The local/national format of the submitted phone number.
Object
The object containing details about the carrier.
String
The carrier that the number is registered with.
String
The type of line. Possible values: mobile, landline, voip, toll_free, personal, pager, unknown.
Integer
Mobile Country Code (MCC).
Integer
Mobile Network Code (MNC).
Object
Geographic details about the phone number.
String
The name of the country.
String
The ISO 3166-1 alpha-2 country code.
String
The calling code prefix.
String
The region, province, or state associated with the number.
String
The city associated with the number.
String
The timezone associated with the number.
Object
Messaging gateway details for the number.
String
The SMS domain associated with the number’s carrier.
String
The email-to-SMS address associated with the number.
Object
Validation and status information for the number.
Boolean
Whether the number is valid and dialable.
String
The line status (e.g. active, inactive).
Boolean
Whether the number is a VOIP line.
Integer
The minimum estimated age of the number, in days.
Object
Registration details for the number.
String
The registered name associated with the number.
String
The type of registrant (e.g. consumer, business).
Object
Risk assessment for the number.
String
The assessed risk level (e.g. low, medium, high).
Boolean
Whether the number is disposable or temporary.
Boolean
Whether abuse or spam activity has been detected for this number.
Object
Breach history associated with the number.
Integer
The total number of known breaches involving this phone number.
String
The date of the first known breach.
String
The date of the most recent known breach.
Array
The list of domains where this number appeared in a breach, including the date of the breach.

Bulk upload (CSV)

Here are some best practices when bulk uploading a CSV file:
  • Ensure the first column contains the phone numbers to be analyzed.
  • Remove any empty rows from the file.
  • Include only one phone number per row.
  • The maximum file size permitted is 50,000 rows.

Response and error codes

Whenever you make a request that fails for some reason, an error is returned also in the JSON format. The errors include an error code and description, which you can find in detail below.

Code samples and libraries

Please see the top of this page for code samples for these languages and more. If we’re missing a code sample, or if you’d like to contribute a code sample or library in exchange for free credits, email us at: team@abstractapi.com

Other notes

A note on metered billing: Each individual phone number you submit counts as a credit used. Credits are also counted per request, not per successful response. So if you submit a request for the (invalid) phone number “kasj8929hs”, that still counts as 1 credit.