What problem does it solve? Server-side Velt integrations fail with 401 errors, expired tokens, and webhook signature mismatches when developers miss the required header contract, generate JWTs on the client, or bind to outdated response shapes. This Skill provides verified rules for every Velt REST API v2 endpoint, JWT token flow, and webhook version. ## Core Features & Use Cases - Authentication Contract: Enforces the correct header pair for every call — x-velt-api-key + x-velt-auth-token for api-key-level endpoints, x-velt-workspace-id + x-velt-workspace-auth-token for workspace-level endpoints — plus server-side JWT generation with 48-hour expiry and refresh handling. - Full REST CRUD Coverage: Documents request and response shapes for comment annotations, comments, users (including GDPR export/delete), documents, organizations, folders, notifications, activity logs, CRDT data, agent executions, and Memory endpoints. - Webhook Management: Covers v1 webhook setup, v2/Svix enterprise webhooks with retries and signature verification, and programmatic advanced-webhook endpoint management with signing secrets. - Use Case: When building a Next.js backend that provisions Velt documents, generates JWT tokens for frontend users, and receives comment webhooks, the agent applies these rules to produce correct endpoint paths, headers, and payload envelopes on the first attempt. ## Quick Start Ask the agent to generate a server-side Next.js API route that creates a Velt JWT token for a user and lists comment annotations for a document using the REST API v2.
