Read Wave recordings, transcripts, and summaries programmatically. Run semantic search across a user’s entire recording history. Token-based, scoped permissions, served at api.wave.co.
Wave API tokens start with the prefix wave_api_. Tokens are scoped — pick from sessions:read, sessions:search, and transcripts:read so a token has access only to what it needs. Tokens are stored as SHA-256 hashes server-side — even Wave staff cannot recover a token after creation, so save it when you generate it.
# List a user's sessions
curl https://api.wave.co/v1/sessions \
-H "Authorization: Bearer wave_api_..."
# Fetch a single session with its transcript
curl https://api.wave.co/v1/sessions/SESSION_ID \
-H "Authorization: Bearer wave_api_..."
# Semantic search across a user's recordings
curl -X POST https://api.wave.co/v1/search \
-H "Authorization: Bearer wave_api_..." \
-H "Content-Type: application/json" \
-d '{"query": "decisions we made about pricing"}'The Wave API is one of three developer surfaces, all sharing the same account and permissions:
Full reference docs are at api.wave.co.
Social Media
Use Cases
All rights reserved
Made with love in New York City