The Amie Recording API.
Meeting recordings, without the bot.

The standard way to record meetings programmatically is a meeting bot: a virtual participant that joins the call, sits in the participant list, and streams audio out. That means waiting-room admissions, "who invited the bot?" moments, per-platform quirks, and whole platforms where bots simply can't go. The Amie Recording API takes the other path. It records where the meeting is actually heard, on the device, using the same engine behind Amie's own meeting notes, hardened by millions of hours of transcription for our own users.

Your app starts a recording session through the capture SDK that ships with the API. It records system audio and the microphone locally, keeps the recording alive through network blips and platform hiccups, and streams the result to Amie's API. You get back a live transcript with speaker labels, then a summary and action items when the meeting ends, delivered by webhook or fetched from the API. Calendar context is built in: sessions can be linked to the event they belong to, so recordings arrive organized instead of as anonymous audio files.

The recorder handles the failure modes we've already spent years on: frozen capture daemons, device switches mid-call, flaky networks, and meetings that outlive their scheduled slot. You integrate once and ship; we keep the recordings alive.

Teams use meeting recording APIs to power CRMs that log calls automatically, recruiting tools that capture interviews, sales coaching that needs every conversation, and AI assistants that turn meetings into structured data. If your roadmap says "record the meeting," the hard part isn't the feature, it's the recording infrastructure underneath it. That's the part we've already built.

The API is rolling out to early-access partners now. Tell us what you're building and we'll fast-track you.