Skip to main content

Overview

Omi allows you to stream audio bytes from your DevKit directly to your backend or any external service. This enables custom audio processing like:

Custom speech recognition

Use your own ASR models instead of Omi’s default transcription

Voice activity detection

Implement custom VAD logic for specialized use cases

Audio analysis

Extract features, spectrograms, or embeddings in real-time

Cloud storage

Store raw audio for later processing or compliance

Technical specifications

The sample rate is passed as a query parameter so your endpoint can handle different device versions.

Setup guide

Create your endpoint

Create a webhook that accepts POST requests with binary audio data.Request format:
Your endpoint should:
  • Accept application/octet-stream content type
  • Read sample_rate and uid from query parameters
  • Process the raw bytes (buffer, save, or analyze)
  • Return 200 OK quickly to avoid timeouts

Configure in the Omi app

  1. Open the Omi app
  2. Go to Settings → Developer Mode
  3. Scroll to Realtime audio bytes
  4. Enter your webhook URL
  5. Set the Every x seconds field (e.g., 10 for 10-second chunks)

Test your integration

Start speaking while wearing your Omi device. Audio bytes should arrive at your webhook at the configured interval.
Use webhook.site to verify data is arriving before implementing your processing logic.

Working with audio bytes

Converting to WAV

The received bytes are raw PCM16 audio. To create a playable WAV file, prepend a WAV header:

Accumulating chunks

If you need continuous audio (not chunked), accumulate bytes across requests:

Example: save to Google Cloud Storage

A complete example that saves audio files to Google Cloud Storage.

Create GCS Bucket

Follow the Cloud Audio Storage setup below to create a bucket, a service account, and a base64-encoded key.

Fork the example repository

Clone and deploy

Clone the repository and deploy to your preferred cloud provider (GCP, AWS, DigitalOcean) or run locally with ngrok.The repository includes a Dockerfile.

Set environment variables

Configure these environment variables during deployment:

Configure the Omi app

Set the endpoint in Developer Settings → Realtime audio bytes:

Verify

Audio files should now appear in your GCS bucket every X seconds (based on your configured interval).

Processing ideas

Feed audio to your own ASR models for specialized vocabulary or languages:
Detect speech vs. silence for custom endpointing:
Extract embeddings for speaker identification or audio similarity:
Analyze emotional tone from audio features:

Best practices

Respond quickly

Return 200 OK immediately, process async. Slow responses may cause timeouts.

Handle missing data

Network issues may cause gaps. Design your processing to handle incomplete audio.

Buffer appropriately

Choose chunk interval based on your use case. Larger chunks = fewer requests but higher latency.

Monitor usage

Audio streaming generates significant data. Monitor storage and bandwidth costs.
Audio data is sensitive. Ensure your endpoint is secured with HTTPS and implement appropriate access controls.

Cloud audio storage

Store audio files from your Omi device in Google Cloud Storage (GCS). You’ll need an active Google Cloud Platform account.

Create a storage bucket

  1. Go to the GCS console
  2. Click Create Bucket
  3. Configure the bucket:
  1. Click Create

Create a service account

  1. Go to IAM & Admin → Service Accounts in the GCP console
  2. Click Create Service Account
  3. Set the name (e.g. omi-audio-uploader)
  4. Grant the Storage Object User role
  5. Click Done

Generate a JSON key

  1. Click on the service account you just created
  2. Go to the Keys tab
  3. Click Add Key → Create new key → JSON
  4. The key file downloads automatically
Keep this key file secure. It grants access to your storage bucket.

Base64 encode the key

Convert the key to Base64 for use as an environment variable:
Copy the output — this is your GOOGLE_APPLICATION_CREDENTIALS_JSON value.

Note your bucket name

Copy your bucket name from the GCS console. This is your GCS_BUCKET_NAME value.
You’ll need these two values when deploying the audio streaming service:

Integration apps

Overview of webhook-based integrations

Cloud audio storage

Guide to storing audio in cloud storage

Real-time transcription

How Omi’s built-in transcription works

Apps introduction

Overview of all Omi app types