Open A3.Meet

API for developers

A REST API with an OpenAPI spec, webhooks, an Embed SDK and an MCP server for AI agents. Build video meetings into your own processes and applications instead of switching between systems.

Authentication

A service key is issued in the “API and webhooks” section of the app or in A3.ID and passed in the API-KEY header. The key is bound to the organization and a set of permissions, and each key has a request log. The response language is set with the Language-Code header.

Sample request
POST /api/v1/meetings
API-KEY: sk_live_********
Language-Code: EN
Content-Type: application/json

{
  "title": "Board of directors",
  "startsAt": "2026-11-02T09:00:00+05:00",
  "accessType": "OrganizationOnly"
}

API methods

  • Rooms and meetings

    Creating and updating meetings, scheduling, recurring series, room state

  • Participants and access

    Invitations, participant list, roles, lobby, moderation

  • Recordings and transcripts

    Recording list, downloads, transcripts, content search that respects permissions

  • Minutes and action items

    Minutes, approval and A3.EDM signing status, action items with deadlines

  • Webinars and broadcasts

    Registrations, polls, speaker Q&A, webinar and broadcast reports

  • Organization

    Departments, employees, licenses and plan usage

Webhooks

Sixteen event types. Every request is signed, failed deliveries are retried with increasing delay, and the log shows response codes and lets you resend an event.

  • Meeting created, updated, canceled, started, ended
  • Participant joined, left, removed
  • Recording started, ready, deleted
  • Transcript ready
  • Minutes generated and approved
  • Quota exceeded

Embed SDK

  • The meeting client inside your app through an iframe and a JavaScript interface
  • Commands from your app: microphone, camera, screen sharing, leave
  • Real-time events: join, leave, microphone, camera, screen sharing, participant list
  • A short-lived embed token bound to your site’s address

MCP server

  • The ecosystem AI agent gets access to meetings, transcripts, minutes, recordings and action items
  • The agent acts within the permissions of the user it works on behalf of
  • The agent creates and reschedules meetings through the same interface as a person

Access and limits

  • A developer sandbox before going to production
  • Rate limiting and quotas by plan
  • Public API: limited on Business, full on Enterprise

Need API access?

Tell us about your integration scenario, and we will pick a plan and issue a sandbox key.

API documentationDiscuss implementation