Meeting Liveness Bot — Quick Start¶
Get a Meeting Liveness Bot 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 the Meeting Liveness Bot.
Bot base URL¶
Public URL of your deployed bot (e.g. https://bot.example.com).
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¶
- Sign in to the Moveris Developer Portal.
- Add an HTTPS webhook URL for your Moveris API key.
- 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"
}'
{
"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.
Step 3: Share the Interviewer Link (Optional)¶
If a human observer should watch live results, send them:
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": "liveness.result",
"session_id": "a3f7c291-...",
"participant_id": "p1",
"participant_name": "Jane Doe",
"verdict": "live",
"score": 88,
"confidence": 93,
"is_live": true,
"processing_ms": 1240,
"frame_urls": [
"https://storage.example.com/frames/session/.../frame-0.png?token=..."
]
}
Use session_id together with your stored sessionId from Step 2 to correlate results. See Session Lifecycle for the deterministic UUID mapping.
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¶
- How It Works — Architecture, auth, and notification channels
- Integration Guide — End-to-end flow, error handling, and production checklist
- Session Lifecycle — Bot status transitions and re-scan behavior
- API Reference — All bot endpoints and response fields