API REFERENCE · GET · STABLE

MAC Vendor Search API — /api/v1/security/mac-vendor

Inverse of `/security/mac-info`. Given a vendor name, returns every OUI prefix on record for that organization.

01 · OVERVIEW

What MAC Vendor Search does

Inverse of `/security/mac-info`. Given a vendor name, returns every OUI prefix on record for that organization.

  • Method GET
  • Path /api/v1/security/mac-vendor
  • Stability STABLE
  • Version v2026-05-15
  • Summary Reverse lookup: find all OUI prefixes assigned to a vendor.
02 · PARAMETERS

Request parameters

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

  • vendor (required) — string Vendor name. Partial matches supported (case-insensitive).
03 · RESPONSE

Response schema

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

  • data.mac — integer Total OUIs matching the vendor query.
  • data.address[].prefix — string OUI prefix (e.g. `90-88-55`).
  • data.address[].organization — string Registered org for this OUI.
  • data.address[].country — string Country code.
04 · EXAMPLE

Example response

Truncated but representative example for a real lookup:

Sample response
{
  "success": true,
  "data": {
    "mac": 1283,
    "address": [
      {
        "prefix": "90-88-55",
        "organization": "Cisco Systems, Inc",
        "country": "US"
      },
      {
        "prefix": "08-F1-B3",
        "organization": "Cisco Meraki",
        "country": "US"
      }
    ]
  }
}
05 · ERRORS

Error codes

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

  • 404 NO_VENDOR_MATCH No OUI assignments match the query.
06 · BEST PRACTICES

Implementation tips

Patterns we recommend when integrating this endpoint:

  • Use longer vendor strings for tighter matches — `cis` returns hundreds of unrelated orgs.