Identifiers validate uuid
Exactidentifiers_validate_uuidDeterministic and authoritative — the canonical answer for this input.
Parse and normalize a UUID, detecting its RFC 4122 version (1-8) and variant. Accepts hyphenated canonical, {braced}, urn:uuid:, or raw 32-hex. Returns every common rendering plus is_nil / is_max flags. Processing multiple inputs? Use `identifiers_validate_uuid_batch` to do up to 1000 in one call.
Parameters
valuestringrequiredThe identifier string to validate.
Call it
curl -X POST https://api.snipget.ai/v1/identifiers/validate/uuid \
-H "Authorization: Bearer sk_live_..." \
-H "Content-Type: application/json" \
-d '{"value":"550e8400-e29b-41d4-a716-446655440000"}'The Batch tab sends up to 1000 inputs in one call via /v1/identifiers/validate/uuid/batch.
Example response
{
"input": "550e8400-e29b-41d4-a716-446655440000",
"is_valid": true,
"normalized": "550e8400-e29b-41d4-a716-446655440000",
"compact": "550e8400e29b41d4a716446655440000",
"hyphenated": "550e8400-e29b-41d4-a716-446655440000",
"braced": "{550e8400-e29b-41d4-a716-446655440000}",
"urn": "urn:uuid:550e8400-e29b-41d4-a716-446655440000",
"version": 4,
"variant": "RFC 4122",
"is_nil": false,
"is_max": false
}FAQ
What does it return?
It confirms a UUID is well-formed and gives you every common rendering (plain, braced, urn, compact) plus its version number and variant, so you can store one consistent form.
What forms of UUID can I paste?
The dashed canonical form, a {braced} form, a urn:uuid: prefixed form, or raw 32 hex characters. They are all normalized to the same output.
Does it generate a new UUID?
No. This only inspects and normalizes a UUID you already have. It does not create one.
How dependable is the check?
It is exact and deterministic. A valid UUID always validates, and the version and variant are read straight from the value.
What are the is_nil and is_max flags?
They mark the two special all-zeros and all-Fs UUIDs. Those are structurally valid but carry no version, so version comes back null.