Overview
User Agent Parser works by analyzing the user agent string provided and extracting information about the browser, operating system, and device. It uses advanced algorithms to parse the user agent string and return the information in a structured format.
Endpoint
One host, one path per API. The block below shows this call in four languages; every one of them is the same HTTP request. Making requests covers the timeouts, retries and parameter rules that apply to all of them. The SDKs wrap the same call in a typed client.
curl -X POST https://api.apiverve.com/v1/useragentparser \
-H "x-api-key: your_api_key_here" \
-H "Content-Type: application/json" \
-d '{
"ua": "Mozilla/5.0 (Windows NT 6.4) AppleWebKit/537.36.0 (KHTML, like Gecko) Chrome/60.0.0.0 Safari/537.36.0"
}'const res = await fetch('https://api.apiverve.com/v1/useragentparser', {
method: 'POST',
headers: {
'x-api-key': 'your_api_key_here',
'Content-Type': 'application/json',
},
body: JSON.stringify({
"ua": "Mozilla/5.0 (Windows NT 6.4) AppleWebKit/537.36.0 (KHTML, like Gecko) Chrome/60.0.0.0 Safari/537.36.0"
}),
});
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const { data } = await res.json();
console.log(data);import requests
res = requests.post(
"https://api.apiverve.com/v1/useragentparser",
headers={"x-api-key": "your_api_key_here"},
json={
"ua": "Mozilla/5.0 (Windows NT 6.4) AppleWebKit/537.36.0 (KHTML, like Gecko) Chrome/60.0.0.0 Safari/537.36.0"
},
timeout=15,
)
res.raise_for_status()
print(res.json()["data"])package main
import (
"fmt"
"io"
"net/http"
"strings"
)
func main() {
body := strings.NewReader(`{
"ua": "Mozilla/5.0 (Windows NT 6.4) AppleWebKit/537.36.0 (KHTML, like Gecko) Chrome/60.0.0.0 Safari/537.36.0"
}`)
req, _ := http.NewRequest("POST", "https://api.apiverve.com/v1/useragentparser", body)
req.Header.Set("Content-Type", "application/json")
req.Header.Set("x-api-key", "your_api_key_here")
res, err := http.DefaultClient.Do(req)
if err != nil {
panic(err)
}
defer res.Body.Close()
out, _ := io.ReadAll(res.Body)
fmt.Println(string(out))
}Replace your_api_key_here with the key from your dashboard. When the inputs arrive as a list rather than one at a time, batch requests run up to 200 of them through this same API in a single call.
Authentication
Send your key in the x-api-key header. That is the only auth step — there is no token exchange and no per-endpoint scope to configure. Authentication covers creating, rotating and revoking keys.
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
Parameters
Sent as JSON in the request body. Premium parameters are accepted on every plan but only take effect on plans that include them.
| Parameter | Type | Description |
|---|---|---|
uaRequired | string | The user agent string to parse |
Response
Every API returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape. Response format covers the envelope, the other output formats and how premium fields are withheld.
{
"status": "ok",
"error": null,
"data": {
"ua": "Mozilla/5.0 (Windows NT 6.4) AppleWebKit/537.36.0 (KHTML, like Gecko) Chrome/60.0.0.0 Safari/537.36.0",
"browser": {
"name": "Chrome",
"version": "60.0.0.0",
"major": "60"
},
"engine": {
"name": "Blink",
"version": "60.0.0.0"
},
"os": {
"name": "Windows",
"version": "10"
},
"device": {},
"cpu": {},
"isMobile": false,
"isBot": false,
"summary": "Chrome 60 on Windows 10"
}
}Response fields
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
ua | string | "Mozilla/5.0 (Windows NT 6.4) AppleWebKit/537.36.0 (KHTML, like Gecko) Chrome/60.0.0.0 Safari/537.36.0" | The original user agent string that was parsed |
browser | object | {...} | |
name | string | "Chrome" | Name of the browser (e.g., Chrome, Firefox, Safari) |
version | string | "60.0.0.0" | Full version of the browser (e.g., 60.0.0.0) |
majorPremium | string | "60" | Major version number of the browser |
engine | object | {...} | |
namePremium | string | "Blink" | Name of the rendering engine (e.g., Blink, WebKit) |
versionPremium | string | "60.0.0.0" | Version of the rendering engine |
os | object | {...} | |
name | string | "Windows" | Operating system name (e.g., Windows, macOS, Linux) |
version | string | "10" | Version of the operating system |
device | object | {...} | Device information object (type, vendor, model) |
cpu | object | {...} | CPU architecture information (architecture type and details) |
isMobile | boolean | false | Whether the user agent is from a mobile device |
isBot | boolean | false | Whether the user agent appears to be a bot/crawler |
summaryPremium | string | "Chrome 60 on Windows 10" | Human-readable summary of browser and OS |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change. Error handling covers the full status list and which of them are worth retrying.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted | A key restriction or IP allow-list; see key scoping. |
429 | Rate limited, or out of credits | Read error to tell them apart; see rate limits. |
Use cases
- Web Analytics
- Use the User Agent Parser API to parse user agent strings for web analytics. Use the data to analyze user behavior, track devices, and optimize user experience
- Content Optimization
- Optimize content by using the User Agent Parser API to parse user agent strings. Use the data to tailor content, improve readability, and enhance user engagement
- Device Detection
- Detect devices by using the User Agent Parser API to parse user agent strings. Use the data to identify devices, optimize layouts, and deliver responsive design
- Browser Detection
- Detect browsers by using the User Agent Parser API to parse user agent strings. Use the data to identify browsers, optimize compatibility, and enhance user experience
Other ways to use User Agent Parser
Set up User Agent Parser on APIVerve, or reach the same source a different way. Your APIVerve account and credits work on all of them — one key, one balance.
Related
More in Parsers: