Organiza tus páginas con colecciones
Guarda y categoriza el contenido según tus preferencias.
Un DeviceIdentifier encapsula los IDs de hardware para identificar un dispositivo fabricado. En este documento, se explica cómo trabajar con identificadores en la API de inscripción sin contacto.
Un DeviceIdentifier combina los metadatos o los IDs de hardware necesarios para identificar un dispositivo de forma única.
Tu organización incluye los valores del identificador de dispositivo cuando sube datos del dispositivo a través del portal o llama a la API.
Campos obligatorios
Dispositivos Android
Por lo general, la inscripción sin intervención identifica los dispositivos por los IDs de los módems celulares IMEI (o MEID). Para admitir dispositivos sin módems celulares, como las tablets, también puedes identificar dispositivos con un conjunto diferente de campos. En la siguiente tabla, se muestran los campos que puedes usar para cada tipo de dispositivo:
Identificador
Móvil
Solo Wi-Fi
Notas
hardware_id
Este campo debe ser un número de IMEI o MEID. La inscripción sin intervención valida el formato de los valores de IMEI cuando los pasas en argumentos de API.
hardware_id2
Este campo debe ser un segundo número de IMEI o MEID. La inscripción sin intervención valida el formato de los valores de IMEI cuando los pasas en argumentos de API. Para obtener información sobre los dispositivos con más de un módem celular, consulta Dispositivos con doble SIM.
serialNumber
El número de serie del fabricante del dispositivo El número de serie distingue mayúsculas de minúsculas y es el mismo valor que se muestra en Build.getSerial().
model
El valor del modelo del dispositivo debe coincidir con el valor integrado del dispositivo que se muestra en Build.MODEL. Consulta la referencia de nombres de modelos para obtener una lista de los valores permitidos para cada fabricante.
manufacturer
El valor del campo manufacturer debe coincidir con el valor integrado del dispositivo que se muestra en Build.MANUFACTURER. Consulta la referencia de nombres de fabricantes para obtener más información.
Si registras el número de serie, también debes registrar el fabricante y el modelo para asegurarte de que la inscripción automática pueda detectar el dispositivo.
Dispositivos con doble SIM
Un dispositivo con doble SIM incluye dos módems discretos y tiene dos números IMEI. Si solo registras un IMEI, prefiere el número IMEI más bajo numéricamente, ya que la inscripción sin contacto funciona de manera más confiable con el IMEI más bajo. Para aumentar la confiabilidad, también puedes registrar el otro IMEI, el número de serie, el fabricante y el modelo.
Para mostrar el segundo IMEI en el portal de inscripción automática, haz lo siguiente:
Ve a la pestaña Devices.
En la esquina superior derecha, junto al botón Agregar dispositivo, haz clic en los tres puntos more_vert.
Selecciona Personalizar tabla.
Selecciona la casilla de verificación correspondiente a IMEI2.
Haz clic en Guardar.
Dispositivos ChromeOS
En el caso de los dispositivos ChromeOS, el conjunto de identificadores obligatorios es el mismo para los dispositivos solo con Wi-Fi y con red celular:
Identificador
Notas
serialNumber
El número de serie del fabricante del dispositivo
model
El valor del modelo del dispositivo debe coincidir con el valor integrado del dispositivo. Consulta la lista de valores de modelos de ChromeOS como referencia.
Usa un DeviceIdentifier cuando encuentres o reclames dispositivos. Debes incluir los campos obligatorios especificados para el tipo de dispositivo.
En el siguiente fragmento, se muestra un número IMEI que se usa para buscar un dispositivo específico llamando a partners.devices.findByIdentifier:
Java
// Create a DeviceIdentifier.DeviceIdentifierdeviceIdentifier=newDeviceIdentifier();deviceIdentifier.setImei("123456789012347");// Perform the search using the zero-touch enrollment API.FindDevicesByDeviceIdentifierRequestbody=newFindDevicesByDeviceIdentifierRequest();body.setLimit(1L);body.setDeviceIdentifier(deviceIdentifier);FindDevicesByDeviceIdentifierResponseresponse=service.partners().devices().findByIdentifier(PARTNER_ID,body).execute();
.NET
// Create a DeviceIdentifier.vardeviceIdentifier=newDeviceIdentifier{Imei="123456789012347"};// Perform the search using the zero-touch enrollment API.varbody=newFindDevicesByDeviceIdentifierRequest{Limit=1,DeviceIdentifier=deviceIdentifier};varresponse=service.Partners.Devices.FindByIdentifier(body,PartnerId).Execute();
Python
# Create a DeviceIdentifier.device_identifier={'imei':'123456789012347'}# Perform the search using the zero-touch enrollment API.response=service.partners().devices().findByIdentifier(partnerId=PARTNER_ID,body={'deviceIdentifier':device_identifier, \
'limit':1}).execute()
En el siguiente fragmento, se muestra cómo crear un identificador de dispositivo con un número de serie:
Java
// Create a device identifier to find a Wi-Fi-only device.DeviceIdentifierdeviceIdentifier=newDeviceIdentifier();deviceIdentifier.setManufacturer("Honeywell");deviceIdentifier.setModel("VM1A");deviceIdentifier.setSerialNumber("ABcd1235678");
.NET
// Create a device identifier to find a Wi-Fi-only device.vardeviceIdentifier=newDeviceIdentifier{Manufacturer="Honeywell",Model="VM1A",SerialNumber="ABcd1235678"};
Python
# Create a device identifier to find a Wi-Fi-only device.device_identifier={'manufacturer':'Honeywell', \
'model':'VM1A','serialNumber':'ABcd1235678'}
[[["Fácil de comprender","easyToUnderstand","thumb-up"],["Resolvió mi problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Falta la información que necesito","missingTheInformationINeed","thumb-down"],["Muy complicado o demasiados pasos","tooComplicatedTooManySteps","thumb-down"],["Desactualizado","outOfDate","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Problema con las muestras o los códigos","samplesCodeIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 2025-07-25 (UTC)"],[[["\u003cp\u003eA \u003ccode\u003eDeviceIdentifier\u003c/code\u003e is used to uniquely identify a hardware device and is distinct from \u003ccode\u003edeviceId\u003c/code\u003e, which refers to a record in the API.\u003c/p\u003e\n"],["\u003cp\u003eFor Android devices, identification commonly relies on IMEI or MEID numbers for cellular devices, while Wi-Fi-only devices can use serial number, model, and manufacturer.\u003c/p\u003e\n"],["\u003cp\u003eDual-SIM devices have two IMEI numbers, and while either can be used, it is recommended to register the lowest number and include other information for increased reliability.\u003c/p\u003e\n"],["\u003cp\u003eChromeOS devices require the manufacturer's serial number, device model, and the Attested Device ID for identification.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eDeviceIdentifier\u003c/code\u003e is used to find or claim devices, and the specific required fields vary depending on the device type.\u003c/p\u003e\n"]]],["`DeviceIdentifier` represents hardware for zero-touch enrollment, using hardware IDs like IMEI, serial number, model, and manufacturer. Organizations use these values when uploading device data. Android devices use IMEI/MEID for cellular models, or serial number, model, and manufacturer for Wi-Fi only. Dual-SIM devices have two IMEIs. ChromeOS devices require serial number, model, and `chromeOsAttestedDeviceId`. To find a device, a `DeviceIdentifier` object with required fields is used in the `partners.devices.findByIdentifier` API call.\n"],null,["# Identifiers\n\nA [`DeviceIdentifier`](/zero-touch/reference/reseller/rest/v1/partners.devices#DeviceIdentifier) encapsulates hardware IDs to identify a\nmanufactured device. This document explains how to work with identifiers in the\nzero-touch enrollment API.\n\nA `DeviceIdentifier` combines hardware metadata or IDs required to uniquely\nidentify a device.\n\nYour organization includes the device identifier values when uploading device\ndata through the portal or calling the API.\n| **Important:** a `DeviceIdentifier` represents a hardware device. It shouldn't be confused with `deviceId`, which represents a record in the API.\n\nRequired fields\n---------------\n\n### Android devices\n\nZero-touch enrollment typically identifies devices by the IMEI (or MEID)\ncellular modem IDs. To support devices without cellular modems, such as\ntablets, you can also identify devices using a different set of fields. The\nfollowing table shows the fields you can use for each type of device:\n\n| Identifier | Cellular | Wi‑Fi only | Notes |\n|----------------|----------|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| `hardware_id` | | | This field must be an IMEI or MEID number. Zero-touch enrollment validates the format of IMEI values when you pass them in API arguments. |\n| `hardware_id2` | | | This field must be a second IMEI or MEID number. Zero-touch enrollment validates the format of IMEI values when you pass them in API arguments. For information on devices with more than one cellular modem, see [Dual-SIM devices](#dual-sim). |\n| `serialNumber` | | | The manufacturer's serial number for the device. The serial number is case sensitive and is the same value that's returned from [`Build.getSerial()`](https://developer.android.com/reference/android/os/Build.html#getSerial()). |\n| `model` | | | The device model value must match the device's built-in value returned from [`Build.MODEL`](https://developer.android.com/reference/android/os/Build.html#MODEL). See the [model names](/zero-touch/resources/manufacturer-names#model-names) reference for a list of allowed values for each manufacturer. |\n| `manufacturer` | | | The `manufacturer` field value must match the device's built-in value returned from [`Build.MANUFACTURER`](https://developer.android.com/reference/android/os/Build.html#MANUFACTURER). See the [manufacturer names](/zero-touch/resources/manufacturer-names) reference for further information. |\n\nIf registering serial number you must also register manufacturer and model to\nensure zero-touch is able to detect the device.\n\n#### Dual-SIM devices\n\nA dual-SIM device includes two discrete modems and has two IMEI numbers. If\nregistering just one IMEI, prefer the numerically lowest IMEI number as\nzero-touch enrollment works more reliably with the lowest IMEI. To increase\nreliability you can additionally register the other IMEI, or the serial number,\nmanufacturer and model.\n\nTo display the second IMEI in the zero-touch portal:\n\n1. Go to the **Devices** tab.\n2. On the upper right corner, beside the **Add Device** button, click the three dots more_vert.\n3. Select **Customize table**.\n4. Select the checkbox for **IMEI2**.\n5. Click **Save**.\n\n### ChromeOS devices\n\nFor ChromeOS devices the set of required identifiers is the same for cellular\nand Wi-Fi only devices:\n\n| Identifier | Notes |\n|----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| `serialNumber` | The manufacturer's serial number for the device. |\n| `model` | The device model value must match the device's built-in value. See the [list of ChromeOS model values](/zero-touch/resources/chromeos-models) for reference. |\n| `chromeOsAttestedDeviceId` | The Attested Device ID. See the [list of compatible ChromeOS devices](https://support.google.com/chrome/a/answer/10130175?#identify_compatible&zippy=%2Cidentify-compatible-chrome-devices) for reference. |\n\nRefer to a device\n-----------------\n\nUse a `DeviceIdentifier` when finding or claiming devices. You need to include\nthe required fields specified for the type of device.\n\nThe following snippet shows an IMEI number used to search for a specific device\nby calling [`partners.devices.findByIdentifier`](/zero-touch/reference/reseller/rest/v1/partners.devices/findByIdentifier): \n\n### Java\n\n```java\n// Create a DeviceIdentifier.\nDeviceIdentifier deviceIdentifier = new DeviceIdentifier();\ndeviceIdentifier.setImei(\"123456789012347\");\n\n// Perform the search using the zero-touch enrollment API.\nFindDevicesByDeviceIdentifierRequest body = new FindDevicesByDeviceIdentifierRequest();\nbody.setLimit(1L);\nbody.setDeviceIdentifier(deviceIdentifier);\n\nFindDevicesByDeviceIdentifierResponse response = service\n .partners()\n .devices()\n .findByIdentifier(PARTNER_ID, body)\n .execute();\n```\n\n### .NET\n\n```c#\n// Create a DeviceIdentifier.\nvar deviceIdentifier = new DeviceIdentifier\n{\n Imei = \"123456789012347\"\n};\n\n// Perform the search using the zero-touch enrollment API.\nvar body = new FindDevicesByDeviceIdentifierRequest\n{\n Limit = 1,\n DeviceIdentifier = deviceIdentifier\n};\nvar response = service.Partners.Devices.FindByIdentifier(body, PartnerId).Execute();\n```\n\n### Python\n\n```python\n# Create a DeviceIdentifier.\ndevice_identifier = {'imei':'123456789012347'}\n\n# Perform the search using the zero-touch enrollment API.\nresponse = service.partners().devices().findByIdentifier(\n partnerId=PARTNER_ID, body={'deviceIdentifier':device_identifier, \\\n 'limit':1}).execute()\n```\n\nThe following snippet shows how to create a device identifier with a serial\nnumber: \n\n### Java\n\n```java\n// Create a device identifier to find a Wi-Fi-only device.\nDeviceIdentifier deviceIdentifier = new DeviceIdentifier();\ndeviceIdentifier.setManufacturer(\"Honeywell\");\ndeviceIdentifier.setModel(\"VM1A\");\ndeviceIdentifier.setSerialNumber(\"ABcd1235678\");\n```\n\n### .NET\n\n```c#\n// Create a device identifier to find a Wi-Fi-only device.\nvar deviceIdentifier = new DeviceIdentifier\n{\n Manufacturer = \"Honeywell\",\n Model = \"VM1A\",\n SerialNumber = \"ABcd1235678\"\n};\n```\n\n### Python\n\n```python\n# Create a device identifier to find a Wi-Fi-only device.\ndevice_identifier = {'manufacturer':'Honeywell', \\\n 'model':'VM1A', 'serialNumber':'ABcd1235678'}\n```\n\nLearn more\n----------\n\n- To learn more about hardware identifiers, see the [API reference documentation](/zero-touch/reference/reseller/rest/v1/partners.devices#DeviceIdentifier) for `DeviceIdentifier`.\n- To see a list of allowed manufacturer names and device models, review the [manufacturer names](/zero-touch/resources/manufacturer-names) reference.\n- To see a list of compatible ChromeOS devices, see the [ChromeOs Help Center](https://support.google.com/chrome/a/answer/10130175?#identify_compatible&zippy=%2Cidentify-compatible-chrome-devices)"]]