AI-generated Key Takeaways
- 
          This API endpoint allows searching for devices by hardware identifiers like IMEI using a POST request. 
- 
          The request URL follows gRPC Transcoding syntax and requires the partnerIdas a path parameter.
- 
          The request body must include pageToken,limit, anddeviceIdentifierto specify the search criteria and results page size.
- 
          The response body includes a list of devices, along withnextPageTokenfor pagination andtotalSizefor the total device count.
- 
          Authorization for this API requires the OAuth scope https://www.googleapis.com/auth/androidworkprovisioning.
Finds devices by hardware identifiers, such as IMEI.
HTTP request
POST https://androiddeviceprovisioning.googleapis.com/v1/partners/{partnerId}/devices:findByIdentifier
The URL uses gRPC Transcoding syntax.
Path parameters
| Parameters | |
|---|---|
| partnerId | 
 Required. The ID of the reseller partner. | 
Request body
The request body contains data with the following structure:
| JSON representation | |
|---|---|
| {
  "pageToken": string,
  "limit": string,
  "deviceIdentifier": {
    object ( | |
| Fields | |
|---|---|
| pageToken | 
 A token specifying which result page to return. | 
| limit | 
 Required. The maximum number of devices to show in a page of results. Must be between 1 and 100 inclusive. | 
| deviceIdentifier | 
 Required. Required. The device identifier to search for. | 
Response body
If successful, the response body contains data with the following structure:
Response containing found devices.
| JSON representation | |
|---|---|
| {
  "devices": [
    {
      object ( | |
| Fields | |
|---|---|
| devices[] | 
 Found devices. | 
| nextPageToken | 
 A token used to access the next page of results. Omitted if no further results are available. | 
| totalSize | 
 The total count of items in the list irrespective of pagination. | 
Authorization Scopes
Requires the following OAuth scope:
- https://www.googleapis.com/auth/androidworkprovisioning
For more information, see the OAuth 2.0 Overview.