MAC Address Lookup is a simple tool for looking up MAC address data. It returns the MAC address vendor, conversions, and more.
Try it — live request, no key required
No key required to try it. Get a key to use it in your app.
{
"status": "ok",
"error": null,
"data": {
// MAC Address Lookup response payload
}
}
About the MAC Address Lookup API
MAC Address Lookup works by retrieving MAC address data a predefined database and providing it in a structured format. The database is updated regularly to ensure accurate and up-to-date information.
What people use it for
- Network Security
- Use the MAC Address Lookup API to look up MAC address data for network security. Use the data to identify devices, monitor traffic, and prevent unauthorized access
- Device Management
- Manage devices by using the MAC Address Lookup API to look up MAC address data. Use the data to track devices, assign IP addresses, and troubleshoot network issues
- IT Support
- Provide IT support by using the MAC Address Lookup API to look up MAC address data. Use the data to diagnose network problems, configure devices, and optimize performance
- Network Monitoring
- Monitor networks by using the MAC Address Lookup API to look up MAC address data. Use the data to analyze traffic patterns, detect anomalies, and ensure network reliability
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
Other ways to use MAC Address Lookup
Same data, same APIVerve account, same credit balance — one key works on all of them.
What does the MAC Address Lookup API do?
How do I authenticate MAC Address Lookup API requests?
How much does the MAC Address Lookup API cost?
How fast is the MAC Address Lookup API?
What response formats does the MAC Address Lookup API support?
What HTTP method does the MAC Address Lookup API use?
Request parameters — GET /v1/macaddresslookup
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 |
|---|---|---|---|
macRequired | string | 00-B0-D0-63-C2-26 | The MAC address for which you want to get the data (e.g., 00-B0-D0-63-C2-26) |
curl "https://api.apiverve.com/v1/macaddresslookup?mac=00-B0-D0-63-C2-26" \
-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-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
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/macaddresslookup
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.
{
"status": "ok",
"error": null,
"data": {
"mac": "00:B0:D0:63:C2:26",
"isValid": true,
"vendor": "Dell Inc.",
"oui": "00B0D0",
"formats": {
"colon": "00:B0:D0:63:C2:26",
"dash": "00-B0-D0-63-C2-26",
"dot": "00.B0.D0.63.C2.26",
"raw": "00B0D063C226"
}
}
}
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 |
|---|---|---|---|
mac | string | "00:B0:D0:63:C2:26" | The MAC address in standard colon-separated format |
isValid | boolean | true | Whether the MAC address is valid and recognized |
vendorPremium | string | "Dell Inc." | Manufacturer of the device with this MAC address |
ouiPremium | string | "00B0D0" | Organizationally Unique Identifier (manufacturer code) |
formats | object | {...} | |
colon | string | "00:B0:D0:63:C2:26" | MAC address formatted with colons (00:B0:D0:63:C2:26) |
dash | string | "00-B0-D0-63-C2-26" | MAC address formatted with dashes (00-B0-D0-63-C2-26) |
dot | string | "00.B0.D0.63.C2.26" | MAC address formatted with dots (00.B0.D0.63.C2.26) |
raw | string | "00B0D063C226" | MAC address formatted without separators (00B0D063C226) |
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 cycle's allowance |
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 | MAC Address 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.
Call it from cURL — GET /v1/macaddresslookup
No SDK to install — this is a plain HTTPS call to /v1/macaddresslookup with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/macaddresslookup" \
-H "x-api-key: YOUR_API_KEY"Resources
Also published for
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/macaddresslookup
Install the Node.js SDK, then call the MAC Address Lookup API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/macaddresslookupconst res = await fetch("https://api.apiverve.com/v1/macaddresslookup", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Python — GET /v1/macaddresslookup
No SDK to install — this is a plain HTTPS call to /v1/macaddresslookup with your key in the x-api-key header. Swap in a real key and it runs as-is.
import requests
res = requests.get(
"https://api.apiverve.com/v1/macaddresslookup",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Resources
Also published for
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/macaddresslookup
Install the C# / .NET SDK, then call the MAC Address Lookup API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
dotnet add package APIVerve.API.MACAddressLookupusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/macaddresslookup");
Console.WriteLine(json);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Go — GET /v1/macaddresslookup
No SDK to install — this is a plain HTTPS call to /v1/macaddresslookup 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/macaddresslookup", 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
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from PHP — GET /v1/macaddresslookup
No SDK to install — this is a plain HTTPS call to /v1/macaddresslookup with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/macaddresslookup");
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
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Ruby — GET /v1/macaddresslookup
No SDK to install — this is a plain HTTPS call to /v1/macaddresslookup with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/macaddresslookup")
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.bodyResources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Zero-code embed — one snippet, no backend
Drop an interactive MAC Address Lookup form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.
Changelog — MAC Address Lookup API
Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog.
Networking
- Bluetooth Company Lookup
- Bot Detector
- Content Filter
- Domain and IP Pinger
- IP Blacklist Lookup
- IP Lookup
- MAC Address Lookup
- Nameservers
- Phishing Domain Checker
- TLD Lookup
- TLS Checker
- Tor Node Detector
- USB Vendor Lookup
- VPN Proxy Detector
Related articles
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