Restez organisé à l'aide des collections
Enregistrez et classez les contenus selon vos préférences.
Requête asynchrone permettant de revendiquer jusqu'à 100 000 appareils pour un ou plusieurs clients.
Les méthodes d'API asynchrones renvoient un résultat avant la fin du traitement. Elles aident également votre application (ou votre outil) à rester réactive pour vos utilisateurs pendant qu'ils attendent la fin d'une opération de longue durée. Votre application doit appeler getOperation pour vérifier régulièrement l'état de l'opération.
Référence de l'entreprise du client auquel l'appareil est attribué.
orderNumber
string
Non
Numéro de la commande
vendorParams
map
Non
Champs supplémentaires, paire clé-valeur spécifiée par le fournisseur.
ClaimDeviceResponse
Nom de propriété
Valeur
Description
operations
Liste d'objets Operation
Une ou plusieurs instances OperationClaimDevices.
Comportement en cas d'erreur
Si une erreur se produit, l'objet Operation renvoie l'un des codes d'erreur suivants:
Code d'erreur
DEVICE_UPLOAD_COUNT_EXCEEDED
DUPLICATE_DEVICES
INTERNAL_SERVER_ERROR
INVALID_CUSTOMER_ID
INVALID_DEVICE_IMEI
INVALID_DEVICE_MEID
INVALID_DEVICE_SERIAL
INVALID_IDENTIFIER_SET
INVALID_MANUFACTURER
INVALID_MODEL
Sauf indication contraire, le contenu de cette page est régi par une licence Creative Commons Attribution 4.0, et les échantillons de code sont régis par une licence Apache 2.0. Pour en savoir plus, consultez les Règles du site Google Developers. Java est une marque déposée d'Oracle et/ou de ses sociétés affiliées.
Dernière mise à jour le 2025/08/29 (UTC).
[null,null,["Dernière mise à jour le 2025/08/29 (UTC)."],[[["\u003cp\u003eThis asynchronous API allows you to claim up to 100,000 devices for one or more customers.\u003c/p\u003e\n"],["\u003cp\u003eEach request using the \u003ccode\u003eResellerService\u003c/code\u003e class supports claiming devices for only one customer; attempting to claim for multiple customers will result in an \u003ccode\u003eINTERNAL_SERVER_ERROR\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eThe asynchronous method \u003ccode\u003eclaimDevicesAsync\u003c/code\u003e returns a result before processing is complete, and you must use \u003ccode\u003egetOperation\u003c/code\u003e to periodically check the status.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eClaimDevicesRequest\u003c/code\u003e requires a list of \u003ccode\u003eDeviceClaim\u003c/code\u003e objects, and each \u003ccode\u003eDeviceClaim\u003c/code\u003e must include a \u003ccode\u003eDeviceIdentifier\u003c/code\u003e and \u003ccode\u003eCompanyReference\u003c/code\u003e for the customer.\u003c/p\u003e\n"],["\u003cp\u003ePotential error codes include \u003ccode\u003eDEVICE_UPLOAD_COUNT_EXCEEDED\u003c/code\u003e, \u003ccode\u003eDUPLICATE_DEVICES\u003c/code\u003e, \u003ccode\u003eINTERNAL_SERVER_ERROR\u003c/code\u003e, and various \u003ccode\u003eINVALID\u003c/code\u003e errors related to customer, device identifiers, and device information.\u003c/p\u003e\n"]]],["The `claimDevicesAsync` method initiates an asynchronous request to claim up to 100,000 devices. Each request, using `ClaimDevicesRequest`, must specify a list of `DeviceClaim` objects, each detailing device identifiers and a customer. The `ResellerService` only supports one customer per request. The method returns `ClaimDevicesResponse` with `Operation` objects for tracking status. Errors, like `DEVICE_UPLOAD_COUNT_EXCEEDED` or `INTERNAL_SERVER_ERROR`, are reported within the `Operation` object.\n"],null,["# claimDevicesAsync\n\nAsynchronous request to claim up to 100,000 devices for one or more customers.\n| **Note:** The `ResellerService` class created by `SamsungResellerServiceFactory` only supports claiming devices for one customer per request. If devices for multiple customers are put into a single request, the operation will fail and return `INTERNAL_SERVER_ERROR`.\n\nAsynchronous API methods return a result before the processing is complete. They\nalso help your app (or tool) remain responsive for your users while they wait\nfor a long-running operation to complete. Your app should call\n[`getOperation`](/zero-touch/reseller-library/reference/methods/getoperation)\nto check the status of the operation periodically.\n\nMethod signature\n----------------\n\n public ClaimDevicesResponse claimDevicesAsync(ClaimDevicesRequest request);\n\nClaimDeviceRequest\n------------------\n\n| Property name | Value | Required | Description |\n|---------------|-------------------------------|----------|--------------------------------------------------|\n| `claims` | List of `object(DeviceClaim)` | Yes | List of device claims to claim for the customer. |\n\nDeviceClaim\n-----------\n\n| Property name | Value | Required | Description |\n|--------------------|-----------------------------------------------------|----------|--------------------------------------------------------------------|\n| `deviceIdentifier` | `object(`[`DeviceIdentifier`](#deviceidentifier)`)` | Yes | Device identifier. |\n| `customer` | `CompanyReference` object | Yes | Company reference for the customer that the device is assigned to. |\n| `orderNumber` | `string` | No | Order number. |\n| `vendorParams` | `map` | No | Extra fields, vendor specified key-value pair. |\n\nClaimDeviceResponse\n-------------------\n\n| Property name | Value | Description |\n|---------------|-----------------------------|---------------------------------------------------|\n| `operations` | List of `Operation` objects | One or more `ClaimDevices` `Operation` instances. |\n\nError behavior\n--------------\n\nIf an error occurs, the `Operation` object returns one of the following error\ncodes:\n\n| Error code |\n|--------------------------------|\n| `DEVICE_UPLOAD_COUNT_EXCEEDED` |\n| `DUPLICATE_DEVICES` |\n| `INTERNAL_SERVER_ERROR` |\n| `INVALID_CUSTOMER_ID` |\n| `INVALID_DEVICE_IMEI` |\n| `INVALID_DEVICE_MEID` |\n| `INVALID_DEVICE_SERIAL` |\n| `INVALID_IDENTIFIER_SET` |\n| `INVALID_MANUFACTURER` |\n| `INVALID_MODEL` |"]]
