Client info
Browser and device, straight from the request
Client info reads the headers of your request: IP address, device, operating system, browser and languages. Free of charge and with no call to a third party.
For businesses and self-employed professionals only
- Free
/v1/client-info
curl "https://api.flowdata.one/v1/client-info" \
-H "Authorization: Bearer fd_YOUR_KEY"
{
"ipString": "203.0.113.42",
"ipNumeric": 3405803818,
"ipType": "IPv4",
"isBehindProxy": false,
"device": "Mac",
"os": "Mac OS X 10.15.7",
"userAgent": "Chrome 132.0.0.0",
"family": "Chrome",
"versionMajor": "132",
"versionMinor": "0",
"versionPatch": "0",
"isSpider": false,
"isMobile": false,
"userAgentDisplay": "Mac OS X 10.15.7 Mac Chrome 132.0.0.0",
"userAgentRaw": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/132.0.0.0 Safari/537.36",
"userLanguages": [
"de-DE",
"de",
"en-US",
"en"
]
}
A real API response.
Endpoints
One call, no parameters. A valid FlowData key is all it needs.
| GET | /v1/client-info |
Evaluates the IP address and User-Agent of the calling client. |
|---|
What is detected
-
IP address
ipString,ipNumeric,ipTypeandisBehindProxy, based on the usual proxy headers. -
Device and system
device,osandisMobilefrom theUser-Agent. -
Browser
familyand the version number inversionMajor,versionMinorandversionPatch. -
Bots and languages
isSpiderflags known crawlers,userLanguagesreads the preferred languages fromAccept-Language.
Screenshots show the FlowData interface in German, with the example data of a fictional company.
What to keep in mind
Nothing goes to third parties. Every call shows up like any other in your team's request log.
The values come from headers a client can set itself. They are not suitable for security decisions.
Over MCP the answer describes the MCP client, not your end customers.
Client info also needs a key, and the key belongs on your server, not in browser code.