MeetCapture API Reference

Access your meeting sessions, transcripts, and recordings programmatically. The MeetCapture API is built on Supabase and supports both REST and Edge Function endpoints.

MeetCapture supports API keys for server-side Edge Function calls and Supabase Auth JWTs for direct PostgREST table access.

curl -H "x-api-key: mc_live_your_key_here" \
  "https://xrhwfuquudleamotznzx.supabase.co/functions/v1/mc-api-sessions?limit=10"

curl -H "Authorization: Bearer eyJhbGciOiJIUzI1NiIs..." \
  -H "apikey: YOUR_SUPABASE_ANON_KEY" \
  https://xrhwfuquudleamotznzx.supabase.co/rest/v1/mc_sessions

MeetCapture exposes standard REST endpoints via Supabase PostgREST for authenticated Supabase users. For API-key access, use the Edge Function endpoints below.

Sessions

A session represents a single meeting capture. It contains metadata about the platform, timing, and status.

List all sessions

curl -X GET \
  "https://xrhwfuquudleamotznzx.supabase.co/functions/v1/mc-api-sessions?limit=10" \
  -H "x-api-key: mc_live_your_key"

Transcripts

Transcripts contain the full text and individual segments (with timestamps and speakers) for each session.

Get transcript with segments

# SESSION_UUID is the mc_sessions.id value.
curl -X GET \
  "https://xrhwfuquudleamotznzx.supabase.co/functions/v1/mc-api-sessions?id=SESSION_UUID" \
  -H "x-api-key: mc_live_your_key"

Recordings

Access audio and video recording metadata. Files are stored in Supabase Storage and can be downloaded via signed URLs.

# The detail response includes recordings, transcript, and segments.
curl -X GET \
  "https://xrhwfuquudleamotznzx.supabase.co/functions/v1/mc-api-sessions?id=SESSION_UUID" \
  -H "x-api-key: mc_live_your_key"

Server-side edge functions handle complex operations like upload token generation and webhook delivery. These run on Supabase Edge (Deno Deploy).

# List sessions with an API key
curl "https://xrhwfuquudleamotznzx.supabase.co/functions/v1/mc-api-sessions?limit=10&platform=zoom" \
  -H "x-api-key: mc_live_your_key"

# Get one session with transcript segments
curl "https://xrhwfuquudleamotznzx.supabase.co/functions/v1/mc-api-sessions?id=SESSION_UUID" \
  -H "Authorization: Bearer USER_SUPABASE_JWT"

curl -X POST \
  "https://xrhwfuquudleamotznzx.supabase.co/functions/v1/mc-api-upload-token" \
  -H "x-api-key: mc_live_your_key" \
  -H "Content-Type: application/json" \
  -d '{"session_id": "SESSION_UUID", "file_name": "recording.wav", "content_type": "audio/wav"}'

{
  "event": "session.completed",
  "session_id": "abc123",
  "timestamp": "2026-04-04T12:00:00Z"
}

Register webhook endpoints from your dashboard to receive real-time notifications when events occur. All payloads are signed with HMAC-SHA256 using your endpoint secret.

Available Events

Example Payload

{
  "event": "session.completed",
  "timestamp": "2026-04-04T12:30:00Z",
  "data": {
    "session_id": "550e8400-e29b-41d4-a716-446655440000",
    "platform": "zoom",
    "title": "Weekly Team Standup",
    "duration_seconds": 1800,
    "transcript_segment_count": 42,
    "recording_count": 1
  }
}

Verifying Signatures

Each webhook request includes a X-MeetCapture-Signature header. Verify it with HMAC-SHA256 using your endpoint secret.

import crypto from "crypto";

function verifyWebhook(payload, signature, secret) {
  const expected = crypto
    .createHmac("sha256", secret)
    .update(payload)
    .digest("hex");

  return crypto.timingSafeEqual(
    Buffer.from(signature),
    Buffer.from(expected)
  );
}

// In your Express handler:
app.post("/webhooks/meetcapture", (req, res) => {
  const sig = req.headers["x-meetcapture-signature"];
  const valid = verifyWebhook(JSON.stringify(req.body), sig, WEBHOOK_SECRET);

  if (!valid) return res.status(401).send("Invalid signature");
  // Process the event...
  res.sendStatus(200);
});

Error Handling

The API uses standard HTTP status codes. Error responses include a message explaining what went wrong.

{
  "message": "Invalid API key",
  "code": "INVALID_API_KEY",
  "hint": "Check that your API key is active and correctly formatted"
}