Fellow API

Product Introduction

1. Fellow API is a programmable interface designed to integrate meeting data and workflows with external systems for enhanced automation and compliance. It enables organizations to archive compliance records, trigger actions based on meeting content, feed analytics dashboards, and process transcripts through large language models (LLMs) for summaries and action plans. The API provides RESTful endpoints with comprehensive documentation and code samples to accelerate integration.
2. The core value of Fellow API lies in its ability to bridge meeting intelligence with enterprise systems, ensuring compliance while automating critical workflows. It transforms raw meeting data into actionable insights, governance-aligned processes, and LLM-driven outputs without requiring manual intervention. This reduces operational overhead and enhances cross-platform interoperability for teams relying on meeting outcomes.

Main Features

1. Workspace Governance: Admins control API access through granular permissions, including key revocation and usage auditing via 90-day logs. Workspace owners can enable/disable the API globally, monitor active keys, and view last-used timestamps for security compliance. This ensures alignment with SOC 2 Type II and internal governance policies.
2. Developer-Ready Infrastructure: The API offers clean REST endpoints with OpenAPI specifications, SDKs in multiple languages, and prebuilt code samples for common use cases like compliance archiving or LLM integration. Documentation includes authentication workflows, rate limits, and error-handling guidelines to streamline proof-of-concept development.
3. Enterprise-Grade Security: All data transfers use HTTPS encryption with TLS 1.2+, while audit logs retain metadata for 90 days to meet e-discovery and legal hold requirements. Access tokens are permission-scoped, and API keys rotate automatically based on organizational policies.

Problems Solved

1. Manual Compliance Overload: Automates retention and auditing of meeting records to satisfy legal and regulatory requirements, eliminating error-prone manual processes. Reduces risk during audits by providing immutable logs of API interactions.
2. Disconnected Workflows: Addresses silos between meeting outcomes and downstream tools like CRMs, LLMs, or analytics platforms. Enables real-time triggers—for example, alerting sales teams when specific contract terms are discussed or updating project boards after action items are assigned.
3. Inefficient Data Utilization: Solves underutilization of meeting data by making transcripts, decisions, and action items programmatically accessible. Teams can feed this data into custom dashboards, training models, or recap generators without manual extraction.

Unique Advantages

1. Granular Admin Controls: Unlike competitors, Fellow API allows workspace-level governance, letting admins disable access globally or revoke individual keys without disrupting other users. Audit logs include timestamps, IP addresses, and endpoint-specific metadata for forensic analysis.
2. Prebuilt LLM Integration: Native support for passing transcripts to LLMs via webhooks or direct API calls simplifies generating summaries, sentiment analysis, or compliance checks. This eliminates the need for middleware in AI-driven workflows.
3. Compliance-by-Design Architecture: Unlike generic APIs, Fellow embeds retention policies and encryption standards into its infrastructure, reducing the need for additional compliance tooling. It prevalidates against SOC 2 Type II, GDPR, and CCPA frameworks.

Frequently Asked Questions (FAQ)

1. Who can enable Fellow’s API? Workspace owners or admins with "Manage Integrations" permissions can enable or disable API access globally. User-level keys require admin approval and adhere to role-based access controls (RBAC) defined in the workspace.
2. Is access permission-aware? Yes, API keys inherit the permissions of the user who generates them, ensuring data access aligns with existing role policies. For example, a marketing team member cannot access engineering-specific endpoints without explicit grants.
3. What data format do responses use? All endpoints return JSON-formatted data with standardized HTTP status codes. Transcripts include speaker-diarized text, timestamps, and optional metadata like sentiment scores or action item tags.
4. How is it secured and audited? Requests are encrypted via HTTPS, and keys use SHA-256 hashing. A 90-day audit log tracks API activity, including endpoint, timestamp, user ID, and IP address, accessible only to admins for compliance reviews.