Fireflies Transcript Retrieval Boundary

Overview

Treat a transcript as sensitive meeting data. Separate metadata, summary, sentences, analytics, media links, attendance, and sharing fields so callers receive only what their use case permits.

Prerequisites

• The target repository or integration path and the requested operator outcome.
• The Fireflies principal, team, environment, and data classification for the work.
• Current Fireflies documentation, credentials only when needed, and an accountable approver.

Current Contract

Use transcript(id: String!) for one record. Meeting ID and transcript ID refer to the same platform identity. Selected fields have different sensitivity and entitlement requirements; analytics requires an eligible plan, and is_live changes whether sentences are live captions or processed transcript data.

Authentication

For authenticated operations, inject FIREFLIES_API_KEY from an approved secret manager and send it only as Authorization: Bearer REDACTED_KEY to https://api.fireflies.ai/graphql. Never print, commit, place in a URL, forward to a browser, or include the key in evidence. Webhook signing secrets are separate credentials and must not be reused as API keys.