Phone Intel V2

Introduction

The Phone Intel V2 API facilitates real-time phone number validation and retrieval of essential information associated with a given mobile number for businesses. This API offers a seamless solution to verify mobile numbers, check subscriber status, determine connection type, identify service providers, and ascertain network regions, all without requiring OTP authentication from the end customer.

Key Features

Real-Time Validation: Enables businesses to validate mobile numbers in real-time.

Subscriber Status Check: Provides information about the subscriber status associated with the mobile number.

Connection Type Determination: Determines whether the mobile number is prepaid or postpaid.

Service Provider Identification: Identifies the current service provider associated with the mobile number.

Network Region Ascertainment: Determines the network region of the mobile number.

Applications

Business Verification: Useful for businesses to verify the accuracy of mobile numbers provided by customers.

Service Provisioning: Assists in determining the type of service (prepaid or postpaid) to be provisioned based on the mobile number.

Marketing Campaigns: Helps in targeting marketing campaigns by identifying the network region of users.

Conclusion

In conclusion, the Phone Intel API offers businesses a powerful tool for real-time phone number validation and retrieval of essntelential information without requiring OTP authentication. With its array of features, this API serves various applications, from business verification to marketing campaigns, enhancing efficiency and accuracy in mobile number-related processes.

API Details

Endpoints

curl --location 'https://api.signzy.app/api/v3/phones/phone-kyc-non-consent' \
--header 'Content-Type: application/json' \
--header 'Authorization: <Auth Token>' \
--data '{
    "mobileNumber": "70*****117",
    "additionalDetails": "yes"
}'

Request Body Parameters

Parameter	Data Type	Description	Required
mobileNumber	String	The mobile number to be validated.	Mandatory
additionalDetails	String	Possible values - "yes" and "no" (default). If it passed as "no", only customerName will be provided in the response. In order to get additional details, "yes" have to be passed explicitly.	Optional

{
    "mobileNumber": "<Mobile number>"
    "additionalDetails": "yes"
}

Request Headers

Name	Value	Required	Description
Content-type	application/json	Mandatory	The type of content that the request body contains.
Authorization	XXXXXXXXXXXXXXX	Mandatory	An authentication token to authorize the request. Reach out to the Signzy support team to get one created.

Code Samples

curl --location 'https://api-preproduction.signzy.app/api/v3/phones/phone-kyc-non-consent' \
--header 'Content-Type: application/json' \
--header 'Authorization:<Auth-Key>' \
--data '{
    "mobileNumber": "70*****117"
}'

Response Body Parameters

Parameter	Data Type	Description
customerName	String	The name of the customer associated with the provided mobile number, if available.
alternateNumber	String	An alternate mobile number associated with the customer, if available.
isValid	String	Indicates whether the provided mobile number is valid (true) or not (false).
subscriberStatus	String	The status of the mobile number's subscriber. Possible Values: ‘CONNECTED’ /’ UNDETERMINED’
connectionType	String	The type of connection associated with the mobile number, typically "prepaid" or "postpaid."
currentServiceProvider	String	The current mobile service provider associated with the mobile number.
originalServiceProvider	String	The original service provider from which the mobile number was obtained.
networkRegion	String	The region or location associated with the current service provider of the mobile number.
isPorted	String	Indicates whether the mobile number has been ported (true) or not (false).

{
    "error": {
        "statusCode": 400,
        "status": "Bad Request",
        "message": "Mobile number is invalid",
        "id": "09f513fd-a7f0-4155-9f13-b6f45d0525d3"
    }
}

Notes:

1) The coverage rate for the customer name is 80% which means in 80% of the cases we will be able to provide the customerName. This is because in some cases the source portal managed by the respective network operators will not have the customer's details like name, alternate contact number, etc.

2) There may be cases where the customerName fetched from this API may not match with the actual customer name. This can happen if the SIM was registered on a different name but is now being used by another individual.

Contact Us for Any Assistance

If you have any questions or need assistance, please reach out to our customer support team. You can contact us via email at [email protected]. We strive to provide prompt and reliable assistance, ensuring your queries are addressed effectively.

We value your feedback and are committed to making your experience smooth and enjoyable. Our team is dedicated to assisting you with any needs you may have. Thank you for choosing our services. We look forward to helping you!