Networking ip validate
Exactnetworking_ip_validateDeterministic and authoritative — the canonical answer for this input.
Validate an IPv4 or IPv6 address. Returns is_valid, the version (4 or 6), and the normalized (compressed) form. Processing multiple inputs? Use `networking_ip_validate_batch` to do up to 1000 in one call.
Parameters
valuestringrequiredThe IP address to validate (v4 or v6).
Call it
curl -X POST https://api.snipget.ai/v1/networking/ip/validate \
-H "Authorization: Bearer sk_live_..." \
-H "Content-Type: application/json" \
-d '{"value":"192.168.1.1"}'The Batch tab sends up to 1000 inputs in one call via /v1/networking/ip/validate/batch.
Example response
{
"input": "192.168.1.1",
"is_valid": true,
"version": 4,
"normalized": "192.168.1.1"
}FAQ
What does it check?
Whether a string is a genuine IPv4 or IPv6 address, which version it is, and the tidy normalized form. It catches things like 999.1.1.1 or a stray space that look like an IP but are not.
Why not just check it with a pattern myself?
Hand-written checks miss real cases, especially the many valid shorthand forms an IPv6 address can take. This uses the standard address rules, so both versions are validated correctly every time.
What is the normalized form for?
It is the canonical, compressed version of the address. Storing that form means the same address always looks identical when you compare or de-duplicate.
How reliable is the verdict?
It is exact and deterministic. A valid address always reads valid, and the same input always returns the same result.
What happens with an invalid address?
You get is_valid false with the reason and confidence 0, not an error, so you can flag the bad rows.