Stay organized with collections
Save and categorize content based on your preferences.
You can search for devices matching certain attributes with the
mobiledevices.list
method of the Directory API. This method accepts the query parameter which is
a search query combining one or more search clauses. Each search clause is made
up of three parts:
Field
Device attribute that is searched. For example, serial.
Operator
Test that is performed on the data to provide a match. For example, the :
operator tests if a text attribute matches a value.
Value
The content of the attribute that is tested. For example, serialNumber.
Multiple clauses are separated by whitespace and are implicitly joined by an
AND operator.
Examples
All queries use the mobiledevices.list
method, which has an HTTP request similar to the following (line breaks included for readability):
GET https://admin.googleapis.com/admin/directory/v1/customer/customerId/devices/mobile
?query=query parameters
The query parameters must be URL encoded. For example, the query
query=brand:goo* is URL encoded as query=brand%3goo*.
All examples on this page show unencoded query parameters.
Client libraries handle this URL encoding automatically.
Search for devices matching an serial number prefix
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-04 UTC."],[],[],null,["You can search for devices matching certain attributes with the\n[`mobiledevices.list`](/workspace/admin/directory/v1/reference/mobiledevices/list)\nmethod of the Directory API. This method accepts the `query` parameter which is\na search query combining one or more search clauses. Each search clause is made\nup of three parts:\n\nField\n: Device attribute that is searched. For example, `serial`.\n\nOperator\n: Test that is performed on the data to provide a match. For example, the `:`\n operator tests if a text attribute *matches* a value.\n\nValue\n: The content of the attribute that is tested. For example, `serialNumber`.\n\nMultiple clauses are separated by whitespace and are implicitly joined by an\n`AND` operator.\n| **Note:** Most device data updates within 1 hour, however, it may take up to 36 hours for new data to be reflected in all search results.\n\nExamples\n\nAll queries use the [`mobiledevices.list`](/workspace/admin/directory/v1/reference/mobiledevices/list)\nmethod, which has an HTTP request similar to the following (line breaks included for readability): \n\n```\nGET https://admin.googleapis.com/admin/directory/v1/customer/customerId/devices/mobile\n?query=query parameters\n```\n\nThe `query` parameters must be URL encoded. For example, the query\n`query=brand:goo*` is URL encoded as `query=brand%3goo*`.\nAll examples on this page show unencoded `query` parameters.\nClient libraries handle this URL encoding automatically.\n\nSearch for devices matching an serial number prefix \n\n serial:525*\n\nSearch for devices with email starting with fred \n\n email:fred* email:contact*\n\n| **Note:** For a complete list of mobile device fields, refer to [Personal device search fields](/workspace/admin/directory/v1/search-operators)."]]
