MAC Address Lookup API — /api/v1/security/mac-info

Accepts colon, dash, or dotted MAC notation. Returns IEEE-registered vendor name, address, and IANA category. Minimum input is a 6-character OUI prefix.

• Method GET
• Path /api/v1/security/mac-info
• Stability STABLE
• Version v2026-05-15
• Summary Resolve a MAC address (OUI) to its vendor.

Pass these as query-string parameters (or, where indicated, in the request headers). Required params marked required.

• mac (required) — string MAC or OUI. Accepts `00:1A:79`, `00-1A-79-A8-30-00`, `001A.79A8.3000`, etc.

All successful responses follow the standard `{ success: true, data: {...} }` envelope. Notable fields on the data object for this endpoint:

• data.vendor.org — string Registered organization.
• data.vendor.address — object Street, city, state, postalCode, country.
• data.vendor.base16 — string OUI in base16 (e.g. `001A79`).
• data.category — object IANA category, usage, and notes.

Truncated but representative example for a real lookup:

{
  "success": true,
  "data": {
    "vendor": {
      "org": "TELECOMUNICATION TECHNOLOGIES LTD.",
      "address": {
        "street": "4D ZHUKOVA BLV.",
        "city": "ODESSA",
        "postalCode": "65121",
        "country": "UA"
      },
      "base16": "001A79"
    },
    "category": {
      "category": "IANA 64-bit MAC Addresses",
      "usage": "Reserved"
    }
  }
}

Errors return HTTP status codes paired with stable machine-readable codes. Match on the code field rather than the human-readable message.

• 400 INVALID_MAC Couldn't parse the input as a MAC / OUI.

Patterns we recommend when integrating this endpoint:

• Strip separators client-side before calling — the parser handles them but it's one less round-trip.

• Why is the vendor empty for some MACs? Randomized / locally-administered MACs (typical on iOS/Android Wi-Fi) have no IEEE registration.