Follow these simple steps to have the DeviceAtlas Enterprise API working locally within a few minutes.
If you do not have a licence, please contact us to request an evaluation.
1. Download Device Data File
For the Enterprise solution, device data is packaged in a JSON format, which is highly compressed to reduce server footprint, and is optimized for speed of search and retrieval. It can either be downloaded manually or fetched with an automated script.
Refer to our Device Data (JSON) reference documentation to know more about DeviceAtlas data downloads.
2. Device Identification API
DeviceApi deviceApi = new DeviceApi(); deviceApi.loadDataFromFile("/path/to/apps_datafile.json");
String makeModel = "samsung SM-N9005".toLowerCase(); Properties properties = deviceApi.getProperties(makeModel);
3. Expected string format for DeviceAtlas lookup
DeviceAtlas expects the make/model string in a specific format.
This format consists of values separated by a space character, where the mandatory values are manufacturer and model. The string is the same for all platforms:
The term "Make" stands for manufacturer and the term "Model" stands for a model number.
It is important to pass the string to the DeviceAtlas API in the lowercase form when using lowercased data file. Modifications to the strings risk resulting in non-identification or mis-identification.
Platform Specific Code (Make/Model)
The following code snippets detail how to obtain the make/model for the most common mobile platforms. This or similar code needs be included in the mobile application gathering the data to be passed to the DeviceAtlas API.
String make = android.os.Build.MANUFACTURER; String model = android.os.Build.MODEL; String makeModel = make + " " + model;
samsung SM-N9005 HTC HTC One mini 2 Meizu m2 note OnePlus A0001 LGE Nexus 4
Note that the HTC example includes the "HTC" information twice. That is because some devices are configured by the vendors to include manufacturer information within the model (e.g. make = "HTC", model = "HTC One mini 2"). This is handled by the DeviceAtlas API, there is no need to manipulate the strings in advance.
4. Data File Options
5. Client-side Component
The Client-side Component is needed for granular identification of iOS devices, as well as for other dynamic properties. Please visit DeviceAtlas Client-side Component.