UUID generate

POST /api/uuid-generate1 quota unit per call · cache hits free

Generate UUIDs over an HTTP API. v4 (random, the standard choice) or v7 (time-ordered for database-friendly insertion). Bulk generation supported.

Generates UUIDs. Two versions: - `v4` (default): 122 random bits. The standard choice when you just need a unique id. - `v7`: time-ordered. The first 48 bits encode a millisecond timestamp followed by random bits. Inserts into a sorted index in approximate insertion order — much friendlier to B-tree databases than v4. Set `count` for bulk generation. The response always includes both the canonical hyphenated form and a compact unhyphenated form.

Inputs

Name	Type	Default	Description
version	enum (v4 \| v7 \| nil)	"v4"	UUID version.
count	number (1…256)	1	How many UUIDs to emit.

Response

Modes: json. Cache: not cacheable.

Every response carries x-cache (HIT / MISS / BYPASS), x-cache-signature (stable across identical inputs), and the rate-limit headers listed below.

Quota & limits

Cost per call	1 unit against the 10,000-unit monthly quota. Cache hits are free — only cache misses decrement.
Burst limit	200 requests per rolling minute, shared across all tools.
Max request size	`1 KiB` (base64 inflates file payloads ~33% — the limit applies to the decoded bytes).
Max response size	`64 KiB`
Timeout	5s wall clock.
Rate-limit headers	`X-RateLimit-Limit`, `X-RateLimit-Remaining`, `X-RateLimit-Burst-Limit` on every response; `X-Quota-Warning` once 80% of the monthly quota is spent; `Retry-After` on 429s.

Errors

Errors are JSON with an error string; schema failures add a details object (Zod's flattened field errors).

Status	When	Body
400	Input fails the tool's schema (wrong type, missing required field, malformed base64) or the file bytes can't be parsed as the expected format.	{ "error": "invalid inputs", "details": { "fieldErrors": { … } } }
401	Missing or invalid X-Api-Key / X-Account-Id headers (or no session when called from the browser).	{ "error": "unauthorized" }
404	Unknown tool id, or calling /api/* on the website hostname instead of api.xtract.bot.	{ "error": "not found" }
413	Request body over the tool's max request size, or an image header declaring more megapixels than the tool's pixel budget.	{ "error": "…exceeds maxRequestBytes…" }
415	Content-Type isn't application/json on the json-body transport.	{ "error": "unsupported content-type; expected application/json" }
429	Monthly quota or the 200/min burst limit exhausted. Check Retry-After and the X-RateLimit-* headers.	{ "error": "monthly quota exceeded", "monthRemaining": 0, … }
5xx	Conversion engine failure. Safe to retry; if it persists, the input is hitting a bug — please report it.	{ "error": "…" }

Code samples

Built from the single-v4 example.


curl -X POST https://api.xtract.bot/api/uuid-generate \
  -H "Content-Type: application/json" \
  -H "Accept: application/json" \
  -H "X-Account-Id: $XTRACT_ACCOUNT_ID" \
  -H "X-Api-Key: $XTRACT_API_KEY" \
  -d '{
  "version": "v4",
  "count": 1
}'