Networking mac validate
Exactnetworking_mac_validateDeterministic and authoritative — the canonical answer for this input.
Validate a 48-bit MAC address in any common separator style (colon, hyphen, dot, bare) and return the canonical colon-separated form. Processing multiple inputs? Use `networking_mac_validate_batch` to do up to 1000 in one call.
Parameters
valuestringrequiredThe MAC address to validate (any common separator).
Call it
curl -X POST https://api.snipget.ai/v1/networking/mac/validate \
-H "Authorization: Bearer sk_live_..." \
-H "Content-Type: application/json" \
-d '{"value":"AA-BB-CC-DD-EE-FF"}'The Batch tab sends up to 1000 inputs in one call via /v1/networking/mac/validate/batch.
Example response
{
"input": "AA-BB-CC-DD-EE-FF",
"is_valid": true,
"normalized": "aa:bb:cc:dd:ee:ff"
}FAQ
What does it check?
Whether a string is a valid 48-bit hardware (MAC) address, and it returns the canonical colon-separated form. It accepts any common separator style, so colons, hyphens, dots, or none all work.
Why use it instead of a quick check of my own?
Because the same MAC can be written several ways, a simple pattern check often rejects valid addresses or accepts junk. This validates the real thing and hands back one consistent form you can store and match on.
How reliable is the verdict?
It is exact and deterministic. A valid MAC always reads valid, and the normalized form is always the same for the same address.
Does it tell me the device maker?
No. It confirms the address is well-formed and normalizes it; it does not look up the manufacturer from the address prefix. That would need a separate vendor database.
What if the value is not a MAC?
Wrong-length or non-hex input returns is_valid false with a reason and confidence 0, rather than throwing an error.