Skip to content

Credentials for Moveris Meet

Get the credentials you need to integrate Moveris Meet: a bot API key for your backend, and a Moveris API key for liveness analysis and webhooks.

In plain terms

Moveris Meet uses two secrets. The bot API key lets your server start and manage meeting sessions. The Moveris API key powers the liveness checks and must be the same key that owns your webhook in the Developer Portal. Moveris provisions both for your organization—keep them on the server only.

What You Need

Bot API key

sk-bot-<key> — send as Authorization: Bearer sk-bot-<key> on session and control endpoints.

Moveris API key

Used by the hosted Meet service for analysis. Register your webhook on this same key in the Developer Portal.

Meet base URL

Public URL for your environment (for example https://meet.example.com). Provided by Moveris.

One API key for analysis and webhooks

Verdict webhooks fire on the Moveris API key configured for your Meet deployment. Do not register the webhook on a different test key unless Moveris configures it that way.

Getting credentials

  1. Create or sign in to the Moveris Developer Portal.
  2. Request Meet access from the Moveris team — they issue your bot API key and Meet base URL, and configure the analysis API key on the service.
  3. Create or select a Moveris API key in the portal (if Moveris asks you to manage it) and store it securely.
  4. Configure a webhook on that same API key — see the Webhook Setup Guide.

Go to Developer Portal

How your backend uses the bot API key

Authorization: Bearer sk-bot-<your-bot-key>

Required for POST /api/sessions and related session routes. See Quick Start and API Reference.

Keep keys secure

  • Never commit keys to version control
  • Use environment variables on your server
  • Never expose keys in client-side JavaScript or the interviewer link
  • Rotate keys with the Moveris team when needed

Next steps