Generate UUIDs

Generated

generators_uuid

Valid by construction but non-reproducible — a fresh call returns new values.

Generate UUIDs. version=1 (time+node), 4 (random, default), 5 (name-based — pass name + namespace dns/url/oid/x500), or 7 (time-ordered). Use count for many in one call. Non-reproducible unless seeded (seeding is for tests only — insecure).

Parameters

versionintegeroptional

UUID version: 1, 4 (default), 5, or 7.

countintegeroptional

How many to generate.

namespacestringoptional

v5 namespace: dns/url/oid/x500 or a UUID string.

namestringoptional

v5 name (required for version 5).

seedintegeroptional

Reproducible (insecure) output for testing.

Call it

curl -X POST https://api.snipget.ai/v1/generators/uuid \
  -H "Authorization: Bearer sk_live_..." \
  -H "Content-Type: application/json" \
  -d '{"version":4,"count":3}'

FAQ

Why not just have the AI write a UUID?

An AI can produce something that looks like a UUID but is not valid, or repeats one it used before. This builds real UUIDs from a proper random source so they are correctly formatted and effectively never collide.

Which version should I pick?

Version 4 (the default) is plain random and the safe everyday choice. Version 7 is also random but time-ordered, so the IDs sort by when they were made. Version 1 is time plus machine. Version 5 is name-based: the same name and namespace always give the same UUID.

Will I get the same UUID again?

For versions 1, 4, and 7, no. Each call returns fresh values you cannot reproduce, so save them when you create them. Version 5 is the exception: it is deterministic, so the same name and namespace always return the same value.

What does version 5 need?

A name (required), plus a namespace, which is dns, url, oid, x500, or your own UUID. Together they always map to the same UUID, which is handy when you want a stable ID derived from a string like a domain or URL.

What happens with a bad request?

Bad parameters, such as an unsupported version or a version 5 call missing its name, are request mistakes: rejected with an INVALID_INPUT error naming the problem, not billed. Read the message and fix the request.

Full API reference (schemas, error codes) →