1. Authentication
Every request needs an X-API-Key header (issued in the admin area under B2B API) or an Authorization: Bearer <token> header from a member account with an active paid plan. Requests with neither, with a wrong/disabled key, or with an expired token are rejected with HTTP 401.
2. IMEI check
GET /api/v3/{carrier}/{imei} — returns the network restriction status of the IMEI on one Japanese carrier. {carrier} is one of the codes in the table below; {imei} is 15 digits with a valid Luhn check. To check several carriers, call each code in turn. Response: {"message": "<symbol>"}.
3. Samsung lookup
GET /api/v3/samsung/{imei} — returns Samsung device information (model, …) by IMEI.
4. Error codes
HTTP 401 {"message":"Thiếu hoặc sai API key / token"}: not authenticated. HTTP 403 (member token only): the account is blocked, disabled, not activated, email not verified, on the Free plan, or the plan has expired — the code field gives the reason (BLOCKED, DISABLED, INACTIVE, NOT_VERIFIED, NO_PLAN, EXPIRED). HTTP 400 {"message":"IMEI Error"}: the IMEI is not 15 digits or fails the Luhn check. HTTP 500 {"message":"error"}: no result could be fetched from the carrier site — retry after a few minutes. During maintenance the message may contain a maintenance notice.
5. Limits
There is no per-key request limit. Each request queries the carrier site directly and may take a few seconds — set a timeout of at least 60 seconds and avoid bursts of simultaneous calls. Every request is logged with its IP.