Product Updates
Fedor Zhilkin
Jun 9, 2025
·
Updated on
Jul 9, 2026
Mymeet.ai provides a REST API for integrating meeting data into external systems. Through the API, you can programmatically launch meeting recordings, retrieve transcripts and reports, and manage meetings from your own code — without any manual actions in the interface.
This article is an overview of the API's capabilities and examples of basic requests with a breakdown of each part. Full technical documentation is linked at the end.
What the Mymeet.ai REST API Is and Why You Need It
A REST API is a set of addresses (endpoints) that external applications use to communicate with Mymeet.ai. Instead of opening the interface and clicking buttons, your code sends a request — and the service returns data or performs an action. This is useful when meeting data needs to flow into other systems automatically: a CRM, a knowledge base, analytics, or your team's own tool.
Who Needs the Mymeet.ai REST API
The API is useful in three core scenarios. Developers — to embed meeting data into their own systems, automatically trigger recording, or export reports. Technical teams and analysts — to collect data across all workspace meetings and build analytics on top. Teams with custom requirements — when ready-made integrations don't fit and you need full control.
How the REST API Differs from Mymeet.ai's MCP Integration
The API requires writing code: you define the logic, send requests, and handle responses. It's flexible, but requires technical knowledge. MCP (Model Context Protocol) is a different approach: you connect an AI agent (Claude, Cursor, ChatGPT), and it queries meeting data for you in plain language. No code needed. If the task is automation and system integration, use the API. If you want to work with meeting data through an AI assistant — read the Mymeet.ai MCP guide.
Authentication via Mymeet.ai API Key
Every request to the API must include an API key — otherwise the service will return an error and refuse to execute the action. The key proves the request comes from you and determines which data it can access.
Where to Get Your API Key
The API key is in your user settings — find the "API Key" section. The key is already created; nothing needs to be activated. Open the page, click "Copy" — the full value is copied to your clipboard. This is the value you substitute into all requests in place of your_key.
On the Free plan, the page is accessible and the key is partially visible, but the "Copy" button is unavailable — the API only works on paid plans. You can regenerate the key at any time: the old one stops working instantly.
[Get API Key]
How to Pass the API Key in Requests
The key is passed in a special header with every request — a line that travels alongside the request and carries service information. The header is called X-API-KEY. This is the standard authorization method in REST APIs — the service reads this header and identifies who the request came from.
In the examples below, this header is included in every request via the -H flag (short for "header").
Core Capabilities of the Mymeet.ai REST API
The API covers the full meeting lifecycle: from launching a recording to retrieving a finished report and managing data. Twelve methods are available, grouped into three categories by function.
Recording Meetings and Uploading Audio Files via API
The API offers two ways to get a transcript and report. The first — send a bot to an online meeting: you pass the meeting link, platform, and time — the bot joins automatically. Supported platforms: Google Meet, Zoom, Microsoft Teams, Yandex.Telemost, SberJazz, TrueConf, Kontur.Tolq, Jitsi. Recording can be scheduled — for example, to have the bot automatically join every weekly sync.
The second — upload an existing file. If the meeting has already been recorded, you can upload the audio or video directly — the service processes it and generates a transcript and report. Maximum file size is 3 GB; files over 1 GB are available on Pro and Business plans.
Retrieving Transcripts and Reports via API
Once a meeting has been processed, data is available through several methods. Processing is asynchronous — this means launching a recording and retrieving the finished result are two separate requests with time between them.
Processing status moves sequentially: new (created) → queued (in queue) → processing (in progress) → processed (ready). When the status is processed, the following are available:
full JSON meeting report with transcript, summary, and metadata
report download in PDF, DOCX, JSON, or Markdown format
paginated list of all meetings in the workspace
JSON is the universal data exchange format between programs — convenient for further processing in code. PDF and DOCX are for sharing with people. Markdown is for uploading to a knowledge base.
Managing Meetings and Report Templates via API
Beyond recording and data retrieval, the API allows managing already-processed meetings. The analysis template determines what type of report is generated: summary, sales report, HR interview, research, meeting minutes, and others — 11 options in total. The template can be set at launch and changed after processing without re-running the recording.
Full list of management operations:
rename a meeting
apply a different template to an already-processed meeting
update a specific section of the report
clear the transcript or restore it
delete a meeting
This enables flexible pipelines: process a meeting with one template, then apply another — without reprocessing the audio.
Mymeet.ai REST API Request Examples
Below are three core scenarios with a breakdown of each part of the code. Examples use curl — a standard utility for sending HTTP requests, available in the terminal on any operating system. Substitute your own key and actual meeting data.
Launch a Bot on an Online Meeting via API
Send a request with meeting details — the bot joins automatically.
What each part means:
curl -X POST— sends data to the server (POST is the request type for creating something new)-H "X-API-KEY: your_key"— your key from Mymeet.ai settings-H "Content-Type: application/json"— tells the server the data is in JSON format"link"— the meeting URL from your browser"source"— the platform:gmeet,zoom,msteams,yandextelemost, and others"template_name"— the report type:summaryis the standard summary
On success, the server returns a 200 status and the data for the created meeting, including its ID — you'll need it for subsequent requests.
Get a List of Workspace Meetings via API
To work with a specific meeting, you need its unique ID (a long string like a1b2c3d4-...). The simplest way to find it is to request a list of all meetings.
What each part means:
curl -X GET— retrieves data from the server (GET is the request type for reading)?page=0— page number (zero-indexed, so 0 is the first page)&perPage=10— how many meetings to show per page
The response arrives as JSON: a list of meetings with their IDs, titles, dates, and processing statuses. Copy the ID you need — it's used in all requests for that meeting.
Download a Meeting Report in Your Preferred Format
Once a meeting is processed (status: processed), download the finished report.
What each part means:
meeting_id=YOUR-MEETING-ID— the unique meeting ID from the previous requestformat=pdf— the desired format:pdf,docx,json, ormd-o report.pdf— the "output" flag, specifies where to save the file. Without it, the content prints to the terminal
The file saves to the folder from which the terminal is running. The filename (report.pdf) can be set to anything you like.
Plans and Limits for the Mymeet.ai REST API
API availability depends on the plan of the workspace the key is linked to. On the Free plan, the API key page is accessible and the key is partially visible — this lets you explore the documentation and prepare your integration before upgrading. However, endpoint requests on Free are rejected with error code 402.
Plan | API Access | Maximum File Size |
Free | Key visible, requests don't work | — |
Lite | Full access | Up to 1 GB |
Pro | Full access | Up to 3 GB |
Business | Full access | Up to 3 GB |
All API requests inherit the workspace plan's limits: minute quota, number of simultaneous bots, meeting restrictions. Switch the workspace using the selector on the API key page — and requests will run within the new workspace's limits.
Summary
The Mymeet.ai REST API covers tasks that are difficult to handle through the interface: automatic recording triggers, programmatic transcript export, and building analytics pipelines. Your API key is already in settings — no additional activation required.
Full technical documentation with all endpoints, parameters, and response schemas: → https://backend.mymeet.ai/docs/
If you need to connect an AI agent (Claude, Cursor, ChatGPT) without writing code — read the Mymeet.ai MCP guide.
Frequently Asked Questions About the Mymeet.ai API
Where can I find my Mymeet.ai API key?
In your user settings — click "API Key." The key is already created; nothing needs to be generated. On a paid plan, click "Copy" — the full value is copied to your clipboard. On the Free plan, copying is unavailable.
Which plans support the Mymeet.ai REST API?
Paid plans: Lite, Pro, and Business. On the Free plan, the API key page is available for exploration, but endpoint requests are rejected with error 402 (insufficient permissions).
How do I pass the API key correctly in requests?
Via the X-API-KEY: your_key header in every request. A header is a service line that travels alongside the request and carries authorization information. In curl, a header is added with the -H flag.
Which video conferencing platforms does the Mymeet.ai API support?
Google Meet, Zoom, Microsoft Teams, Yandex.Telemost, SberJazz, TrueConf, Kontur.Tolq, and Jitsi. The platform is specified in the source field when submitting a recording request.
In what formats can I download a report via the Mymeet.ai API?
PDF, DOCX, JSON, and Markdown. The format is specified in the format parameter. JSON is suited for programmatic processing, Markdown for knowledge bases, and PDF and DOCX for sharing with participants.
Can I schedule a recurring meeting recording via API?
Yes. When launching a recording, you can include a cron parameter — a schedule in standard cron format (time in UTC). This lets you automatically send the bot to recurring meetings — for example, every Monday at 10:00 — without any manual action.
Is there a file size limit for audio uploads?
The maximum file size is 3 GB. Files between 1 GB and 3 GB are only available on Pro and Business plans. Files shorter than 30 seconds are not accepted. Uploads use chunked transfer — this is the standard method for uploading large files via API.
What are analysis templates and what types are available?
A template determines the type of report generated from a meeting. Eleven templates are available: general summary, sales summary, sales coaching, HR interview, research report, meeting minutes, speaker summary, and others. The template is set when launching the recording and can be changed after processing — without re-recording.
How do I know when a meeting has been processed and the report is ready?
Request the meeting status by its ID. Statuses progress sequentially: new (created) → queued (in queue) → processing (in progress) → processed (ready). When the status is processed, the report is available for download.
Where can I find the full Mymeet.ai REST API documentation?
Full documentation with all endpoints, parameters, response codes, and data schemas: https://backend.mymeet.ai/docs/
Fedor Zhilkin
Jun 9, 2025
