Publish a link template
Creates the template and its public link in one step — the link starts active (unless status: "paused" is sent) at /l/{org}/{slug}. The published snapshot starts at version: 1 (GET-83); every verification minted from the link records the version it ran against.
Side effects: none beyond the write — publishing does NOT mint verifications or send notifications.
Idempotency: slugs are unique per tenant; a re-publish of a live slug returns 409 slug_taken.
Authorizations
Dashboard / operator session cookie. Set by /v1/auth/google/callback after Google OAuth, JWT signed with the rotating rial-platform/session-signing HMAC. Read on every request the SPA makes with credentials: include. Browser-only — server-to-server callers use bearerApiKey instead.
Body
2 - 40^[a-z0-9]+(?:-[a-z0-9]+)*$1 - 801- Option 1
- Option 2
- Option 3
capture, audit, hybrid 60 <= x <= 86400draft, active 1 - 3001 - 2001 - 6 elements1 - 401 <= x <= 100001 <= x <= 10000002 - 40^[a-z0-9]+(?:-[a-z0-9]+)*$Response
Template published. version is always 1 on create.
capture, audit, hybrid active, paused x >= 1