For the Enterprise solution, device data is packaged in a JSON format, which is highly compressed to reduce server footprint, and optimized for speed of search and retrieval. It can either be downloaded manually or fetched with an automated script.
In the Cloud service, data is delivered on demand for the specific device headers submitted via the Client API. See the Getting Started guide for Cloud.
The device data is updated daily, and we recommend that you update the data file on a regular basis to ensure you have the most up-to-date device data.
Data file types
The device data file comes in three forms:
Content of data file
You can manage the content of the data file to optimise performance.
By default, the evaluation data file contains a limited property set, but these can be extended via Data File Options (My Account / Data File Options). Please note that adding properties will increase the footprint and will affect performance. Any changes made will take effect in the next data file download.
It is strongly recommended to setup a regular automated data download. The data file can be downloaded from this simple download page by passing the correct parameters in the URL. Either HTTP or HTTPs can be used to fetch the device data.
The download request must use the following parameters:
ExamplesDownload the latest data file in zip format:
Download the MD5 checksum file for the latest data file:
Download a past data file:
Sample shell script
A sample shell script to download the latest data file and verify it with the MD5 file can be found here: deviceatlas_auto_download.sh
Verification of a downloaded data file is very important to ensure the whole file was received and it is not corrupted. Setting the MD5 parameter to "1" will download a text file containing the MD5 hash of the main data file which can then be compared against the full data file.
Downloading past files
Past data files can be requested by setting the date parameter. If a personal data file is requested for a particular date, it is required that you have already downloaded that file in the past. Community data files do not have this restriction.
Installing the data file
Once the data file is downloaded the DeviceAtlas API needs to be told to reload it. This is a simple process and can be done as follows, typically taking a fraction of a second. Device recognition is not affected during a data file reload.
Take a look at the documentation specific to your API for further details.