API Updates

Improvements & Retranscribe Route

Teams/GMeet stability improvements and new transcription capabilities

Paris, the 27th of February 2025.

We're excited to announce significant improvements to our platform stability and the introduction of new API capabilities.

Platform Stability Improvements

Teams & Google Meet Enhancement

  • Complete engine rewrite for both Teams and Google Meet platforms
  • Migrated from Puppeteer to Playwright for improved stability
  • Significantly enhanced performance and reliability
  • Successfully tested with extended runtime (15+ hours) showing excellent stability

New API Features

New Retranscribe Endpoint

  • Introduced new POST /bots/retranscribe endpoint
  • Allows transcription or retranscription of a bot's audio
  • Supports both default and custom speech-to-text providers
  • Flexible webhook configuration for processing notifications

OCR Capabilities

  • Added Optical Character Recognition (OCR) inside bots for better detection of current meeting status
  • This will enable future features including:
    • Sharing screenshots of meeting content
    • OCR'ed content shared in meetings (for RAG and other AI-enhanced applications)
  • Improves bot awareness of visual meeting context

Join Endpoint Enhancement

  • Added audio_only parameter to POST /bots endpoint
  • Enables audio-only participation in meetings
  • Optimized for scenarios requiring only audio capabilities

Implementation Details

Retranscribe API

The new retranscribe endpoint accepts the following parameters:

  • bot_uuid: Identifier for the target bot
  • provider: Choice of speech-to-text provider
  • webhook_url: Optional callback URL for completion notifications

The retranscribe feature is particularly useful for:

  • Improving existing transcriptions

  • Using different speech-to-text providers

  • Recovering from any transcription issues

Future Enhancements

We're actively working on expanding the capabilities of the retranscribe endpoint:

  • Additional speech-to-text providers will be supported in upcoming releases
  • Custom provider parameters will be exposed through a flexible JSON configuration field
  • This will enable fine-tuned control over transcription settings and provider-specific features

Migration Guide

No breaking changes were introduced with these updates. All new features are additive and backward compatible with existing implementations.

Implementation Timeline

These changes are now live in production and available for immediate use.

On this page