Docs/APIs/User Agent Generator

User Agent Generator

Generate user agent strings

OperationalCredits 1 per callp50 389msData GenerationStar

Overview

User Agent Generator works by generating a random user agent string based on the browser, operating system, and device. It returns the generated user agent string 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.

GEThttps://api.apiverve.com/v1/useragentgenerator
curl "https://api.apiverve.com/v1/useragentgenerator?device=desktop" \
  -H "x-api-key: your_api_key_here"
const res = await fetch('https://api.apiverve.com/v1/useragentgenerator?device=desktop', {
  headers: { 'x-api-key': 'your_api_key_here' },
});

if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);

const { data } = await res.json();
console.log(data);
import requests

res = requests.get(
    "https://api.apiverve.com/v1/useragentgenerator?device=desktop",
    headers={"x-api-key": "your_api_key_here"},
    timeout=15,
)
res.raise_for_status()

print(res.json()["data"])
package main

import (
	"fmt"
	"io"
	"net/http"
)

func main() {
	req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/useragentgenerator?device=desktop", nil)
	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.

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.

Parameters

Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them.

ParameterTypeDescription
deviceRequiredstringThe device type for the user agent string
desktopmobiletablet
default desktop

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.

Sample response
{
  "status": "ok",
  "error": null,
  "data": {
    "ua": "Mozilla/5.0 (Windows NT 6.4) AppleWebKit/537.36.0 (KHTML, like Gecko) Chrome/94.0.0.0 Safari/537.36.0",
    "browser": {
      "name": "Chrome",
      "version": "94.0.0.0",
      "major": "94"
    },
    "engine": {
      "name": "Blink",
      "version": "94.0.0.0"
    },
    "os": {
      "name": "Windows",
      "version": "10"
    },
    "device": {},
    "cpu": {}
  }
}

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.

FieldTypeExampleDescription
uastring"Mozilla/5.0 (Windows NT 6.4) AppleWebKit/537.36.0 (KHTML, like Gecko) Chrome/94.0.0.0 Safari/537.36.0"Complete user agent string representing browser environment
browserobject{...}
namestring"Chrome"Name of the browser (e.g., Chrome, Firefox, Safari)
versionstring"94.0.0.0"Full browser version number including all segments
majorstring"94"Major version number of the browser
engineobject{...}
namePremiumstring"Blink"JavaScript engine name (e.g., Blink, WebKit, Gecko)
versionPremiumstring"94.0.0.0"JavaScript engine version number
osobject{...}
namestring"Windows"Operating system name (e.g., Windows, macOS, Linux)
versionstring"10"Operating system version number
devicePremiumobject{...}Device information object containing vendor and model details
cpuPremiumobject{...}CPU architecture and processor information

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.

StatusMeaningWhat to do
400Input was rejectedRead error; it names the parameter.
401Key missing or invalidCheck the header name and the key value.
403Key valid, but not permittedA key restriction or IP allow-list; see key scoping.
429Rate limited, or out of creditsRead error to tell them apart; see rate limits.

Use cases

Web Scraping
Use the User Agent Generator API to generate user agent strings for web scraping. Use the data to scrape websites, collect data, and automate tasks
Browser Testing
Generate user agent strings by using the User Agent Generator API for browser testing. Use the data to test compatibility, verify functionality, and ensure performance
Device Simulation
Simulate devices by using the User Agent Generator API to generate user agent strings. Use the data to emulate devices, test responsiveness, and optimize layouts
Website Testing
Test websites by using the User Agent Generator API to generate user agent strings. Use the data to test functionality, verify compatibility, and ensure performance

Other ways to use User Agent Generator

Set up User Agent Generator on APIVerve, or reach the same source a different way. Your APIVerve account and credits work on all of them — one key, one balance.

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

More in Data Generation:

Was this page helpful?