Device data API for the GSM industry

IMEI API check, built for your stack.

Run an IMEI API check programmatically and get brand, model, code name, device type and supported bands in a single JSON response — no manual lookups on third-party sites, no scraping, no spreadsheets. Built for buyback platforms, used-electronics stores, wholesalers and ERP/POS integrators.

Start free trial View documentation

Try it live

Demo preview with sample data — sign up to run real checks.

One request. Complete device identity.

curl "https://api.imeiapi.net/v1/device/356656420854225" \
  -H "X-Api-Key: YOUR_API_KEY"

const res = await fetch(
  "https://api.imeiapi.net/v1/device/356656420854225",
  { headers: { "X-Api-Key": process.env.IMEIAPI_KEY } }
);
const device = await res.json();
console.log(device.brand, device.model); // Apple iPhone 11

$ch = curl_init("https://api.imeiapi.net/v1/device/356656420854225");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["X-Api-Key: " . $apiKey]);
$device = json_decode(curl_exec($ch), true);
curl_close($ch);
echo $device["brand"] . " " . $device["model"];

Infrastructure you can build on

Raw numbers, not slogans. This is what the platform does day in, day out.

190,000+
TAC records in database: 12,400,000+
IMEIs checked in total: 180ms
Median API response time: 99.9%
Uptime, last 90 days

What the API returns

One endpoint, five fields — the complete hardware identity of a device, resolved from its IMEI. No noise, no upsell fields, no surprises in the schema.

GET /v1/device/356656420854225

{
  "imei": "356656420854225",
  "brand": "Apple",
  "model": "iPhone 11",
  "code_name": "A2221",
  "device_type": "smartphone",
  "bands": "GSM / HSPA / LTE"
}

More check types are on the roadmap — the response schema above is stable and won't change under you.

brand string: Device manufacturer, e.g. "Samsung" or "Apple".
model string: Commercial model name, e.g. "Galaxy S24 Ultra".
code_name string: Internal model code used by the manufacturer, e.g. "SM-S928B".
device_type string: Hardware category: smartphone, tablet, modem, wearable and similar.
bands string: Radio bands and network technologies supported by the device.

From zero to first check in minutes

No sales calls, no onboarding meetings. The integration path is three steps long.

01
Create an account
Sign up and start a 7-day trial with up to 100 checks per day — enough to build and test a full integration before you commit to a plan.
02
Grab your API key
Your key is issued instantly. Send it as an X-Api-Key header or a token query parameter — whichever fits your stack better.
03
Send your first request
One GET request with an IMEI returns the full device identity as JSON. Median response time is well under a second.

Sandbox environment

Test every response shape before you write a single line of production code.

The sandbox accepts reserved test IMEIs that deterministically return each response type — including the errors you'll want your integration to handle gracefully. Same schema, same status codes, no quota usage.

A valid IMEI returning a complete device record.

Request

curl "https://api.imeiapi.net/v1/device/356656420854225" \
  -H "X-Api-Key: SANDBOX_KEY"

Response200 OK

{
  "imei": "356656420854225",
  "brand": "Apple",
  "model": "iPhone 11",
  "code_name": "A2221",
  "device_type": "smartphone",
  "bands": "GSM / HSPA / LTE"
}

Sandbox responses are static fixtures — identical structure to production, zero cost.

Pricing that scales with your volume

Flat monthly packages. The more you check, the less each check costs. No per-seat fees, no setup fees.

7-day free trial100/day

Every account starts with a 7-day trial: up to 100 checks per day, full API access, sandbox included. Pick a plan whenever you're ready.

Start free trial

MonthlyAnnualsave ~17%

Starter

$9/mo

2,000 checks / month

~$4.50 per 1,000 checks

Growth

Business

$89/mo

50,000 checks / month

~$1.78 per 1,000 checks

Scale

$249/mo

200,000 checks / month

~$1.25 per 1,000 checks

Enterprise

Custom quote

Custom volume

Checkout opens soon — plans can be activated after the trial.

Documentation developers actually read

A complete OpenAPI specification rendered as interactive reference docs — every endpoint, every parameter, every error code, with copy-paste examples in curl, JavaScript and PHP.

Authenticate via X-Api-Key header or token query parameter
Standard HTTP status codes — 401, 402, 422, 429 — documented with response bodies
OpenAPI 3.1 spec you can import straight into Postman or your codegen

Open API reference →

HTTP status codes

200	OK — device record returned
401	Invalid or missing API key
402	Subscription expired / no active plan
422	IMEI failed validation (Luhn)
429	Daily or monthly quota exceeded

Frequently asked questions

The technical details, up front.

What exactly does one check return?

Five fields resolved from the IMEI: brand, model, code name, device type and supported bands. The response is a flat JSON object — see the API section above for a live example.

How do daily and monthly limits work?

During the trial you can run up to 100 checks per day. Paid plans have a monthly quota (e.g. 10,000 checks on Growth). Requests beyond the quota return HTTP 429 with a Retry-After header — they are rejected, never silently billed.

What happens when I hit my plan limit?

The API starts returning 429 responses until your quota resets or you upgrade. Your integration keeps working the moment the new quota is active — no key changes needed.

Do invalid IMEIs count against my quota?

No. IMEIs that fail format or Luhn checksum validation are rejected with HTTP 422 before any lookup happens, and they don't consume quota.

How do I authenticate requests?

Two interchangeable methods: send your key in the X-Api-Key header (recommended) or as a token query parameter for quick tests and legacy systems. Both are documented in the API reference.

What about blacklist, iCloud or carrier checks?

Right now the API does one thing well: device identity from IMEI. More check types are being evaluated for the roadmap — when they ship, they'll be added as new endpoints without breaking the existing schema.

What support do you offer?

Email support for all plans, with priority handling for Business and above. Enterprise customers get a dedicated contact and custom SLA terms.

Stop checking IMEIs by hand.

Wire the check into your intake flow, your POS, your ERP — and let the API do the typing. The trial takes two minutes to start.

Start free trial Talk to us

support@imeiapi.net

Get in touch

Questions about volume pricing, integrations or the roadmap? Send a message — we respond within one business day.