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

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

Returns complete IMEI details including TAC, manufacturer, model, serial number, and checksum with validation status, perfect for testing and development purposes.

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
GraphQL: Query language
MCP: For AI agents

View all integrations →

Other ways to use IMEI Generator

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

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.on VerveKit

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 2 credits, which works out to $0.0003 per call or $0.30 per 1,000 calls on the Starter plan. That plan provides enough credits for 100,000 calls each month. You can also develop on the Free plan, which includes 100 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.

Request parameters — GET /v1/imeigenerator

Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.

Optional

Parameter	Type	Example	Description
`brand`Optional	string	`Samsung`	Filter by manufacturer brand (e.g., Samsung, Apple, Nokia)
`count`OptionalPremium	integer	`1`	Number of IMEIs to generate default 1 · range 1-5

Example request

1
2

curl "https://api.apiverve.com/v1/imeigenerator?brand=Samsung&count=2" \
  -H "x-api-key: YOUR_API_KEY"

Authentication

Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.

Header	When	Value
`x-api-key`Required	Every request	Your API key. Header names are case-insensitive, so `X-API-Key` is the same header.
`Authorization`Alternate	Instead of the above	`Bearer <key>` — for clients that only expose bearer auth. Resolves to the same account and the same billing.

401 is the only auth verdict

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.

Response — GET /v1/imeigenerator

Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.

Sample response

{
  "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
`tac`Premium	string	`"35839804"`	Type Allocation Code (first 8 digits)
`manufacturer`Premium	string	`"Samsung"`	Device manufacturer name
`model`Premium	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

Response headers

Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.

Header	What it carries
`x-api-remaining-credits`	Credits left in the current cycle
`x-api-credits-used`	Credits spent in the current cycle
`x-api-max-credits`	The allowance for the cycle
`x-api-version`	Version of the endpoint that answered

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.

Status	Meaning	What to do
`400`	Input was rejected	Read `error`; it names the parameter that has to change.
`401`	Key missing or invalid	Check the header name and the key value.
`403`	Key valid, but not permitted here	A key restriction or an IP allow-list — never a bad key.
`429`	Rate limited, or out of credits	Read `error` to tell them apart, then back off or top up.

What a call costs — 2 credits per call

Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.

Plan	Per month	Credits	IMEI Generator calls	Per 1,000 calls
Free	Free	200	100	Free
Starter	$29.99	200,000	100,000	$0.30
Pro	$99.99	1,000,000	500,000	$0.20
Mega	$299.99	4,000,000	2,000,000	$0.15

Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.

Compare all pricing tiers →

Call it from cURL — GET /v1/imeigenerator

No SDK to install — this is a plain HTTPS call to /v1/imeigenerator with your key in the x-api-key header. Swap in a real key and it runs as-is.

cURL

1
2

curl "https://api.apiverve.com/v1/imeigenerator" \
  -H "x-api-key: YOUR_API_KEY"

Resources

GitHubapiverve/imeigenerator-apiSource, issues and the examples this page is built from.ReferenceIMEI Generator API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/imeigeneratornpm apiverve-imeigeneratorPyPI APIVerve.API.IMEIGeneratorNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Node.js — GET /v1/imeigenerator

Install the Node.js SDK, then call the IMEI Generator API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — npm

npm install @apiverve/imeigenerator

Node.js

const res = await fetch("https://api.apiverve.com/v1/imeigenerator", {
  headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);

Resources

npm@apiverve/imeigeneratorThe published Node.js client, versioned and signed.GitHubapiverve/imeigenerator-apiSource, issues and the examples this page is built from.ReferenceIMEI Generator API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

apiverve-imeigeneratorPyPI APIVerve.API.IMEIGeneratorNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Python — GET /v1/imeigenerator

Install the Python SDK, then call the IMEI Generator API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — PyPI

pip install apiverve-imeigenerator

Python

import requests

res = requests.get(
    "https://api.apiverve.com/v1/imeigenerator",
    headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])

Resources

PyPIapiverve-imeigeneratorThe published Python client, versioned and signed.GitHubapiverve/imeigenerator-apiSource, issues and the examples this page is built from.ReferenceIMEI Generator API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/imeigeneratornpm APIVerve.API.IMEIGeneratorNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from C# / .NET — GET /v1/imeigenerator

Install the C# / .NET SDK, then call the IMEI Generator API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — NuGet

dotnet add package APIVerve.API.IMEIGenerator

C# / .NET

using var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");

var json = await client.GetStringAsync("https://api.apiverve.com/v1/imeigenerator");
Console.WriteLine(json);

Resources

NuGetAPIVerve.API.IMEIGeneratorThe published C# / .NET client, versioned and signed.GitHubapiverve/imeigenerator-apiSource, issues and the examples this page is built from.ReferenceIMEI Generator API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/imeigeneratornpm apiverve-imeigeneratorPyPI

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Go — GET /v1/imeigenerator

No SDK to install — this is a plain HTTPS call to /v1/imeigenerator with your key in the x-api-key header. Swap in a real key and it runs as-is.

req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/imeigenerator", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")

res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))

Resources

Also published for

@apiverve/imeigeneratornpm apiverve-imeigeneratorPyPI APIVerve.API.IMEIGeneratorNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from PHP — GET /v1/imeigenerator

No SDK to install — this is a plain HTTPS call to /v1/imeigenerator with your key in the x-api-key header. Swap in a real key and it runs as-is.

PHP

$ch = curl_init("https://api.apiverve.com/v1/imeigenerator");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);

$response = curl_exec($ch);
echo $response;

Resources

Also published for

@apiverve/imeigeneratornpm apiverve-imeigeneratorPyPI APIVerve.API.IMEIGeneratorNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Ruby — GET /v1/imeigenerator

No SDK to install — this is a plain HTTPS call to /v1/imeigenerator with your key in the x-api-key header. Swap in a real key and it runs as-is.

Ruby

require "net/http"

uri = URI("https://api.apiverve.com/v1/imeigenerator")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"

res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.body

Resources

Also published for

@apiverve/imeigeneratornpm apiverve-imeigeneratorPyPI APIVerve.API.IMEIGeneratorNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Data Generation

View all 32 →

All articles →

Generate Barcodes for Inventory and ShippingCreate Code 128 and Code 39 barcodes programmatically. Tutorial for inventory systems, shipping labels, and asset tracking.Read

Add Secure Password Generation to Your AppGenerate cryptographically secure passwords via API. Tutorial with code examples for signup flows, admin panels, and password managers.Read

QR Codes Are Back (And This Time It's Different)Remember when QR codes were a punchline? Now they're everywhere. Here's why this time it stuck.Read

IMEI Generator API

Try it — live request, no key required

About the IMEI Generator API

What people use it for

Ways to call it

Other ways to use IMEI Generator

Questions.

Request parameters — GET /v1/imeigenerator

Optional

Authentication

Response — GET /v1/imeigenerator

Response fields

Response headers

Errors

What a call costs — 2 credits per call

Call it from cURL — GET /v1/imeigenerator

Resources

Also published for

Call it from Node.js — GET /v1/imeigenerator

Resources

Also published for

Call it from Python — GET /v1/imeigenerator

Resources

Also published for

Call it from C# / .NET — GET /v1/imeigenerator

Resources

Also published for

Call it from Go — GET /v1/imeigenerator

Resources

Also published for

Call it from PHP — GET /v1/imeigenerator

Resources

Also published for

Call it from Ruby — GET /v1/imeigenerator

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — IMEI Generator API

Data Generation

Related articles

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

Explore the catalog