Bluetooth Company Lookup API

GET

Identify the manufacturer behind any Bluetooth device or beacon.

Bluetooth Company Lookup allows you to identify Bluetooth device manufacturers by their Bluetooth SIG assigned company identifier. This helps identify the manufacturer of Bluetooth devices, beacons, and accessories.

Try it — live request, no key required

Request

GETapi.apiverve.com/v1/bluetoothlookup?companyid=76

Query parameters

companyidstring

Verification

Format

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

Example

{
  "status": "ok",
  "error": null,
  "data": {
    "companyId": 76,
    "companyIdHex": "0x004C",
    "found": true,
    "company": "Apple, Inc."
  }
}

About the Bluetooth Company Lookup API

Bluetooth Company Lookup uses the official Bluetooth SIG company identifiers database, which contains thousands of registered Bluetooth manufacturers. The database is updated weekly to include newly registered companies.

What people use it for

Device Identification: Identify Bluetooth devices by their manufacturer company ID. Useful for understanding what devices are in your environment.
Beacon Analysis: Analyze BLE beacons by looking up their manufacturer company ID to understand beacon types and sources.
Security Auditing: Audit Bluetooth devices in your environment by identifying their manufacturers.
IoT Device Management: Manage IoT devices by identifying their Bluetooth manufacturers for compatibility and support.

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 Bluetooth Company 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 Bluetooth Company Lookup API.

Read the docs →

Where does the manufacturer data come from and how often is it updated?

Data is sourced from the official Bluetooth SIG assigned numbers database. The registry is updated weekly to include newly registered companies and hardware manufacturers.

Is it cheap enough to identify the manufacturer for every detected beacon?

Each query costs 2 credits, which comes out to $0.30 per 1,000 calls or about $0.0003 per lookup on the Starter plan. Starter includes 200,000 credits each month, covering 100,000 lookups. You can also evaluate the service with 100 free lookups per month.

Does the lookup accept both hexadecimal and decimal company IDs?

Yes, you can provide company identifiers in either format. You can pass raw decimal values or hex strings with a 0x prefix, and the response provides both representations alongside the manufacturer name.

What happens if a company identifier is not in the database?

When a queried ID does not exist in the official registry, the API returns a response with the found property set to false. Your code can check this flag directly without handling broken schemas.

Can I display these manufacturer names inside a commercial IoT management tool?

Yes, you can integrate and display manufacturer names within commercial applications on any paid plan. Commercial use is not allowed on the Free tier, and you may not resell the raw dataset directly.

Request parameters — GET /v1/bluetoothlookup

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
`companyid`Required	string	`76`	The Bluetooth SIG company identifier (decimal or hex with 0x prefix). For example, 76 or 0x4C for Apple.

Example request

1
2

curl "https://api.apiverve.com/v1/bluetoothlookup?companyid=76" \
  -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/bluetoothlookup

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": {
    "companyId": 76,
    "companyIdHex": "0x004C",
    "found": true,
    "company": "Apple, Inc."
  }
}

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
`companyId`	number	`76`	Bluetooth SIG company identifier in decimal format
`companyIdHex`	string	`"0x004C"`	Bluetooth SIG company identifier in hexadecimal format
`found`	boolean	`true`	Whether the company ID was found in database
`company`	string	`"Apple, Inc."`	Bluetooth company or manufacturer name

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	Bluetooth Company 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/bluetoothlookup

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

Resources

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

Also published for

@apiverve/bluetoothlookupnpm APIVerve.API.BluetoothCompanyLookupNuGet

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/bluetoothlookup

Install the Node.js SDK, then call the Bluetooth Company 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/bluetoothlookup

Node.js

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

Resources

npm@apiverve/bluetoothlookupThe published Node.js client, versioned and signed.GitHubapiverve/bluetoothlookup-apiSource, issues and the examples this page is built from.ReferenceBluetooth Company 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.BluetoothCompanyLookupNuGet

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

Call it from Python — GET /v1/bluetoothlookup

No SDK to install — this is a plain HTTPS call to /v1/bluetoothlookup 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/bluetoothlookup",
    headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])

Resources

Also published for

@apiverve/bluetoothlookupnpm APIVerve.API.BluetoothCompanyLookupNuGet

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/bluetoothlookup

Install the C# / .NET SDK, then call the Bluetooth Company 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.BluetoothCompanyLookup

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

Resources

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

Also published for

@apiverve/bluetoothlookupnpm

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

Call it from Go — GET /v1/bluetoothlookup

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

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

Call it from PHP — GET /v1/bluetoothlookup

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

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

Call it from Ruby — GET /v1/bluetoothlookup

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

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

Bluetooth Company Lookup API

Try it — live request, no key required

About the Bluetooth Company Lookup API

What people use it for

Ways to call it

Other ways to use Bluetooth Company Lookup

Questions.

Request parameters — GET /v1/bluetoothlookup

Required

Authentication

Response — GET /v1/bluetoothlookup

Response fields

Response headers

Errors

What a call costs — 2 credits per call

Call it from cURL — GET /v1/bluetoothlookup

Resources

Also published for

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

Resources

Also published for

Call it from Python — GET /v1/bluetoothlookup

Resources

Also published for

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

Resources

Also published for

Call it from Go — GET /v1/bluetoothlookup

Resources

Also published for

Call it from PHP — GET /v1/bluetoothlookup

Resources

Also published for

Call it from Ruby — GET /v1/bluetoothlookup

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — Bluetooth Company Lookup API

Networking

Related articles

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

Explore the catalog