EN
Meeting APIClosed beta

Notetaker API to Record and Transcribe Every Meeting

Send a notetaker to Google Meet, Microsoft Teams or Zoom with one API call. Get the recording, transcript, summary and action items back by webhook. No bot to build or maintain.

In closed beta. Contact us to get access.

At a glance

From meeting URL to transcript in one API call

  • €0.30 / hour Transcript included

    Summaries and action items too.

  • 5 hours free Every month, every account

    Per connected calendar account.

  • 3 platforms Meet, Teams, Zoom

    One payload, one set of webhooks.

  • 1 API call From URL to transcript

    Join now, later, or from the calendar.

Triggers

Three ways to send a notetaker to a meeting

One endpoint for every trigger: join now, plan ahead, or let the calendar decide.

Now

Join right now

Post a meeting URL and the notetaker joins at once. Perfect for a Record button or an AI agent.

Later

Schedule for later

Add a future join_at timestamp. Update or cancel it any time before it joins.

Automatic

Follow the calendar

Matching events on a connected Google or Outlook calendar create, move or cancel their own notetaker.

See the Calendar API
Request and response

One request, one notetaker

Post the meeting URL, then follow the job by webhook. Configuration and retries come from the account.

Requestcreate-notetaker.sh
curl --request POST \
  "https://api.unipile.com/v2/$ACCOUNT_ID/notetakers" \
  --header "X-API-KEY: $UNIPILE_API_KEY" \
  --header "Idempotency-Key: customer-meeting-123" \
  --header "Content-Type: application/json" \
  --data '{
    "meeting_url": "https://meet.google.com/abc-defg-hij",
    "artifact_settings": {
      "transcript": { "enabled": true },
      "summary": { "enabled": true },
      "action_items": { "enabled": true }
    },
    "retention": { "type": "timed", "hours": 72 }
  }'
Responsenotetaker.json
{
  "object": "Notetaker",
  "id": "nt_01k00000000000000000000000",
  "status": "joining",
  "meeting_provider": "google_meet",
  "capture_source": "cloud",
  "processing_plan": {
    "live_transcript": "disabled",
    "final_transcript": "source",
    "speaker_identification": "source",
    "summary": "unipile",
    "action_items": "unipile"
  }
}
Meeting artifacts

What comes back from every meeting

One schema for Google Meet, Microsoft Teams and Zoom. Your code never branches on the platform.

Meeting recording

Audio and video, streamed with HTTP Range support so your player can seek.

Speaker-attributed transcript

Timestamped segments with speaker diarization and language detection. No separate speech-to-text vendor.

Summary

Generated from the final transcript, with your own instructions for format and tone.

Action items

Follow-ups extracted from the call, ready for a CRM, an ATS or a task manager.

Webhooks for every artifact

Five events tell your backend what is ready.

notetaker.status notetaker.transcript notetaker.recording notetaker.summary notetaker.action_items

Full job history

A timeline per notetaker, so your support team can answer on its own.

CRM and ATS sync

From transcript to an updated record

Pull the facts your users need out of the call and write them into the candidate or deal record. No more notes typed after the meeting.

ATS: fill the candidate profile

CRM: update the deal

1

List the fields you want in the summary's custom instructions.

2

Receive notetaker.summary and the transcript by webhook.

3

Write each value to the record, with its timestamp as proof.

Configuration

Configured once, per customer

Each customer has its own recording policy. Set defaults once, then override them where needed.

  • Inherited settings

    Application, then customer, then user, then a single meeting: each level overrides the one above.

  • Bot name and avatar

    Your product's name and image in the participant list, not ours.

  • Deduplication

    Several users in one meeting share one capture, not several bots.

  • Quota and pause

    Metered overage or a hard limit, and a pause switch per account.

  • Retention policies

    Delete on delivery, keep for a set number of hours, or retain long-term.

  • Consent announcements

    Choose what the notetaker announces when it joins, market by market.

Capture strategies

A meeting bot API that is not only a bot

A classic meeting bot works until IT blocks external guests. Unipile offers three capture strategies behind one contract, and tells you which one ran in capture_source.

POST/notetakers"capture_strategy": "auto"

cloud

A hosted participant joins the call. Nothing to install.

extension

Records in the user's browser tab. No external guest in the meeting.

official_api

Uses the platform's own interfaces through the connected Google or Microsoft account.

Same request, lifecycle, artifacts and webhookscapture_source
Auto or pinned

auto picks the first source that supports the meeting. Pin a single value and there is no silent fallback.

One contract

Request, lifecycle, artifacts and webhooks stay identical: adding a strategy is a configuration change, not a rewrite.

One account model

Built on the same account model as the rest of Unipile

A notetaker runs on the Google or Microsoft account your user already connected for the Calendar API and the Email API. One connection, one consent screen.

A moved meeting moves its notetaker, a cancelled one cancels it. The transcript lands next to the LinkedIn conversation and the email thread with the same prospect.

Pricing

Pricing that does not punish success

One hourly rate, billed to the second. Transcript, summary and action items included.

  • €0.30 Per hour of capture

    Billed per second, transcript included.

  • 300 min Included every month

    Per connected calendar account.

  • €0 For calendar access

    Scheduling and calendar sync are part of the API.

No per-participant fee No separate speech-to-text invoice Summaries and action items included
Usage and billing

Usage you can actually reconcile

Usage comes back as data, so the minutes you bill always match ours. One predictable line, like the rest of the Unipile pricing model.

GET/notetakers/usageQuota, overage, estimate
GET/notetakers/usage/exportPer-job breakdown for the month
Security

Security, consent and data protection

Meeting content is sensitive data. The API is built for it.

Built into the API

  • Media downloads require Unipile authentication.

  • Capture credentials are never exposed to the browser.

  • Extension tokens are short-lived.

  • Deleting a notetaker erases its artifacts and anonymises personal data. Billing seconds are kept.

Customer responsibility

You stay the data controller

You set retention, announcements and capture rules, and you inform participants and hold the legal basis for recording.

Read more about security and compliance at Unipile, or compare the total cost with a Recall.ai alternative before you commit.

Notetaker API: frequently asked questions

Platforms, capture strategies, billing and data retention, answered for developers.

A notetaker API is a developer interface that sends a capture participant into an online meeting, records audio and video, and returns a speaker-attributed transcript through HTTP endpoints and webhooks. It lets a CRM, an ATS or an AI agent add meeting recording without building and hosting meeting bots.

Google Meet, Microsoft Teams and Zoom, from a connected Google or Microsoft calendar account. The meeting platform is normally inferred from the meeting URL, and the same request payload works for all three.

No. Transcription with speaker diarization and automatic language detection is part of the API and part of the hourly rate, as are summaries and action items when you enable them.

Yes. List the fields you need in the summary instructions, such as salary expectation and availability for a candidate or deal amount and close date for an opportunity, then write the values into the record when the webhook arrives.

Yes. The extension capture strategy records inside the participant's browser tab, so no external guest appears in the participant list. The cloud strategy joins as a visible participant, and auto picks whichever is available.

Yes. Send a future join_at timestamp to schedule one, or enable calendar automation so that events on a connected Google or Outlook calendar create, reschedule and cancel their own notetakers.

Deduplication lets eligible scheduled jobs in the same scope share one capture, so one meeting does not end up with several bots and several invoices.

Per hour of capture, billed to the second, with an included monthly quota per connected account. Transcription, summaries and action items are included. A usage endpoint and an auditable per-job export let you reconcile every cent.

You choose: delete artifacts as soon as they are delivered, keep them for a set number of hours, or retain them long-term when your contract requires it. Deleting a notetaker removes its artifacts and anonymises personal data.

It is currently in beta and enabled per organisation. Contact us to get your organisation activated and to lock in beta pricing.

Still have questions? Our team is here to help.

Talk to an expert