Phone marketplaces
Compare available TAC identity with seller-entered brand and model data.
TAC database API demo
See exactly how the TAC database API request works
This maintained technical resource shows the required headers, live request tester, rate limits, and example JSON responses for TAC-based phone identification. It is not a blacklist, carrier-lock, or account-status API.
B2B use cases
Built for device workflows, not consumer-status claims
Developers can use available TAC identity data to normalize inventory, compare marketplace listings, route repair intake, and begin trade-in assessment. Blacklist, carrier lock, Find My, finance, warranty, and history remain separate products and data sources.
Inventory systems
Normalize device-family fields during warehouse or reseller intake.
Repair-shop software
Pre-fill available model identity before diagnostics and parts selection.
Trade-in and recycling
Route a phone into the correct downstream assessment workflow.
API key required
Use the X-API-Key header with the key emailed after approval.
TAC lookup only
The public API exposes TAC model lookup and health only. Nothing else.
Free for approved users
Access is free of cost after review and approval.
TAC lookup guide
Built for TAC database lookup
The TAC database API is TAC-only and approval based. Approved users can send either an 8-digit TAC or a full 14/15-digit IMEI, and the service derives the TAC automatically before returning brand and model data.
Free of cost for approved users
3 checks per hour by default
One key, one scope: TAC lookup only
Revocable and suspendable by admin
Live API Tester
Send a TAC lookup request
Solve the captcha to mint a 5-use temporary key, then send TAC or IMEI lookups from the demo.
Temporary demo key
Valid for 5 TAC/IMEI checks, expires after 30 minutes, and is tied to this demo session.
Enter an 8-digit TAC or a 14/15-digit IMEI. The demo will derive the TAC automatically.
The key goes in the X-API-Key header.
Request preview
POST /api/tac-demo/lookup
Content-Type: application/json
X-API-Key: tac_live_xxxxxxxxxxxxxxxxxxxx
{
"imeiOrTac": "35693803"
}cURL
What to send
The TAC lookup endpoint is a simple authenticated POST request through the demo gate.
Method
POST
Endpoint
/api/tac-demo/lookup
Header
X-API-Key: your key
Body
JSON with one field: imeiOrTac
Accepted input
8-digit TAC or 14/15-digit IMEI, for example 35693803 or 356938031234567
Live response
The panel below shows the real API result, headers, and any error message.
Waiting for requestNo response yet
Response JSON
{
"success": true,
"status": "success",
"result": "Brand: Apple<br>Model: iPhone 14 Pro<br>Model Name: iPhone15,2<br>",
"count_free_checks_today": 209000,
"readPerformance": "0.0001 seconds",
"object": {
"brand": "Apple",
"name": "iPhone15,2",
"model": "iPhone 14 Pro"
}
}Response headers
content-type: application/json
Request format
What users need to send
Method: GET
Endpoint: /api/tac/:tac
Headers: X-API-Key and Accept: application/json
TAC: 8 digits, for example 35693803
IMEI input: Full IMEI values are also accepted and the TAC is derived automatically.
Rate limits: Approved free keys are limited to 3 checks per hour. Higher limits and custom plans are available on request.
{
"method": "GET",
"url": "/api/tac/35693803",
"headers": {
"X-API-Key": "tac_live_xxxxxxxxxxxxxxxxxxxx",
"Accept": "application/json"
}
}Response examples
What the API returns
Successful lookups return the device object, the rendered result string, and usage metadata. Not-found lookups return the same friendly fallback message used elsewhere on the site.
Success
{
"success": true,
"status": "success",
"result": "Brand: Apple<br>Model: iPhone 14 Pro<br>Model Name: iPhone14,2<br>",
"count_free_checks_today": 209000,
"readPerformance": "0.0001 seconds",
"object": {
"brand": "Apple",
"name": "iPhone14,2",
"model": "iPhone 14 Pro"
}
}Not found
{
"success": false,
"error": {
"code": "TAC_NOT_FOUND",
"message": "Unable to check device at the moment. Please try your free check again in 24–48 hours—our device database is updated regularly."
}
}Developer FAQ
Frequently Asked Questions About the TAC API
Common questions about rate limits, data accuracy, supported formats, and enterprise integration.
What is the TAC Database API?
The TAC Database API is a REST endpoint that allows approved developers and businesses to convert an 8-digit Type Allocation Code (TAC) or a full 14/15-digit IMEI into official device brand, model name, and hardware marketing name.
How fast is the TAC API response time?
The TAC Database API utilizes in-memory indexed lookup tables delivering ultra-fast sub-millisecond responses (typically 0.0001 seconds), designed for high-throughput automated workflows.
Can I send a full 15-digit IMEI instead of just the 8-digit TAC?
Yes. The API automatically parses full 14 or 15-digit IMEIs, strips formatting, extracts the first 8 digits (the TAC segment), and performs the model lookup without requiring manual string manipulation on your side.
Does the TAC API check carrier lock or blacklist status?
No. The TAC API is exclusively an identity and hardware specification endpoint. Live carrier locks, GSMA blacklist records, and iCloud/FRP activation locks require separate real-time carrier registry checks.
Is TAC API access free?
Approved users receive free tier access with 3 checks per hour. For high-volume batches, ERP inventory software, or custom limits, contact our enterprise support team.
Postman available
Prefer importing the collection?
You can also download the Postman collection from the GitHub TAC database repo and start testing immediately.
This gives you a clear request format, a predictable response shape, and a simple path from approval to testing.