Skip to content

Moveris Meet — Quick Start

Get a Moveris Meet session running from your backend in a few steps: credentials, webhook setup, create a session, and receive your first verdict.

In plain terms

You need two keys from Moveris (a bot key and an API key), a webhook URL, and a meeting link. Your server calls one endpoint to start the bot; Moveris notifies you when each participant is analyzed.

Prerequisites

Bot API key

sk-bot-<key> — authenticates your backend to Moveris Meet.

Moveris API key

Used by the bot for analysis. Configured in the bot or by Moveris staff.

Bot base URL

Public URL of your deployed bot (e.g. https://bot.example.com).

Webhook URL

HTTPS endpoint on your server for verification.completed events.

Webhook first

Configure your webhook in the Developer Portal before your first live session. Results are delivered asynchronously—you should not rely on polling alone in production.

Flow Overview

flowchart LR
    A[Configure webhook] --> B[POST /api/sessions]
    B --> C[Share interview link optional]
    B --> D[Bot joins meeting]
    D --> E[Webhook per participant]
    E --> F[DELETE session optional]

Step 1: Configure Your Webhook

  1. Sign in to the Moveris Developer Portal.
  2. Add an HTTPS webhook URL for your Moveris API key.
  3. Copy and store the webhook secret for signature verification.

See the Webhook Setup Guide for screenshots and step-by-step instructions.

Step 2: Create a Session

Call the bot from your backend before the meeting starts (or as it begins):

# Create a bot session for a video meeting
curl -X POST "https://<bot-url>/api/sessions" \
  -H "Authorization: Bearer sk-bot-<your-bot-key>" \
  -H "Content-Type: application/json" \
  -d '{
    "meetingUrl": "https://meet.google.com/abc-defg-hij",
    "model": "mixed-10-v3_1"
  }'

Response

{
  "sessionId": "550e8400-e29b-41d4-a716-446655440000",
  "botId": "bot_abc123",
  "status": "bot_created",
  "interviewToken": "eyJzZXNzaW9uSWQiOiI1NTBlODQwMC4uLiJ9.abc123sig",
  "message": "Bot is being created and will join the meeting shortly"
}

Save sessionId for correlation. Optionally save interviewToken for the read-only interviewer view.

If a human observer should watch live results, send them:

https://<bot-url>/interview/<interviewToken>

No login is required. The link is valid for 24 hours.

Step 4: Receive Webhook Results

When each participant's analysis completes, Moveris sends an HTTP POST to your webhook URL. Handle the payload on your server:

{
  "event": "verification.completed",
  "session_id": "a3f7c291-8b2e-5c1d-9f0a-1b2c3d4e5f6a",
  "timestamp": "2026-06-01T15:26:42.123456Z",
  "data": {
    "verdict": "live",
    "score": 88.0,
    "real_score": 0.88,
    "confidence": 0.93,
    "processing_ms": 1240,
    "frames_processed": 10
  }
}

No participant_id in the payload

The webhook body does not include participant_id or participant_name—session_id is how you correlate the result back to a participant. Use session_id together with your stored sessionId from Step 2. See Session Lifecycle for the deterministic UUID mapping and Integration Guide for the full payload shape.

Step 5: Stop the Session (Optional)

To end the bot before the meeting finishes:

curl -X DELETE "https://<bot-url>/api/sessions/<sessionId>" \
  -H "Authorization: Bearer sk-bot-<your-bot-key>"

Next Steps