Original Carrier
The Original Carrier insight provides low-latency information about the carrier and network type originally associated with a phone number, using Vonage’s proprietary Numbering Plan intelligence. It offers metadata without requiring live queries to third party suppliers or operators, making it fast and reliable for many use cases.
While this insight focuses on the original assignment rather than any subsequent changes, therefore not reflecting portability changes, it remains highly valuable for identifying the nature of a phone number. It can indicate whether a number was initially designated as mobile, landline, toll-free, premium-rate, or virtual—categories often relevant for fraud prevention, cost control, and user qualification.
Key benefits include:
- Fraud risk signals: Spot virtual, premium, or high-risk number types that may indicate impersonation or artificially inflated traffic.
- Cost efficiency: Avoid engaging with expensive or invalid numbers early in the process.
- Data quality: Pre-screen leads and customer records by understanding the number’s origin.
Original Carrier is ideal for businesses looking to streamline communications, reduce artificial inflated traffic, and optimize their number-based workflows with lightweight intelligence.
Prerequisites
To use Identity Insights, you must ensure your account is configured correctly; see the Getting Started guide for more information on:
- Creating your account,
- Creating a Vonage application for use with the Identity Insights API,
- The different environments available and how to configure your account to use them,
- And how to use the Dashboard Getting Started UI to use the API without writing any code.
This guide will explain how to use the Original Carrier Insight programatically using cURL.
Making an API Call
Authentication for the Identity Insights API is done via JWTs, a compact and self-contained JSON token. To generate a JWT, you can use our online generator, or alternatively use the Vonage CLI. You will need your application ID and private key to generate the JWT. Once you have your JWT, you can send a request to the API.
This example shows a cURL request for the Original Carrier insight:
curl -X POST https://api-eu.vonage.com/v0.1/identity-insights \
-H "Authorization: Bearer $JWT" \
-H "Content-Type: application/json" \
-d '{
"phone_number": "14040000000",
"purpose": "FraudPreventionAndDetection",
"insights": {
"original_carrier": {}
}
}'
The API will then return information about the network the phone number is currently assigned to, including the name, network type, and country code:
{
"request_id": "c2cc7a65-9b10-493f-9c0a-1c86751a91c4",
"insights": {
"original_carrier": {
"name": "Orange Espana, S.A. Unipersonal",
"network_type": "MOBILE",
"country_code": "ES",
"network_code": "21403",
"status": {
"code": "NO_COVERAGE",
"message": "Success"
}
}
}
You'll see the following fields in the original_carrier array:
| Field | Description |
|---|---|
name | The full name of the original carrier associated with the phone_number provided. This is applicable to mobile numbers only. |
network_type | The type of network that phone_number is associated with. Will be one of MOBILE, LANDLINE, TOLLFREE, PREMIUM, VIRTUAL. |
country_code | Two character country code for phone_number. This is in ISO 3166-1 alpha-2 format. |
network_code | Mobile country codes (MCC) + Mobile network codes (MNC). E.212 International mobile subscriber identity. |
status | Indicates the status of the information returned for the specified phone number. |
code | Code indicating the status of the request. Must be one of: NO_COVERAGE: The country or mobile network is not supported by available suppliers. INVALID_PURPOSE: The purpose used is not valid or allowed for this Insight. UNAUTHORIZED: The request could not be authorized for the combination of application, supplier, and phone number. INTERNAL_ERROR: An internal error occurred while processing the request. SUPPLIER_ERROR: The supplier returned an error while processing the request. NOT_FOUND: The phone number could not be found for this Insight. INVALID_NUMBER_FORMAT: The phone number format is not valid for assignment by carriers to users. PARTIAL_SUCCESS: Some response attributes were omitted because they are not applicable or were not available. OK: All Insight attributes are available and included in the response. |
message | More detailed status description. |
Further Reading
- Read more about the Identity Insights API in the API Reference.
- If you have any questions, you can reach out to us on the Vonage Community Slack.