IMEI Verification

Endpoint Overview

POST /api/v1/imei/imei-verification

Description

The IMEI Verification API allows you to validate and retrieve detailed information about a mobile device using its International Mobile Equipment Identity (IMEI) number. This endpoint verifies the authenticity of a device and returns comprehensive details including the manufacturer, brand name, model, and verification status.

Key Benefits

Instantly verify the authenticity of mobile devices

Prevent fraud by identifying counterfeit or stolen devices

Access detailed device specifications for inventory management

Streamline device onboarding processes with reliable verification

Use Cases

Telecommunications

E-commerce

Insurance

Device verification during SIM activation or mobile number portability

Validating device compatibility with network services

Identifying blacklisted or stolen devices before service provision

Technical Implementation

Authentication

All API requests require authentication using a JWT Bearer token. Authentication follows these steps:

Obtain API Credentials: Register with Surepass to receive your API key.

Generate JWT Token: Use your API key to generate a JWT token.

Include in Requests: Add the token to the Authorization header as Bearer TOKEN.

Different authentication tokens are used for sandbox and production environments:

Sandbox: https://sandbox.surepass.io

Production: https://kyc-api.surepass.io

Request Parameters

Request Headers

Header	Required	Description
Authorization	Yes	Bearer token authentication using JWT format
Content-Type	Yes	Must be set to `application/json`

Request Body

Parameter	Type	Required	Description
imei	String	Yes	The International Mobile Equipment Identity number of the device to be verified (15-17 digits)

Example Request

{
    "imei": "867268074226205"
}

Process Response

Response Parameters

Parameter	Type	Description
data	Object	Container for the verification result data
data.client_id	String	Unique identifier for the verification request
data.imei	String	The IMEI number that was verified
data.brand_name	String	Brand name of the device (e.g., Samsung, Apple, 1+)
data.model_name	String	Model name and version of the device
data.manufacturer	String	Full name of the device manufacturer
data.device_type	String	Type of the device (e.g., Smartphone, Tablet)
data.status	String	Verification status of the device (e.g., Valid, Invalid)
status_code	Integer	HTTP status code of the response
success	Boolean	Indicates whether the request was successful
message	String	Human-readable description of the response
message_code	String	Machine-readable code for the response

Example Successful Response

{
    "data": {
        "client_id": "imei_verification_ueIckoGbgyMjzLvneoLW",
        "imei": "867268074226205",
        "brand_name": "1+",
        "model_name": "CPH2487",
        "manufacturer": "OnePlus Technology (Shenzhen) Co Ltd",
        "device_type": "Smartphone",
        "status": "Valid"
    },
    "status_code": 200,
    "success": true,
    "message": "Success",
    "message_code": "success"
}

Possible Error Responses

Invalid IMEI

Authentication Error

Server Error

{
    "status_code": 422,
    "success": false,
    "message": "Verification Failed",
    "message_code": "verification_failed"
}

The IMEI number provided is not in the correct format or does not exist.

Integration Best Practices

Security Recommendations

Store JWT tokens securely and never expose them in client-side code

Implement proper error handling to avoid exposing sensitive information

Validate IMEI numbers on your end before sending to the API to reduce unnecessary calls

Implement rate limiting in your application to prevent abuse

User Experience Guidelines

Provide clear feedback to users when an IMEI verification fails

Implement a loading state during API calls as verification may take a few seconds

Consider caching verified IMEI results to improve performance for repeat lookups

Display device details in a user-friendly format with appropriate labels

Code Samples

cURL

Python

Node.js

Related APIs

Device Blacklist Check - Verify if a device has been reported as stolen or lost

SIM Verification - Validate SIM card details and status

Device Specifications - Get detailed technical specifications for a device

Compliance and Legal Considerations

When implementing IMEI verification, be aware of data privacy regulations in your jurisdiction. The IMEI number is considered device identifiable information in many regions. Ensure you have appropriate consent from users before collecting and processing IMEI numbers, and clearly state the purpose of collection in your privacy policy.

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

curl --location --request POST 'https://kyc-api.surepass.app/api/v1/imei/imei-verification' \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data-raw '{ "imei": "867268074226205" }'

{ "data": { "client_id": "imei_verification_ueIckoGbgyMjzLvneoLW", "imei": "867268074226205", "brand_name": "1+", "model_name": "CPH2487", "manufacturer": "OnePlus Technology (Shenzhen) Co Ltd", "device_type": "Smartphone", "status": "Valid" }, "status_code": 200, "success": true, "message": "Success", "message_code": "success" }

IMEI Verification

IMEI Verification#

Description#

Use Cases#

Technical Implementation#

Request Headers#

Request Body#

Example Request#

Response Parameters#

Example Successful Response#

Possible Error Responses#

Integration Best Practices#

Code Samples#

Request

Responses

IMEI Verification

Description

Use Cases

Technical Implementation

Request Headers

Request Body

Example Request

Response Parameters

Example Successful Response

Possible Error Responses

Integration Best Practices

Code Samples