Skip to content

Changelog

All notable changes to Moveris Meet, the SDK, and webhooks that affect integrators are documented here.

In plain terms

This page lists Meet, SDK, and webhook features, changes, and fixes relevant to teams integrating sessions, in-app capture, and callbacks. Check it when upgrading your integration or troubleshooting unexpected behavior.

Portal changelog

Entries cover the products in the documentation portal: Moveris Meet, the SDK, and the webhooks used to receive verdicts. REST API and MCP notes remain in git history and will return when those products are documented again.

2026

[SDK 4.1.3] - 2026-09-24

Fixed

  • SDK — browser bundles — @moveris/react 4.1.3. Strict browser bundlers such as Next.js Turbopack load the React SDK. They no longer fail with Dynamic require of 'events' is not supported. Install it with @moveris/shared 4.1.2. @moveris/react-native 4.1.2 tracks that same @moveris/shared release. See Installation — Version Compatibility.

[2.14.0] - 2026-09-18

Changed

  • Moveris Meet — Mixed V3.1.1 catalog — Session create and verification history use the three production aliases: mixed-30-v3_1_1 (default, 30 frames), mixed-60-v3_1_1 (60), and mixed-120-v3_1_1 (120). Mixed V2 aliases are rejected. Pin model explicitly. See Overview — Models.
  • Moveris Meet — duplicate session create — A repeated POST /api/sessions for the same meeting and owner returns the existing active session instead of starting a second bot.
  • Moveris Meet — accumulation timeout — Scan timeout scales with the model's frame count and whether face or background gating is on. A 30-frame scan with no gates still uses about 30 seconds; 60- and 120-frame scans get more time.
  • Moveris Meet — org-scoped sessions — GET / DELETE / SSE for a session from another organization return 404.
  • Moveris Meet — M2M billing — Machine-to-machine sessions run against the caller's sk-bot-* key. An unlinked bot key returns 403 and does not create a session.

[SDK 4.1.0] - 2026-09-15

Changed

  • SDK — consecutive capture — @moveris/shared, @moveris/react, and @moveris/react-native 4.1.0. Frames are submitted as one uninterrupted sequence. A quality or detection failure discards the partial run and fires onSequenceReset on useSmartFrameCapture; LivenessView calls restartCapture() on useLiveness / useLivenessV2. Sequential streaming no longer waits on in-flight requests between frames.
  • SDK — frame geometry — Full frames keep the camera aspect ratio and downscale to fit 1280×720 (720×1280 portrait), with no letterboxing and no upscaling. fast-check sends measured fps (fps_source: 'measured') plus metadata.frame_format and resolution. New exports: detectImageFormat, getPngDimensions.

[SDK 4.0.0] - 2026-09-15

Changed

  • SDK — Mixed V3.1.1 only — @moveris/shared, @moveris/react, and @moveris/react-native 4.0.0. FastCheckModel and MODEL_CONFIGS list mixed-30-v3_1_1, mixed-60-v3_1_1, and mixed-120-v3_1_1. VALID_FRAME_COUNTS is [30, 60, 120]. ModelVersion is 'latest' | 'v3_1_1'. The default model is mixed-30-v3_1_1 (30 frames), exported as DEFAULT_MODEL. Mixed V2, V3, and V3.1 ids no longer type-check and are rejected by the API. See Models.

[2.13.0] - 2026-07-15

Added

  • Moveris Meet — frame quality gating — Before frames enter the accumulator, Meet runs a gate-and-reset quality pipeline (blur, brightness, and optionally face geometry / pose). A rejected frame resets that participant's buffer so the model still receives consecutive frames. The session SSE stream adds frame-quality-rejected (throttled to about once per second per participant) with participantId, participantName, reason, framesCollected, and framesRequired so M2M clients can surface interviewer guidance. See Integration Guide — Frame quality gating and API Reference — Session Events.

Fixed

  • Moveris Meet — stale session cleanup — When a session expires, Meet now leaves the meeting, broadcasts session-status with fatal, and unlocks the client form. SSE onerror that receives 404 for the session also marks the session fatal so the UI does not stay stuck in scanning.

[2.12.0] - 2026-06-26

Added

  • Moveris Meet — V3.1.1 models — Session create and verification history support the mixed-*-v3_1_1 aliases, so meeting sessions can target the latest model generation.

Changed

  • Moveris Meet — H.264 video pipeline — Meet now ingests each participant's video as an H.264 stream and extracts frames with FFmpeg, instead of receiving one PNG per frame. End-to-end verdict latency drops from roughly 20 seconds to about 9 seconds. Frames are delivered at native capture resolution and as consecutive frames (no frame skipping), matching how the liveness models are trained. No API changes — session endpoints, SSE streams, and webhook payloads are unchanged.

[2.11.0] - 2026-06-22

Added

  • Moveris Meet — targeted participant scanning — POST /api/sessions now accepts optional targetParticipantNames and excludeParticipantNames (arrays of display names). When targetParticipantNames is set, Meet scans only matched participants; excludeParticipantNames skips named people (for example interviewers or hosts). Name matching is fuzzy (typos, reordered names, partial names). Matched participants are pinned and analyzed during active speech. The SSE stream adds participant-stage and participant-matched events for real-time UI. See Integration Guide — Targeted participant scanning.

[2.8.0] - 2026-06-08

Added

  • Moveris Meet — Concurrent sessions (isolated per-session handlers with scoped WebSocket routing); manual per-participant scan in the interviewer UI (explicit trigger instead of auto-accumulation); full mixed-*-v3_1 model support in scanner and history filters.

Changed

  • Webhook metadata — Fast-check webhook payloads now forward client metadata as tenant_metadata consistently. Meet session analysis uses the same delivery path—see Webhook Setup Guide.

Fixed

  • Moveris Meet — Fresh Moveris session_id on re-scan to avoid API cache hits; bot_session_id in request metadata for webhook clustering.

[2.3.0] - 2026-04-02

Added

  • Webhook delivery logs — payload echo and filters — Delivery log API responses now include request_body (the JSON body Moveris attempted to deliver). You can filter logs by event_type (e.g. verification.completed, verification.failed) and by model. The Portal Webhook / delivery views add filtering and a detail drawer for each attempt. See Webhook Setup Guide.

[2.2.0] - 2026-04-01

Added

  • verification.failed webhook — In the Developer Portal you can subscribe to a second event type. Moveris sends it when analysis fails after authentication and request validation. The JSON body keeps the same top-level shape as verification.completed (event, session_id, timestamp, data); for failures, data includes error, model, input_source, processing_ms, and frames_processed (no verdict). The X-Webhook-Event header is verification.failed. Configure which events each webhook receives in the Portal (completed only, failed only, or both). Signing with your webhook secret works the same as for completed events. See Webhook Setup Guide and Integration Guide.

Fixed

  • Webhook delivery logging — Failure-path deliveries no longer hit invalid null constraints or missing session linkage when emitting verification.failed.

[1.3.0] - 2026-02-24

Added

  • Webhook delivery logs — View delivery history and status of webhooks in the Developer Portal. Helps debug failed deliveries and monitor verification callbacks. See Webhook Setup Guide.

How to Read This Changelog

  • Added - New features
  • Changed - Changes to existing functionality
  • Deprecated - Features that will be removed in future versions
  • Removed - Features that have been removed
  • Fixed - Bug fixes
  • Security - Security-related changes