Re-invite Bot

Overview

Use this endpoint to ask the SeaMeet bot to join a meeting after the initial auto-join did not run, or after a meeting has already ended and you want a fresh recording session against the same Google Meet URL.

Typical use cases:

• A scheduled meeting started but no bot joined (e.g., the calendar event was created late or the original auto-dispatch was skipped). Call the endpoint to dispatch the bot right now.
• A meeting has already finished (OFFLINE) and you want to reuse the same meeting record for a follow-up recording on the same Meet URL. Call with force_restart=true to reset it back to INITIAL and dispatch the bot.

The endpoint enforces at most one bot per (Meet URL, workspace). Calling it multiple times while a dispatch is already in flight will return a conflict rather than spawning a second bot.

This endpoint only supports Google Meet meetings. MS Teams and Zoom meetings will be rejected with HTTP 400 (code 12102).

Authorization: API Key

All requests must include a valid API key issued from your workspace in the Authorization header as a Bearer token. The calling user must have the Owner or Manager role on the target workspace; lower roles are rejected.

1. Generate Your API Key

Currently the only UI to get an API key is through SeaX.

• Go to Workspace → API Key tab.
• Click Add New Key and check seameet as the scope.
• Copy the key and keep it safe. This key is required in the Authorization header for all requests.

API Specification

Re-invite Bot

POST /api/v1/public/meeting/{workspace_id}/meetings/{meeting_id}/reinvite_bot

Dispatch the SeaMeet bot for a meeting in your workspace.

Behavior by meeting status

The force_restart=true reset preserves the meeting’s configuration (language, participants, transcriptions, NLP results, etc.) and only flips the runtime state fields (status, start_time, end_time, duration, flag) so the existing meeting can host a new bot session.

Example

Re-invite the bot to a meeting that is still INITIAL:

curl -X 'POST' \
  'https://meet.seasalt.ai/seameet-api/api/v1/public/meeting/<workspace_id>/meetings/<meeting_id>/reinvite_bot' \
  -H 'accept: application/json' \
  -H 'Authorization: Bearer <your_api_key>' \
  -H 'Content-Type: application/json' \
  -d '{}'

Restart a meeting that has already ended (OFFLINE) and dispatch a fresh bot:

curl -X 'POST' \
  'https://meet.seasalt.ai/seameet-api/api/v1/public/meeting/<workspace_id>/meetings/<meeting_id>/reinvite_bot' \
  -H 'accept: application/json' \
  -H 'Authorization: Bearer <your_api_key>' \
  -H 'Content-Type: application/json' \
  -d '{"force_restart": true}'

Response Status 202

The bot dispatch has been accepted. The bot will join the Google Meet shortly; this endpoint returns as soon as the dispatch is enqueued, not when the bot has actually joined.

{
  "meeting_id": "2b342a6e177d4b139638bc16bd312291",
  "status": "INITIAL",
  "action": "dispatched",
  "dispatched_at": "2026-05-21T03:42:11.482"
}

Error Responses

All error responses follow the standard envelope:

{
  "detail": "Meeting <meeting_id> is OFFLINE. Pass force_restart=true to restart",
  "code": 12106,
  "parameters": { "meeting_id": "2b342a6e177d4b139638bc16bd312291" }
}