Changelog

Compatibility promise

• Within /api/v1 we only make additive changes: new endpoints, new optional fields, new event types, new error codes.
• Breaking changes ship as a new version (/api/v2) and the previous version keeps working for at least 6 months after the announcement here.
• Webhook payloads may gain fields; ignore fields you don't know. Subscribing to * also delivers event types added later.
• @vmeet/embed follows semantic versioning; /sdk/vmeet-embed.js always serves the latest 1.x.

October 2026 — VMeet is now GurukulLive

The product was renamed from VMeet to GurukulLive and is served from gurukullive.trinetraailabs.in; the old host keeps working as an alias. Nothing changes for integrations: API paths, vmk_ keys, the VMeet-Signature / VMeet-Webhook-* headers, @vmeet/embed, /sdk/vmeet-embed.js, window.VMeet and the source: 'vmeet' message protocol keep their names.

• @vmeet/embed 1.0.1 — the default iframe title is now “GurukulLive meeting”.
• If you allow-list the room origin (event.origin, CSP frame-src, WebView host checks), add gurukullive.trinetraailabs.in.

October 2026 — v1.0

The first public release of the developer platform.

• Public REST API (/api/v1/public): users (with bulk import), classes, courses, enrollments, meetings, live rosters, recordings, attendance (JSON/CSV) and usage. Reference
• API keys with scopes, expiry, IP allowlists and per-key rate limits, managed in Settings → API keys.
• Join links: single-use, short-lived links that let your users into a meeting without a GurukulLive login; meeting-scoped sessions; waiting-room support. Guide
• Embedded room (/embed/meeting/:slug) and recording player (/embed/recording/:id), with the origin-checked postMessage protocol. Guide
• @vmeet/embed 1.0.0 — JS SDK (ESM + CDN build), ~3 KB gzipped, zero dependencies.
• Webhooks v1: 22 event types, HMAC-SHA256 signatures with secret rotation, retries for ~2 days, delivery log and redelivery. Guide
• OpenAPI 3.1 document at /api/v1/public/openapi.json.