Overview
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.
Live Test IMEI Generator API →
Endpoint
One host, one path per API. The block below shows this call in four languages; every one of them is the same HTTP request. Making requests covers the timeouts, retries and parameter rules that apply to all of them. The SDKs wrap the same call in a typed client.
curl "https://api.apiverve.com/v1/imeigenerator?brand=Samsung&count=1" \
-H "x-api-key: your_api_key_here"const res = await fetch('https://api.apiverve.com/v1/imeigenerator?brand=Samsung&count=1', {
headers: { 'x-api-key': 'your_api_key_here' },
});
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const { data } = await res.json();
console.log(data);import requests
res = requests.get(
"https://api.apiverve.com/v1/imeigenerator?brand=Samsung&count=1",
headers={"x-api-key": "your_api_key_here"},
timeout=15,
)
res.raise_for_status()
print(res.json()["data"])package main
import (
"fmt"
"io"
"net/http"
)
func main() {
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/imeigenerator?brand=Samsung&count=1", nil)
req.Header.Set("x-api-key", "your_api_key_here")
res, err := http.DefaultClient.Do(req)
if err != nil {
panic(err)
}
defer res.Body.Close()
out, _ := io.ReadAll(res.Body)
fmt.Println(string(out))
}Replace your_api_key_here with the key from your dashboard. When the inputs arrive as a list rather than one at a time, batch requests run up to 200 of them through this same API in a single call.
Authentication
Send your key in the x-api-key header. That is the only auth step — there is no token exchange and no per-endpoint scope to configure. Authentication covers creating, rotating and revoking keys.
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
Parameters
Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them.
| Parameter | Type | Description |
|---|---|---|
brandOptional | string | Filter by manufacturer brand (e.g., Samsung, Apple, Nokia) |
countOptionalPremium | integer | Number of IMEIs to generate default 1 · range 1–5 |
Response
Every API returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape. Response format covers the envelope, the other output formats and how premium fields are withheld.
{
"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
}
]
}
}
Response fields
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
count | number | 2 | Number of IMEIs returned |
brand | string | "Samsung" | Manufacturer the reporting body identifier belongs to |
imeis | array[2] | Array of generated IMEI objects | |
imei | string | "358398048517203" | 15-digit IMEI number with valid Luhn checksum |
tacPremium | string | "35839804" | Type Allocation Code (first 8 digits) |
manufacturerPremium | string | "Samsung" | Device manufacturer name |
modelPremium | string | "Galaxy Xcover" | Device model identifier |
serial | string | "851720" | Serial portion of the IMEI, unique within the model |
checksum | string | "3" | Luhn check digit closing the IMEI |
isValid | boolean | true | Whether the generated IMEI passes the Luhn check |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change. Error handling covers the full status list and which of them are worth retrying.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted | A key restriction or IP allow-list; see key scoping. |
429 | Rate limited, or out of credits | Read error to tell them apart; see rate limits. |
Use cases
- 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
Other ways to use IMEI Generator
Set up IMEI Generator on APIVerve, or reach the same source a different way. Your APIVerve account and credits work on all of them — one key, one balance.
Related
More in Data Generation: