NewAPIVerve Academy: free courses and certifications anyone can verify.Explore the Academy →

IMEI Generator API

GET

Populate test environments with valid, brand-matched IMEI numbers.

IMEI Generator creates valid International Mobile Equipment Identity (IMEI) numbers with proper Luhn checksum validation for mobile devices.

Try it — live request, no key required

Request
GETapi.apiverve.com/v1/imeigenerator?brand=Samsung
Query parameters
Verification
Format

No key required to try it. Get a key to use it in your app.

Example
{
  "status": "ok",
  "error": null,
  "data": {
    "count": 2,
    "brand": "Samsung",
    "imeis": [
      {
        "imei": "358398048517203",
        "tac": "35839804",
        "manufacturer": "Samsung",
        "model": "Galaxy Xcover",
        "serial": "851720",
        "checksum": "3",
        "isValid": true
      },
      {
        "imei": "359040029448038",
        "tac": "35904002",
        "manufacturer": "Samsung",
        "model": "SGH-B130",
        "serial": "944803",
        "checksum": "8",
        "isValid": true
      }
    ]
  }
}

About the IMEI Generator API

IMEI Generator produces 15-digit IMEI numbers in the correct International Mobile Equipment Identity structure, with a valid Luhn checksum, for testing and development. Returns test IMEI numbers with their serial number and Luhn checksum and a validation status, and lets you narrow the results to one manufacturer, such as Samsung.

QA teams use generated IMEIs to fill device registration forms, test input validation and checksum code, seed mobile device management and inventory systems with realistic device identifiers, and demo telecom or insurance apps without exposing a real customer's phone.

The Free plan returns one IMEI per request with its serial, check digit and validation flag. Paid plans can request several IMEI numbers in one call and add the Type Allocation Code, manufacturer and model that each IMEI was built from, so a generated device identifier can be shown alongside a believable handset name.

How it works

Each IMEI is assembled from three parts. The first eight digits are a Type Allocation Code taken from a TAC reference table that pairs each code with a manufacturer and model. Six random digits follow as the serial number. The fifteenth digit is the Luhn check digit computed over the first fourteen, doubling every second digit starting from the rightmost, so the result passes any standard IMEI checksum validator.

brand filters the TAC table before a device is picked. It matches the manufacturer name as a whole word first, so iPhone (an alias for Apple, as are galaxy for Samsung and pixel for Google) never matches SciPhone; a partial name such as sam still falls back to a substring match. Without it, any entry in the table can be chosen. If no manufacturer matches, the request returns a 400. The brand field in the response echoes the filter, or any when none was given.

The serial is random and is not checked against any registry, so a generated IMEI uses a real model's TAC but is not tied to a real handset. Use the output as test data only; do not use it to identify or register devices.

count sets how many IMEIs are generated, from 1 to 5, and is a paid-plan parameter; on the Free plan it is ignored and one IMEI is returned. Each entry in imeis carries imei, serial, checksum and isValid, which is always true because every number is built to pass the check. tac, manufacturer and model are null on the Free plan.

What people use it for

Testing & QA
Generate valid IMEI numbers for testing mobile device management systems and applications
Development
Create test data for mobile device registration and tracking systems during development
Data Generation
Generate realistic IMEI numbers for database seeding and mock data creation
Validation Testing
Test IMEI validation logic with properly formatted and checksummed IMEI numbers

Ways to call it

One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.

JSON
Default REST response
XML
Markup format
YAML
Human-readable
CSV
Tabular export
Beta
GraphQL
Query language
New
MCP
For AI agents

Other ways to use IMEI Generator

Same data, same APIVerve account, same credit balance — one key works on all of them.

Questions.

Common questions about the IMEI Generator API.

Read the docs →
Can I generate IMEIs for specific device brands?
Yes. You can pass a brand parameter such as Apple, Samsung, or Nokia to produce IMEIs that match genuine manufacturer identifiers. If you omit the brand, the API generates valid numbers across available manufacturers.
Is it cheap enough to generate fresh IMEIs for every automated test run?
Yes. Each request costs 1 credit, which works out to about $0.00015 per call or $0.15 per 1,000 calls on the Starter plan. That plan provides enough credits for 200,000 calls each month. You can also develop on the Free plan, which includes 200 calls per month.
Are the device model and TAC details included on the Free plan?
No. The Type Allocation Code, manufacturer name, and model identifier are premium fields reserved for paid subscriptions. The Free plan returns the full 15-digit IMEI, serial number, Luhn check digit, and validity confirmation. Custom generation quantities via the count parameter also require a paid plan.
Will these generated IMEIs pass frontend and database Luhn validation checks?
Yes. Every generated 15-digit IMEI ends with a valid Luhn checksum calculated across the preceding 14 digits. The response also provides an explicit validation status confirming the number passes standard verification, preventing test failures caused by invalid formats.
Can I generate batches of IMEIs in a single request?
Yes, if you are on a paid plan. Paid tiers unlock the count parameter, allowing you to generate multiple IMEI records in a single API call. Free plan users receive one generated IMEI per request.
How recent are the device models?
The TAC reference table is the Osmocom TAC database (CC BY-SA 3.0), which stopped updating in 2016. Brands and checksums are real, but the newest models are from about 2016 (for example iPhone 7), so use the output as structurally valid test data rather than a list of current handsets.

Ready to build with IMEI Generator? Start with 200 free credits — one key unlocks all 404+ APIs.

Explore the catalog

404+ APIs on the same key and the same response shape.

Browse all APIs