Hedy Bot Hedy API

Name: Hedy API
Brand: Hedy API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityCollaborationapiKey4 EndpointsREST

For Agents

List Hedy AI meeting sessions and retrieve their transcripts, summaries, and AI-generated highlights across 4 read-only endpoints.

Install Jentic One Beta

Connect the Hedy API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Hedy API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Hedy API.

List recent Hedy meeting sessions, paginated and filterable by date, via GET /sessions

Retrieve a single session's transcript and summary by id via GET /sessions/{sessionId}

List AI-generated highlights (decisions, action items, questions) across sessions via GET /highlights

GET STARTED

Start building with Hedy API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Hedy API for, with concrete tasks.

★ Weekly Status Email Generation

An assistant compiles a weekly status email by pulling the past week's Hedy highlights and grouping them into decisions, action items, and open questions. The /highlights endpoint returns highlights with their source session reference, so the assistant can attribute each item to the meeting it came from. End-to-end the workflow runs in seconds.

Call GET /highlights filtered to the last 7 days and group the results into decisions, action items, and questions

CRM Meeting Note Sync

A sales operations workflow syncs Hedy meeting summaries into CRM contact records. For each new session, the workflow calls /sessions/{sessionId} to fetch the summary and key highlights, then writes them onto the matched contact. No transcription or summarisation is needed locally — Hedy delivers the structured output.

For each session in GET /sessions from the last 24 hours, retrieve the summary via GET /sessions/{sessionId} and append it to the matching CRM contact

Searchable Meeting Memory

A team builds an internal search tool over their meeting history by indexing Hedy sessions and highlights into a vector store. The /sessions and /highlights endpoints supply the raw text content to embed; the agent only handles the index and retrieval layer.

Iterate GET /sessions, fetch each session's transcript via GET /sessions/{sessionId}, and embed the text into a vector store

AI Agent Meeting Assistant

A Claude or GPT assistant answers 'what did we decide in yesterday's meeting?' by calling Hedy through Jentic. The agent searches by intent, loads the /highlights operation, filters by date and category, and returns a concise answer with citations to specific session ids.

Search Jentic for 'list meeting highlights', load the operation, filter to yesterday's date, and return the action items with their source session ids

Key Endpoints

4 endpoints — jentic publishes the only available openapi specification for hedy api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/sessions

List meeting sessions

GET

/sessions/{sessionId}

Get session transcript and summary

GET

/highlights

List AI-generated highlights across sessions

GET

/highlights/{highlightId}

Get a single highlight's content and source session

GET

/sessions

List meeting sessions

GET

/sessions/{sessionId}

Get session transcript and summary

GET

/highlights

List AI-generated highlights across sessions

GET

/highlights/{highlightId}

Get a single highlight's content and source session

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Hedy X-API-Key is stored encrypted in the Jentic vault. Agents receive scoped access tokens — the raw key never enters the agent's prompt or chat context.

Intent-based discovery

Agents search by intent (e.g. 'list meeting highlights' or 'get a meeting transcript') and Jentic returns the matching Hedy operation with its query parameters and headers, so the agent doesn't have to read the SwaggerHub UI.

Time to first call

Direct integration: roughly half a day to wire up auth, pagination, and error handling. Through Jentic: under 30 minutes — search, load, execute.

FAQs

Specific to using Hedy API through Jentic.

Why is there no official OpenAPI spec for Hedy API?

Hedy publishes a Swagger UI on SwaggerHub but does not distribute a maintained OpenAPI file. Jentic generates and maintains this spec so that AI agents and developers can call Hedy via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Hedy API use?

Hedy uses an API key passed in the X-API-Key header (the ApiKeyAuth scheme in the spec). Through Jentic, the key is stored encrypted in the vault and the agent receives scoped access at execution time.

Can I retrieve a meeting transcript with this API?

Yes. GET /sessions/{sessionId} returns the session record including the transcript and summary fields, so an agent can pull the full meeting text in a single call.

What are the rate limits for the Hedy API?

The OpenAPI spec does not declare hard rate limits; Hedy applies fair-use limits per workspace. For high-volume sync workflows, paginate /sessions by date and cache transcripts locally rather than re-fetching.

How do I list recent meeting highlights through Jentic?

Run pip install jentic, have the agent search for 'list meeting highlights', load the GET /highlights operation, and execute it filtered to the desired date range.

Does the Hedy API support creating or updating sessions?

No. The current API surface is read-only — agents can list and retrieve sessions and highlights, but session creation happens inside the Hedy app via the meeting recorder.