Loading
Loading
Parse any User-Agent string to obtain detailed information about the browser, device, and operating system. Also detects crawlers, bots, and potential attack sources.
The User Agent Parser API takes a User-Agent header and returns a structured JSON response with browser name, version, engine details, device information, and operating system data. Supports desktop, mobile, tablet, and crawler detection.
Authorize every request with your API key, passed either as a header or as a query parameter:
X-apiKeyapiKeyThis is version v1.0 of the API.
The following query parameter can optionally be used.
formatoptionalStringdefault: jsonjson (default) or xml.The following header is included in your API request.
User-AgentoptionalStringUser-agent string to parse.
A successful request returns a 200 OK response with a JSON object containing the parsed user-agent data. The response includes the top-level fields listed below. See the response preview on the right for the full JSON structure.
user_agent_stringThe raw User-Agent string.
nameThe name of the browser or crawler.
typeThe type (e.g. Browser, Robot, Hacker)
versionThe full version string.
version_majorThe major version.
name (String), type (String), brand (String), cpu (String)
name (String), type (String), version (String), version_major (String)
name (String), type (String), version (String), version_major (String), build (String)
Besides the response body, every response carries custom headers you can use to track credit usage, and concurrency usage on endpoints that enforce a concurrency limit. See the Custom Response Headers documentation and the endpoints with concurrency limits for more details.
X-Concurrent-Threadsheaderconcurrency-limited endpointsSpecifies the maximum number of concurrent requests allowed.
X-Concurrent-Threads-Activeheaderconcurrency-limited endpointsIndicates the number of active concurrent requests being processed.
X-AF-Credits-Costheaderall responsesSpecifies the number of credits consumed by the current request.
DesktopThis device is a Desktop/Laptop.
MobileThis device is a mobile device however we are not sure if its a tablet, watch, e-reader or phone.
TabletThis device is a Tablet.
PhoneThis device is a mobile Phone.
WatchThis device is a watch or device with tiny screen.
Virtual RealityThis is VR capable mobile device.
eReaderDevice with e-ink screen.
Set-top boxA connected device that can interact with TV screen.
TVSmart TV.
Game ConsoleFixed game consoles like PS and XBox.
Handheld Game ConsoleMobile game systems like the 3DS.
VoiceA voice driven device that reads the page loud.
RobotRobot crawler.
Robot MobileMobile device Robot crawler.
Robot ImitatorRobots that pretend to be Google or Bing crawlers but they usually are not official crawlers.
HackerEither the User Agent String is malformed or some kind of scripting is detected in it.
AnonymizedThe User Agent has been altered by anonymization software.
UnknownWe can't extract the device information from the User Agent.
Besides the response body, every response carries custom headers you can use to track credit usage, and concurrency usage on endpoints that enforce a concurrency limit. See the Custom Response Headers documentation and the endpoints with concurrency limits for more details.
X-Concurrent-Threadsheaderconcurrency-limited endpointsSpecifies the maximum number of concurrent requests allowed.
X-Concurrent-Threads-Activeheaderconcurrency-limited endpointsIndicates the number of active concurrent requests being processed.
X-AF-Credits-Costheaderall responsesSpecifies the number of credits consumed by the current request.
DesktopA Desktop OS (Desktop/Laptop)
MobileA Mobile OS (Tablet/Mobile/Watch)
Game ConsoleGame Console like PlayStation.
EmbeddedAn Embedded device (TV, RTOS etc)
CloudSomething running in the cloud environment.
HackerA Hacker.
AnonymizedExplicitly hidden with some software.
UnknownWe really don't know about this OS.
Besides the response body, every response carries custom headers you can use to track credit usage, and concurrency usage on endpoints that enforce a concurrency limit. See the Custom Response Headers documentation and the endpoints with concurrency limits for more details.
X-Concurrent-Threadsheaderconcurrency-limited endpointsSpecifies the maximum number of concurrent requests allowed.
X-Concurrent-Threads-Activeheaderconcurrency-limited endpointsIndicates the number of active concurrent requests being processed.
X-AF-Credits-Costheaderall responsesSpecifies the number of credits consumed by the current request.
BrowserRegular Web Browser.
Mobile AppA mobile app with webview or an app that includes regular browser.
HackerSomeone with malicious stuff in useragent string or malformed UA string.
RobotA web crawler.
UnknownWe don't know anything about the identity of this device.
Besides the response body, every response carries custom headers you can use to track credit usage, and concurrency usage on endpoints that enforce a concurrency limit. See the Custom Response Headers documentation and the endpoints with concurrency limits for more details.
X-Concurrent-Threadsheaderconcurrency-limited endpointsSpecifies the maximum number of concurrent requests allowed.
X-Concurrent-Threads-Activeheaderconcurrency-limited endpointsIndicates the number of active concurrent requests being processed.
X-AF-Credits-Costheaderall responsesSpecifies the number of credits consumed by the current request.
BrowserRegular Web Browser.
Browser WebviewRegular browser being used in a mobile app.
Mobile AppA mobile app accessing the website.
Robot MobileA web crawler who want to be detected as mobile.
Cloud ApplicationSomething running in the cloud (can be web scrapper etc.)
Email ClientAn email client.
VoiceVoice enabled browser that reads out loud.
SpecialSomething special we can't classify.
TestclientWebsite testing tool.
HackerSomeone with malicious stuff in useragent string or malformed UA string.
UnknownWe don't know.
Besides the response body, every response carries custom headers you can use to track credit usage, and concurrency usage on endpoints that enforce a concurrency limit. See the Custom Response Headers documentation and the endpoints with concurrency limits for more details.
X-Concurrent-Threadsheaderconcurrency-limited endpointsSpecifies the maximum number of concurrent requests allowed.
X-Concurrent-Threads-Activeheaderconcurrency-limited endpointsIndicates the number of active concurrent requests being processed.
X-AF-Credits-Costheaderall responsesSpecifies the number of credits consumed by the current request.