Import a recording made elsewhere

Upload an audio file recorded outside Meetily and get a transcript and summary from it.

If you have an audio file recorded somewhere else, your phone, another app, a colleague, you can bring it into Meetily and get a transcript and summary from it. This walkthrough uploads a file, waits for it to finish, and reads back the summary.

This is an HTTP upload

Importing is available over the HTTP API only, not the CLI, the SDK, or an AI-assistant tool. In practice a developer or your AI assistant runs the upload for you, then you read the finished summary in the app or over the API.

Before you start

Enable Integrations in the app (see the Quickstart) so the gateway is running.

Step 1: upload the file

Send POST /v1/jobs/import with a filename query parameter and the raw file bytes as the body. It returns 202 with a job_id.

curl -s -X POST "http://127.0.0.1:8420/v1/jobs/import?filename=standup.m4a" -H "Authorization: Bearer $MEETILY_PRO_TOKEN" --data-binary @standup.m4a

Accepted formats: mp4, m4a, wav, mp3, flac, ogg, aac, mkv, webm, wma. Up to 2 GB per file.

Step 2: watch the job

Poll GET /v1/jobs/:id with the job_id from step 1 until its state is completed. The job carries a meeting_id once one is assigned; that is your new meeting.

curl -s http://127.0.0.1:8420/v1/jobs/JOB_ID -H "Authorization: Bearer $MEETILY_PRO_TOKEN"

Step 3: read the summary

Once the import completes, read the meeting summary with GET /v1/meetings/:id/summary, using the meeting_id from step 2.

curl -s http://127.0.0.1:8420/v1/meetings/MEETING_ID/summary -H "Authorization: Bearer $MEETILY_PRO_TOKEN"

If you want a fresh summary instead of the one generated automatically, regenerate it:

curl -s -X POST http://127.0.0.1:8420/v1/meetings/MEETING_ID/summary/regenerate -H "Authorization: Bearer $MEETILY_PRO_TOKEN" -H "content-type: application/json" -d '{"template_id":"daily_standup"}'

Good to know

No pause, only cancel

Import jobs cannot be paused or resumed. You can cancel a running one with POST /v1/jobs/:id/cancel, but to change anything about the import (a different file, a different filename) you cancel and re-upload rather than editing the job in place.

If an import fails, its error text is path-redacted before you read it. See Limitations and roadmap for details.
Large files count against a shared ceiling: up to 20 GB across all imports and at most 3 running at once.