User Agent Parser
User Agent Parser is a simple tool for parsing user agent strings. It returns the browser, operating system, and more from the user agent string.
The User Agent Parser API provides reliable and fast access to user agent parser data through a simple REST interface. Built for developers who need consistent, high-quality results with minimal setup time.
To use User Agent Parser, you need an API key. You can get one by creating a free account and visiting your dashboard.
POST Endpoint
https://api.apiverve.com/v1/useragentparserCode Examples
Here are examples of how to call the User Agent Parser API in different programming languages:
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 response = 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"
})
});
const data = await response.json();
console.log(data);import requests
headers = {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
payload = {
"ua": "Mozilla/5.0 (Windows NT 6.4) AppleWebKit/537.36.0 (KHTML, like Gecko) Chrome/60.0.0.0 Safari/537.36.0"
}
response = requests.post('https://api.apiverve.com/v1/useragentparser', headers=headers, json=payload)
data = response.json()
print(data)const https = require('https');
const url = require('url');
const options = {
method: 'POST',
headers: {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
};
const postData = 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"
});
const req = https.request('https://api.apiverve.com/v1/useragentparser', options, (res) => {
let data = '';
res.on('data', (chunk) => data += chunk);
res.on('end', () => console.log(JSON.parse(data)));
});
req.write(postData);
req.end();<?php
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, 'https://api.apiverve.com/v1/useragentparser');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_CUSTOMREQUEST, 'POST');
curl_setopt($ch, CURLOPT_HTTPHEADER, [
'X-API-Key: your_api_key_here',
'Content-Type: application/json'
]);
curl_setopt($ch, CURLOPT_POSTFIELDS, json_encode({
'ua': 'Mozilla/5.0 (Windows NT 6.4) AppleWebKit/537.36.0 (KHTML, like Gecko) Chrome/60.0.0.0 Safari/537.36.0'
}));
$response = curl_exec($ch);
curl_close($ch);
$data = json_decode($response, true);
print_r($data);
?>package main
import (
"fmt"
"io"
"net/http"
"bytes"
"encoding/json"
)
func main() {
payload := map[string]interface{}{
"ua": "Mozilla/5.0 (Windows NT 6.4) AppleWebKit/537.36.0 (KHTML, like Gecko) Chrome/60.0.0.0 Safari/537.36.0"
}
jsonPayload, _ := json.Marshal(payload)
req, _ := http.NewRequest("POST", "https://api.apiverve.com/v1/useragentparser", bytes.NewBuffer(jsonPayload))
req.Header.Set("X-API-Key", "your_api_key_here")
req.Header.Set("Content-Type", "application/json")
client := &http.Client{}
resp, err := client.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()
body, _ := io.ReadAll(resp.Body)
fmt.Println(string(body))
}require 'net/http'
require 'json'
uri = URI('https://api.apiverve.com/v1/useragentparser')
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true
payload = {
"ua": "Mozilla/5.0 (Windows NT 6.4) AppleWebKit/537.36.0 (KHTML, like Gecko) Chrome/60.0.0.0 Safari/537.36.0"
}
request = Net::HTTP::Post.new(uri)
request['X-API-Key'] = 'your_api_key_here'
request['Content-Type'] = 'application/json'
request.body = payload.to_json
response = http.request(request)
puts JSON.pretty_generate(JSON.parse(response.body))using System;
using System.Net.Http;
using System.Text;
using System.Threading.Tasks;
class Program
{
static async Task Main(string[] args)
{
using var client = new HttpClient();
client.DefaultRequestHeaders.Add("X-API-Key", "your_api_key_here");
var jsonContent = @"{
""ua"": ""Mozilla/5.0 (Windows NT 6.4) AppleWebKit/537.36.0 (KHTML, like Gecko) Chrome/60.0.0.0 Safari/537.36.0""
}";
var content = new StringContent(jsonContent, Encoding.UTF8, "application/json");
var response = await client.PostAsync("https://api.apiverve.com/v1/useragentparser", content);
response.EnsureSuccessStatusCode();
var responseBody = await response.Content.ReadAsStringAsync();
Console.WriteLine(responseBody);
}
}Authentication
The User Agent Parser API requires authentication via API key. Include your API key in the request header:
X-API-Key: your_api_key_hereInteractive API Playground
Test the User Agent Parser API directly in your browser with live requests and responses.
Parameters
The following parameters are available for the User Agent Parser API:
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
| ua | string | Yes | The user agent string to parse | - | - |
Response
The User Agent Parser API returns responses in JSON, XML, YAML, and CSV formats:
Example Responses
{
"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": {}
}
}<?xml version="1.0" encoding="UTF-8"?>
<response>
<status>ok</status>
<error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<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</ua>
<browser>
<name>Chrome</name>
<version>60.0.0.0</version>
<major>60</major>
</browser>
<engine>
<name>Blink</name>
<version>60.0.0.0</version>
</engine>
<os>
<name>Windows</name>
<version>10</version>
</os>
<device>
</device>
<cpu>
</cpu>
</data>
</response>
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: {}
| key | value |
|---|---|
| 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 | {} |
Response Structure
All API responses follow a consistent structure with the following fields:
| Field | Type | Description | Example |
|---|---|---|---|
| status | string | Indicates whether the request was successful ("ok") or failed ("error") | ok |
| error | string | null | Contains error message if status is "error", otherwise null | null |
| data | object | null | Contains the API response data if successful, otherwise null | {...} |
Response Data Fields
When the request is successful, the data object contains the following fields:
| Field | Type | Sample Value |
|---|---|---|
| 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" |
| browser | object | {...} |
| â”” name | string | "Chrome" |
| â”” version | string | "60.0.0.0" |
| â”” major | string | "60" |
| engine | object | {...} |
| â”” name | string | "Blink" |
| â”” version | string | "60.0.0.0" |
| os | object | {...} |
| â”” name | string | "Windows" |
| â”” version | string | "10" |
| device | object | {...} |
| cpu | object | {...} |
Headers
Required and optional headers for API requests:
| Header Name | Required | Example Value | Description |
|---|---|---|---|
| X-API-Key | Yes | your_api_key_here | Your APIVerve API key. Found in your dashboard under API Keys. |
| Accept | No | application/json | Specify response format: application/json (default), application/xml, or application/yaml |
| User-Agent | No | MyApp/1.0 | Identifies your application for analytics and debugging purposes |
| X-Request-ID | No | req_123456789 | Custom request identifier for tracking and debugging requests |
| Cache-Control | No | no-cache | Control caching behavior for the request and response |
GraphQL AccessALPHA
Most APIVerve APIs support GraphQL queries, allowing you to combine multiple API calls into a single request and retrieve only the data you need. This powerful feature enables you to orchestrate complex data fetching with precise field selection.
Not all APIs support GraphQL. Check the API schema or test in the GraphQL Explorer to confirm availability for this specific endpoint.
Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.
POST https://api.apiverve.com/v1/graphqlquery {
useragentparser(
input: {
ua: "Mozilla/5.0 (Windows NT 6.4) AppleWebKit/537.36.0 (KHTML, like Gecko) Chrome/60.0.0.0 Safari/537.36.0"
}
) {
ua
browser {
name
version
major
}
engine {
name
version
}
os {
name
version
}
device {
}
cpu {
}
}
}Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.
CORS Support
The User Agent Parser API supports Cross-Origin Resource Sharing (CORS) with wildcard configuration, allowing you to call User Agent Parser directly from browser-based applications without proxy servers.
| CORS Header | Value | Description |
|---|---|---|
| Access-Control-Allow-Origin | * | Accepts requests from any origin |
| Access-Control-Allow-Methods | * | Accepts any HTTP method |
| Access-Control-Allow-Headers | * | Accepts any request headers |
Browser Usage: You can make direct API calls from JavaScript running in the browser without encountering CORS errors. No additional configuration needed.
Rate Limiting
APIVerve implements rate limiting to ensure fair usage and maintain service quality across all users. Rate limits vary by subscription plan and are applied per API key.
| Plan | Rate Limit | Description |
|---|---|---|
| Free | 5 requests/min | Hard rate limit enforced - exceeding will return 429 errors |
| Starter | No Limit | Production ready - no rate limiting or throttling |
| Pro | No Limit | Production ready - no rate limiting or throttling |
| Mega | No Limit | Production ready - no rate limiting or throttling |
Rate Limit Headers
When rate limits apply, each API response includes headers to help you track your usage:
| Header | Description |
|---|---|
| X-RateLimit-Limit | Maximum number of requests allowed per time window |
| X-RateLimit-Remaining | Number of requests remaining in the current window |
| X-RateLimit-Reset | Unix timestamp when the rate limit window resets |
Handling Rate Limits
Free Plan: When you exceed your rate limit, User Agent Parser returns a 429 Too Many Requests status code. Your application should implement appropriate backoff logic to handle this gracefully.
Paid Plans: No rate limiting or throttling applied. All paid plans (Starter, Pro, Mega) are production-ready.
Best Practices:
- Monitor the rate limit headers to track your usage (Free plan only)
- Implement caching where appropriate to reduce API calls
- Upgrade to Pro or Mega for guaranteed no-throttle performance
Note: Rate limits are separate from credit consumption. You may have credits remaining but still hit rate limits on Free tier.
Client Libraries
To get started with minimal code, most of our APIs are available through client libraries and clients:
Error Codes
The User Agent Parser API uses standard HTTP status codes to indicate success or failure:
| Code | Message | Description | Solution |
|---|---|---|---|
| 200 | OK | Request successful, data returned | No action needed - request was successful |
| 400 | Bad Request | Invalid request parameters or malformed request | Check required parameters and ensure values match expected formats |
| 401 | Unauthorized | Missing or invalid API key | Include x-api-key header with valid API key from dashboard |
| 403 | Forbidden | API key lacks permission or insufficient credits | Check credit balance in dashboard or upgrade plan |
| 429 | Too Many Requests | Rate limit exceeded (Free: 5 req/min) | Implement request throttling or upgrade to paid plan |
| 500 | Internal Server Error | Server error occurred | Retry request after a few seconds, contact support if persists |
| 503 | Service Unavailable | API temporarily unavailable | Wait and retry, check status page for maintenance updates |
Need help? Contact support with your X-Request-ID for assistance.
Integrate User Agent Parser with No-Code Tools
Connect the User Agent Parser API to your favorite automation platform without writing code. Build workflows that leverage user agent parser data across thousands of apps.





All platforms use your same API key to access User Agent Parser. Visit our integrations hub for step-by-step setup guides.
Frequently Asked Questions
How do I get an API key?
What are credits and how do they work?
Credits are your API usage currency. Each successful API call consumes credits based on the API's complexity. Most APIs cost 1 credit per call, while more complex APIs may cost 2-5 credits. Failed requests and errors don't consume credits. Check the API details above to see the credit cost for this specific API.
Can I use User Agent Parser in production?
The free plan is for testing and development only. For production use of User Agent Parser, upgrade to a paid plan (Starter, Pro, or Mega) which includes commercial use rights, no attribution requirements, and guaranteed uptime SLAs. All paid plans are production-ready.
Can I use User Agent Parser from a browser?
What happens if I exceed my credit limit?
When you reach your monthly credit limit, API requests will return an error until you upgrade your plan or wait for the next billing cycle. You'll receive notifications at 80% and 95% usage to give you time to upgrade if needed.



