Device Information Parser API is an advanced tool designed to analyze user agent strings extracted from HTTP headers. These strings contain key information about the client device or application making the request, including details such as operating system, browser, device type and, in some cases, additional metadata.
This API converts these raw strings into structured and useful data, allowing you to better understand the technical characteristics of your users' devices or software. Access to this information facilitates user experience personalization, device-specific optimization, segmented content delivery and more accurate analytics.
{
"ua": "Mozilla/5.0 (Linux; Android 12; Pixel 6 Build/SD1A.210817.023; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/94.0.4606.71 Mobile Safari/537.36",
"browser": {
"name": "Chrome WebView",
"version": "94.0.4606.71",
"major": "94"
},
"engine": {
"name": "Blink",
"version": "94.0.4606.71"
},
"os": {
"name": "Android",
"version": "12"
},
"device": {
"vendor": "Google",
"model": "Pixel 6",
"type": "mobile"
},
"cpu": {}
}
curl --location --request POST 'https://zylalabs.com/api/6530/device+information+parser+api/9462/parser' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{
"user-agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/94.0.4606.81 Safari/537.36"
}'
| Header | Description |
|---|---|
Authorization
|
[Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed. |
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
To use this API, users must indicate the information of the user agent to structure in a JSON the information.
There are different plans to suit everyone, including a free trial for a small number of requests, but its rate is limited to avoid abuse of the service.
Zyla provides a wide range of integration methods for almost all programming languages. You can use these codes to integrate with your project as you need.
The API helps you tailor your web content and user experiences based on the specific devices used by visitors. This ensures optimal display and functionality across different devices, such as desktops, smartphones, and tablets.
Device Information Parser API designed to parse and interpret user agent strings sent by web browsers.
The Parser endpoint returns structured data about the user agent, including details about the browser, operating system, device type, and additional metadata. The response is formatted as JSON.
Key fields in the response include "ua" (user agent string), "browser" (name, version), "os" (name, version), "device" (vendor, model, type), and "engine" (name, version). Each field provides specific insights into the user's environment.
The response data is organized in a hierarchical JSON format. Each major category (browser, os, device, engine) contains relevant subfields, making it easy to access specific information about the user agent.
The Parser endpoint provides information about the browser name and version, operating system details, device vendor and model, and rendering engine specifics. This data helps in understanding user environments.
Users can customize their requests by specifying different user agent strings in the POST request. This allows for tailored responses based on the specific user agent being analyzed.
The data is sourced from a comprehensive database of known user agents, maintained through continuous updates and community contributions. This ensures a wide coverage of devices and browsers.
Data accuracy is maintained through regular updates to the user agent database, validation against known standards, and algorithms that parse user agent strings effectively. This helps ensure reliable identification.
Typical use cases include optimizing web content for specific devices, enhancing user experience through personalization, conducting analytics on user demographics, and improving security by identifying potential threats based on user agents.
To obtain your API key, you first need to sign in to your account and subscribe to the API you want to use. Once subscribed, go to your Profile, open the Subscription section, and select the specific API. Your API key will be available there and can be used to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
If you don’t cancel before the 7th day, your free trial will end automatically and your subscription will switch to a paid plan under the same plan you originally subscribed to, meaning you will be charged and gain access to the API calls included in that plan.
The free trial ends when you reach 50 API requests or after 7 days, whichever comes first.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost, so you can test our APIs without any commitment.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
Service Level:
100%
Response Time:
259ms
Service Level:
100%
Response Time:
123ms
Service Level:
100%
Response Time:
423ms
Service Level:
100%
Response Time:
238ms
Service Level:
100%
Response Time:
179ms
Service Level:
100%
Response Time:
233ms
Service Level:
100%
Response Time:
114ms
Service Level:
100%
Response Time:
78ms
Service Level:
100%
Response Time:
85ms
Service Level:
100%
Response Time:
151ms
Service Level:
100%
Response Time:
1,241ms
Service Level:
100%
Response Time:
134ms
Service Level:
100%
Response Time:
219ms
Service Level:
100%
Response Time:
1,115ms
Service Level:
100%
Response Time:
729ms
Service Level:
100%
Response Time:
1,586ms
Service Level:
100%
Response Time:
1,171ms
Service Level:
100%
Response Time:
863ms
Service Level:
100%
Response Time:
396ms
Service Level:
100%
Response Time:
8,082ms