User Agent Parser API

POST

Detect the browser, OS, and device behind every incoming request.

User Agent Parser extracts browser, operating system, and hardware details from user agent strings. It identifies device types, CPU architecture, and bot traffic on every incoming HTTP request.

Try it — live request, no key required

Request

POSTapi.apiverve.com/v1/useragentparser

Body

uastring

Verification

Format

No key required to try it. Get a key to use it in your app.

Example

{
  "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,
    "deviceType": "desktop",
    "summary": "Chrome 60 on Windows 10"
  }
}

About the User Agent Parser API

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.

What people use it for

Adaptive Asset Delivery: Web servers inspect the device type and mobile flag to serve lightweight media assets and alternate layouts to smartphones and tablets.
Crawler Traffic Segregation: When incoming requests arrive, API gateways read the bot flag to filter out search engine spiders and scrapers from application metrics.
Compatibility Banner Triggers: Flag outdated client environments before pages fail by evaluating the reported browser version against required feature sets.
Platform Installer Matching: To route downloads accurately, software distribution sites match the visitor's operating system and CPU architecture directly to the right installer package.

Ways to call it

One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.

JSON: Default REST response
XML: Markup format
YAML: Human-readable
CSV: Tabular export
GraphQL: Query language
MCP: For AI agents

View all integrations →

Other ways to use User Agent Parser

Same data, same APIVerve account, same credit balance — one key works on all of them.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.on VerveKit

Questions.

Common questions about the User Agent Parser API.

Read the docs →

Is it cheap enough to parse user agents on every incoming request?

Yes. Each parse costs 2 credits, allowing 100,000 user agent lookups each month on the Starter plan. That works out to about $0.30 per 1,000 calls, or $0.0003 per request. The Free plan includes 100 calls per month for testing.

Are rendering engine details and the summary string included on the Free plan?

No. Rendering engine name and version, the browser major version number, and the human-readable summary are premium fields. Free plan requests omit these attributes. Any paid plan, starting with Starter, unlocks all premium fields.

Can it detect automated bots and search engine crawlers?

Yes. The response includes a dedicated isBot flag alongside standard browser detection. When an automated crawler or bot agent is parsed, this field flags the traffic so your application can treat bot requests separately from regular human visitors.

What hardware and device information does the parser return?

It extracts device type, vendor, and model data from the user agent string. It also returns an isMobile boolean flag to distinguish mobile devices from desktop computers, along with CPU architecture details when present in the string.

Does it return exact version numbers for browsers and operating systems?

Yes. User Agent Parser returns the full version string and name for both the browser and the operating system. Full release versions such as Chrome 60.0.0.0 or specific OS versions like Windows and macOS are parsed into distinct fields.

Request parameters — POST /v1/useragentparser

Sent as JSON in the request body. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.

Required

Parameter	Type	Example	Description
`ua`Required	string	`Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36`	The user agent string to parse

Example request

curl -X POST "https://api.apiverve.com/v1/useragentparser" \
  -H "x-api-key: YOUR_API_KEY" \
  -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"}'

Authentication

Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.

Header	When	Value
`x-api-key`Required	Every request	Your API key. Header names are case-insensitive, so `X-API-Key` is the same header.
`Authorization`Alternate	Instead of the above	`Bearer <key>` — for clients that only expose bearer auth. Resolves to the same account and the same billing.
`content-type`Required	POST body	`application/json`

401 is the only auth verdict

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.

Response — POST /v1/useragentparser

Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.

Sample 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": {},
    "isMobile": false,
    "isBot": false,
    "deviceType": "desktop",
    "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	`{...}`	Browser detected in the user agent; empty when none is recognised
`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)
`major`Premium	string	`"60"`	Major version number of the browser
`engine`	object	`{...}`	Rendering engine detected in the user agent
`name`Premium	string	`"Blink"`	Name of the rendering engine (e.g., Blink, WebKit)
`version`Premium	string	`"60.0.0.0"`	Version of the rendering engine
`os`	object	`{...}`	Operating system detected in the user agent
`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
`deviceType`	string	`"desktop"`	Device class: desktop, mobile, tablet, console, smarttv, wearable, embedded, xr or bot; null when it can't be determined
`summary`Premium	string	`"Chrome 60 on Windows 10"`	Human-readable summary of browser and OS

Response headers

Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.

Header	What it carries
`x-api-remaining-credits`	Credits left in the current cycle
`x-api-credits-used`	Credits spent in the current cycle
`x-api-max-credits`	The allowance for the cycle
`x-api-version`	Version of the endpoint that answered

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.

Status	Meaning	What to do
`400`	Input was rejected	Read `error`; it names the parameter that has to change.
`401`	Key missing or invalid	Check the header name and the key value.
`403`	Key valid, but not permitted here	A key restriction or an IP allow-list — never a bad key.
`429`	Rate limited, or out of credits	Read `error` to tell them apart, then back off or top up.

What a call costs — 2 credits per call

Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.

Plan	Per month	Credits	User Agent Parser calls	Per 1,000 calls
Free	Free	200	100	Free
Starter	$29.99	200,000	100,000	$0.30
Pro	$99.99	1,000,000	500,000	$0.20
Mega	$299.99	4,000,000	2,000,000	$0.15

Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.

Compare all pricing tiers →

Call it from cURL — POST /v1/useragentparser

No SDK to install — this is a plain HTTPS call to /v1/useragentparser with your key in the x-api-key header. Swap in a real key and it runs as-is.

cURL

1
2

curl "https://api.apiverve.com/v1/useragentparser" \
  -H "x-api-key: YOUR_API_KEY"

Resources

GitHubapiverve/useragentparser-apiSource, issues and the examples this page is built from.ReferenceUser Agent Parser API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/useragentparsernpm apiverve-useragentparserPyPI APIVerve.API.UserAgentParserNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Node.js — POST /v1/useragentparser

Install the Node.js SDK, then call the User Agent Parser API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — npm

npm install @apiverve/useragentparser

Node.js

const res = await fetch("https://api.apiverve.com/v1/useragentparser", {
  headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);

Resources

npm@apiverve/useragentparserThe published Node.js client, versioned and signed.GitHubapiverve/useragentparser-apiSource, issues and the examples this page is built from.ReferenceUser Agent Parser API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

apiverve-useragentparserPyPI APIVerve.API.UserAgentParserNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Python — POST /v1/useragentparser

Install the Python SDK, then call the User Agent Parser API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — PyPI

pip install apiverve-useragentparser

Python

import requests

res = requests.get(
    "https://api.apiverve.com/v1/useragentparser",
    headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])

Resources

PyPIapiverve-useragentparserThe published Python client, versioned and signed.GitHubapiverve/useragentparser-apiSource, issues and the examples this page is built from.ReferenceUser Agent Parser API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/useragentparsernpm APIVerve.API.UserAgentParserNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from C# / .NET — POST /v1/useragentparser

Install the C# / .NET SDK, then call the User Agent Parser API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — NuGet

dotnet add package APIVerve.API.UserAgentParser

C# / .NET

using var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");

var json = await client.GetStringAsync("https://api.apiverve.com/v1/useragentparser");
Console.WriteLine(json);

Resources

NuGetAPIVerve.API.UserAgentParserThe published C# / .NET client, versioned and signed.GitHubapiverve/useragentparser-apiSource, issues and the examples this page is built from.ReferenceUser Agent Parser API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/useragentparsernpm apiverve-useragentparserPyPI

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Go — POST /v1/useragentparser

No SDK to install — this is a plain HTTPS call to /v1/useragentparser with your key in the x-api-key header. Swap in a real key and it runs as-is.

req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/useragentparser", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")

res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))

Resources

Also published for

@apiverve/useragentparsernpm apiverve-useragentparserPyPI APIVerve.API.UserAgentParserNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from PHP — POST /v1/useragentparser

No SDK to install — this is a plain HTTPS call to /v1/useragentparser with your key in the x-api-key header. Swap in a real key and it runs as-is.

PHP

$ch = curl_init("https://api.apiverve.com/v1/useragentparser");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);

$response = curl_exec($ch);
echo $response;

Resources

Also published for

@apiverve/useragentparsernpm apiverve-useragentparserPyPI APIVerve.API.UserAgentParserNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Ruby — POST /v1/useragentparser

No SDK to install — this is a plain HTTPS call to /v1/useragentparser with your key in the x-api-key header. Swap in a real key and it runs as-is.

Ruby

require "net/http"

uri = URI("https://api.apiverve.com/v1/useragentparser")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"

res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.body

Resources

Also published for

@apiverve/useragentparsernpm apiverve-useragentparserPyPI APIVerve.API.UserAgentParserNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

All articles →

What Your User Agent String RevealsEvery HTTP request announces who you are. Here's what's in that string and what you can do with it.Read

Extract Clean Content from Any WebpageTurn messy web pages into clean Markdown. Perfect for content migration, archiving, AI training data, and building read-later tools.Read

Take Your App Multilingual (No Rewrite)Add language support to an existing app without rearchitecting. Practical strategies for translation, detection, and localization.Read

User Agent Parser API

Try it — live request, no key required

About the User Agent Parser API

What people use it for

Ways to call it

Other ways to use User Agent Parser

Questions.

Request parameters — POST /v1/useragentparser

Required

Authentication

Response — POST /v1/useragentparser

Response fields

Response headers

Errors

What a call costs — 2 credits per call

Call it from cURL — POST /v1/useragentparser

Resources

Also published for

Call it from Node.js — POST /v1/useragentparser

Resources

Also published for

Call it from Python — POST /v1/useragentparser

Resources

Also published for

Call it from C# / .NET — POST /v1/useragentparser

Resources

Also published for

Call it from Go — POST /v1/useragentparser

Resources

Also published for

Call it from PHP — POST /v1/useragentparser

Resources

Also published for

Call it from Ruby — POST /v1/useragentparser

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — User Agent Parser API

Parsers

Related articles

Ready to build with User Agent Parser? Start with 200 free credits — one key unlocks all 300+ APIs.

Explore the catalog