USB Vendor Lookup API

GET

Identify the manufacturer and device model behind any USB ID.

USB Vendor Lookup allows you to identify USB device manufacturers and products by their vendor ID and product ID. It uses the Linux USB ID Repository, which contains thousands of USB vendor and product identifiers.

Try it — live request, no key required

Request

GETapi.apiverve.com/v1/usbvendorlookup?vendorid=05AC

Query parameters

vendoridstring

Verification

Format

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

Example

{
  "status": "ok",
  "error": null,
  "data": {
    "vendorId": "05AC",
    "productId": "8290",
    "found": true,
    "vendor": "Apple, Inc.",
    "product": "iPhone"
  }
}

About the USB Vendor Lookup API

USB Vendor Lookup works by matching USB vendor IDs (VID) and product IDs (PID) against a comprehensive database maintained by the Linux USB project. The database is updated weekly to ensure accurate and up-to-date information.

What people use it for

Device Identification: Identify unknown USB devices by their vendor and product IDs. Useful for IT asset management and inventory tracking.
Hardware Diagnostics: Diagnose USB device issues by looking up manufacturer information and product details.
Security Auditing: Audit USB devices connected to your network by identifying manufacturers and device types.
Driver Matching: Help users find appropriate drivers by identifying the exact manufacturer and product model.

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 USB Vendor Lookup

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 Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.on VerveSheets Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.on VerveContext

Questions.

Common questions about the USB Vendor Lookup API.

Read the docs →

How far does the Starter plan go for USB device lookups?

Starter covers up to 100,000 lookups each month at 2 credits per request. That works out to about $0.30 per 1,000 calls, or $0.0003 per query. The Free plan includes 100 lookups per month for development and testing.

Where does the USB vendor and product data come from?

USB Vendor Lookup is powered by the Linux USB ID Repository maintained by the Linux USB project. The catalog indexes thousands of vendor and product identifiers and updates weekly to incorporate newly registered devices.

Can I identify a manufacturer without providing a product ID?

Yes, the product ID parameter is optional. Passing only a valid vendor ID returns the registered manufacturer name without requiring specific device hardware details.

What format do vendor and product IDs need to be in?

Both identifiers must be passed as 4-digit hexadecimal strings, such as 05AC. Passing numbers in decimal form or omitting leading zeroes will prevent the database from finding a match.

Can I use USB lookup data in a commercial diagnostic tool?

Yes, commercial use is permitted on all paid plans. You may display vendor and product information directly inside your diagnostic software or auditing platform, though redistributing or reselling the raw data is not allowed.

Request parameters — GET /v1/usbvendorlookup

Sent in the query string. 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
`vendorid`Required	string	`05AC`	The USB vendor ID in 4-digit hex format (e.g., 05AC for Apple) length 4-4

Optional

Parameter	Type	Example	Description
`productid`Optional	string	`8290`	The USB product ID in 4-digit hex format (optional) length 4-4

Example request

1
2

curl "https://api.apiverve.com/v1/usbvendorlookup?vendorid=05AC&productid=8290" \
  -H "x-api-key: YOUR_API_KEY"

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.

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 — GET /v1/usbvendorlookup

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": {
    "vendorId": "05AC",
    "productId": "8290",
    "found": true,
    "vendor": "Apple, Inc.",
    "product": "iPhone"
  }
}

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
`vendorId`	string	`"05AC"`	USB vendor ID in 4-digit hexadecimal format
`productId`	string	`"8290"`	USB product ID in 4-digit hexadecimal format
`found`	boolean	`true`	Whether the vendor/product combination exists in database
`vendor`	string	`"Apple, Inc."`	Manufacturer name corresponding to vendor ID
`product`	string	`"iPhone"`	Device product name corresponding to product ID

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	USB Vendor Lookup 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 — GET /v1/usbvendorlookup

No SDK to install — this is a plain HTTPS call to /v1/usbvendorlookup 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/usbvendorlookup" \
  -H "x-api-key: YOUR_API_KEY"

Resources

GitHubapiverve/usbvendorlookup-apiSource, issues and the examples this page is built from.ReferenceUSB Vendor Lookup API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/usbvendorlookupnpm APIVerve.API.USBVendorLookupNuGet

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

Call it from Node.js — GET /v1/usbvendorlookup

Install the Node.js SDK, then call the USB Vendor Lookup 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/usbvendorlookup

Node.js

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

Resources

npm@apiverve/usbvendorlookupThe published Node.js client, versioned and signed.GitHubapiverve/usbvendorlookup-apiSource, issues and the examples this page is built from.ReferenceUSB Vendor Lookup API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

APIVerve.API.USBVendorLookupNuGet

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

Call it from Python — GET /v1/usbvendorlookup

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

Python

import requests

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

Resources

Also published for

@apiverve/usbvendorlookupnpm APIVerve.API.USBVendorLookupNuGet

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

Call it from C# / .NET — GET /v1/usbvendorlookup

Install the C# / .NET SDK, then call the USB Vendor Lookup 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.USBVendorLookup

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/usbvendorlookup");
Console.WriteLine(json);

Resources

NuGetAPIVerve.API.USBVendorLookupThe published C# / .NET client, versioned and signed.GitHubapiverve/usbvendorlookup-apiSource, issues and the examples this page is built from.ReferenceUSB Vendor Lookup API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/usbvendorlookupnpm

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

Call it from Go — GET /v1/usbvendorlookup

No SDK to install — this is a plain HTTPS call to /v1/usbvendorlookup 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/usbvendorlookup", 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/usbvendorlookupnpm APIVerve.API.USBVendorLookupNuGet

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

Call it from PHP — GET /v1/usbvendorlookup

No SDK to install — this is a plain HTTPS call to /v1/usbvendorlookup 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/usbvendorlookup");
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/usbvendorlookupnpm APIVerve.API.USBVendorLookupNuGet

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

Call it from Ruby — GET /v1/usbvendorlookup

No SDK to install — this is a plain HTTPS call to /v1/usbvendorlookup 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/usbvendorlookup")
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/usbvendorlookupnpm APIVerve.API.USBVendorLookupNuGet

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

All articles →

7 SSL Certificate Problems That Kill TrustExpired certs, mismatched domains, weak encryption. A practical checklist for catching SSL issues before your users do.Read

How to Detect VPN and Proxy UsersIdentify VPN, proxy, and datacenter IPs to prevent fraud and enforce geo-restrictions. Complete tutorial with code examples.Read

Preventing Fake Signups: Registration Fraud GuideLearn how to stop bots and fraudsters while maintaining conversion rates for legitimate users.Read

USB Vendor Lookup API

Try it — live request, no key required

About the USB Vendor Lookup API

What people use it for

Ways to call it

Other ways to use USB Vendor Lookup

Questions.

Request parameters — GET /v1/usbvendorlookup

Required

Optional

Authentication

Response — GET /v1/usbvendorlookup

Response fields

Response headers

Errors

What a call costs — 2 credits per call

Call it from cURL — GET /v1/usbvendorlookup

Resources

Also published for

Call it from Node.js — GET /v1/usbvendorlookup

Resources

Also published for

Call it from Python — GET /v1/usbvendorlookup

Resources

Also published for

Call it from C# / .NET — GET /v1/usbvendorlookup

Resources

Also published for

Call it from Go — GET /v1/usbvendorlookup

Resources

Also published for

Call it from PHP — GET /v1/usbvendorlookup

Resources

Also published for

Call it from Ruby — GET /v1/usbvendorlookup

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — USB Vendor Lookup API

Networking

Related articles

Ready to build with USB Vendor Lookup? Start with 200 free credits — one key unlocks all 300+ APIs.

Explore the catalog