Introducing the Wave Developer API

Wave has captured over 172 million minutes of conversations. Until now, all that data lived inside the Wave app. Today, we're opening it up.

The Wave Developer API gives you programmatic access to your sessions, transcripts, summaries, and media. Build custom integrations, sync meeting notes to your CRM, search across recordings with natural language, or pipe session data into whatever workflow you've been wishing existed.

What You Can Do

The API covers the full lifecycle of a Wave session:

• List and retrieve sessions — access metadata, AI summaries, notes, and tags for any recording
• Get full transcripts — speaker-attributed transcripts with timestamps, ready for analysis or export
• Semantic search — search across all your sessions using natural language queries like "when did we discuss pricing?"
• Update sessions — modify titles, notes, tags, and favorite status programmatically
• Access media — get signed URLs for audio and video files
• Bulk export — pull up to 50 sessions at once with transcripts and summaries included
• Account info — check subscription status and session counts

Webhooks

The API isn't just request-response. You can register webhooks to get notified in real time when things happen:

• session.completed — a new recording finishes processing
• session.updated — session metadata is changed
• session.deleted — a session is removed

Every webhook delivery is signed with HMAC-SHA256, so you can verify that payloads actually came from Wave. Failed deliveries automatically retry with exponential backoff.

Use Cases

Here are some of the things people are building:

• CRM sync — automatically push meeting summaries and action items to Salesforce, HubSpot, or Pipedrive after every call
• Slack and Teams bots — post meeting recaps to a channel as soon as recordings finish processing
• Analytics dashboards — track meeting volume, duration trends, and team activity over time
• Custom AI workflows — feed transcripts into your own LLM pipelines for specialized analysis
• Compliance and archiving — export recordings and transcripts on a schedule for audit trails
• Notion and docs sync — create a meeting note in your knowledge base every time a session completes

Authentication and Security

API tokens follow the principle of least privilege. When you create a token, you choose exactly which scopes it gets — read sessions, write metadata, access transcripts, manage webhooks, and so on. Tokens are hashed on our end, so we never store the raw key.

Create and manage your tokens at app.wave.co/settings/integrations/api.

Getting Started

It takes about a minute to make your first API call:

1. Go to Settings → Integrations → API and create a token
2. Make a request:

curl -H "Authorization: Bearer wave_api_your_token" \
  https://api.wave.co/v1/sessions

That's it. You'll get back a list of your sessions with metadata, summaries, and pagination.

Full documentation, interactive API reference, and an OpenAPI spec are all available at api.wave.co.

Rate Limits

Standard rate limits are 60 requests per minute and 1,000 per day per token. Response headers tell you exactly where you stand. If you need higher limits for a production integration, reach out to us.

What's Next

This is the first version of the Wave API, and we're actively building on it. If you have feedback or want to see specific endpoints, let us know — the API is shaped by what developers actually need.

Start building: api.wave.co