Thank you, we are in the progress developing an IoT platform, we read an IMEI from IoT devices such as. Router, GPS, CCTV, EDC, etc. We use IMEIDB (https://imeidb.xyz/api) to get the device info like spec, brand, model etc, I was thinking about it would be great if we can show the image.
for example:
IMEI: 86334304021214 --> decode to get the check digit using LUHN and get decoded IMEI and we connect to imeidb.xyz/api to get the info, we received the name, model, etc (see below)
{"tac": 86334304, "name": "TP-LINK TL-MR6400", "type": "WLAN Router", "brand": "TP-LINK", "model": "TL-MR6400", "valid": true, "models": ["TL-MR6400"], "serial": 21214, "blacklist": {"status": false}, "device_id": null, "frequency": ["LTE FDD BAND 1", "LTE FDD BAND 3", "LTE FDD BAND 5", "LTE FDD BAND 7", "LTE FDD BAND 8", "LTE FDD BAND 20", "LTE FDD BAND 28", "LTE TDD BAND 38", "LTE TDD BAND 39", "LTE TDD BAND 40", "LTE TDD BAND 41", "WCDMA FDD Band 1", "WCDMA FDD Band 5", "WCDMA FDD Band 8"], "device_spec": {"os": null, "nfc": null, "usb": null, "wlan": null, "speed": null, "aliases": [], "nettech": null, "bluetooth": null, "os_family": "", "sim_slots": null}, "device_image": null, "manufacturer": "TP-Link Technologies Co Ltd", "controlNumber": 4}
as you see from the API returns, actually there is device_image property but looks like we can't depend on that! as you can see it's null!.. and looks like they can't guarantee to have the image of the device.
I expect to get the image from an API (free or paid) and get the image URL from them by passing the brand and model, in this example I would pass: TPLINK TL-MR6400.
Let me know what's your thoughts!
thank you