| title | Integration Apps |
|---|---|
| icon | link |
| description | Build webhook-based apps that connect Omi to external services. Process memories, real-time transcripts, raw audio, or daily summaries. |
Integration apps allow Omi to interact with external services by sending data to your webhook endpoints. Unlike prompt-based apps, these require you to host a server.
Run code when a memory is created Process live transcripts as they happen Receive raw audio bytes for custom processing Receive a daily recap of a user's conversationsflowchart LR
subgraph Omi["Omi Backend"]
M[Memory Created]
T[Live Transcript]
A[Audio Stream]
D[Day Summary]
end
subgraph Your["Your Server"]
W[Webhook Endpoint]
P[Process Data]
E[External Services]
end
M -->|POST| W
T -->|POST| W
A -->|POST| W
D -->|POST| W
W --> P
P --> E
These apps are activated when Omi creates a new memory, allowing you to process or store the data externally.
This trigger also covers conversations uploaded from a Limitless Pendant. If an initial short fragment is discarded, Omi sends the event once later uploaded speech makes the conversation visible. 1. User completes a conversation 2. Omi processes and creates a memory 3. Your webhook receives the complete memory object 4. Your server processes and respondsThe webhook receives the full conversation data including transcript, structured summary, action items, and metadata.
**Running FastAPI locally (no cloud deployment):**
<iframe
width="560"
height="315"
src="https://www.youtube.com/embed/bMU6fTLysRY?si=3cvXEsWAUwKEnjHn"
title="Running FastAPI Locally"
frameborder="0"
allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"
referrerpolicy="strict-origin-when-cross-origin"
allowfullscreen
></iframe>
Your endpoint receives a POST request with the memory object:
POST /your-endpoint?uid=user123
{
"id": "memory_abc123",
"created_at": "2024-07-22T23:59:45.910559+00:00",
"started_at": "2024-07-21T22:34:43.384323+00:00",
"finished_at": "2024-07-21T22:35:43.384323+00:00",
"transcript_segments": [
{
"text": "Let's discuss the project timeline.",
"speaker": "SPEAKER_00",
"speakerId": 0,
"speaker_name": "John",
"is_user": false,
"start": 10.0,
"end": 15.0
}
],
"structured": {
"title": "Project Timeline Discussion",
"overview": "Brief overview of the conversation...",
"emoji": "📅",
"category": "work",
"action_items": [
{
"description": "Send project proposal by Friday",
"completed": false
}
],
"events": []
},
"apps_response": [],
"discarded": false,
"folder_id": "folder_uuid",
"folder_name": "Work"
}Process conversation transcripts as they occur, enabling real-time analysis and actions.
This trigger requires an active live-listen session. Historical or store-and-forward uploads, including Limitless Pendant WAL uploads, do not replay transcript segments through the real-time webhook. 1. User starts speaking 2. Omi transcribes in real-time 3. Your webhook receives transcript segments as they're created 4. Your server processes and can trigger immediate actionsSegments arrive in multiple calls as the conversation unfolds, allowing for live reactions.
Your endpoint receives transcript segments with session context:
POST /your-endpoint?session_id=abc123&uid=user123
[
{
"text": "I think we should prioritize the mobile app.",
"speaker": "SPEAKER_00",
"speakerId": 0,
"is_user": false,
"start": 10.0,
"end": 15.0
},
{
"text": "Agreed, let's start with iOS.",
"speaker": "SPEAKER_01",
"speakerId": 1,
"is_user": true,
"start": 16.0,
"end": 18.0
}
]Stream raw audio bytes from Omi directly to your endpoint for custom audio processing.
Audio-byte delivery requires an active live-listen session. Historical or store-and-forward uploads do not replay their audio through this webhook. 1. User speaks into Omi device 2. Raw PCM audio is streamed to your endpoint 3. Your server processes the audio bytes directly 4. Handle as needed (custom STT, VAD, feature extraction, etc.)Unlike transcript processors, you receive the actual audio data, not text.
| Setting | Value |
|---|---|
| Trigger Type | audio_bytes |
| HTTP Method | POST |
| Content-Type | application/octet-stream |
| Audio Format | PCM16 (16-bit little-endian) |
| Bytes per Sample | 2 |
Request format:
POST /your-endpoint?sample_rate=16000&uid=user123
Body contains raw PCM16 audio bytes.
To produce a playable WAV file, prepend a WAV header and concatenate the received chunks.You can control how often audio is sent via the Omi app Developer Settings:
url,seconds
For example: https://your-endpoint.com/audio,5 sends audio every 5 seconds.
Receive a structured daily recap of a user's conversations, delivered at most once per day at the user's configured notification hour. The webhook only fires on days where the user actually had recorded, transcribed conversations — see Delivery conditions below.
1. An hourly cron job runs at minute 0 of every UTC hour 2. For each user whose local time matches their configured notification hour, Omi generates a comprehensive daily summary using an LLM 3. Your webhook receives the summary 4. Your server can store, display, or forward it to external services**Day selection logic:** If the user's local time is before noon (12:00), the summary covers the *previous* day's conversations; at noon or later it covers *today's* conversations.
**Timezone requirement (scheduled delivery only):** The hourly cron job selects recipients by matching configured timezones to the current UTC hour, so users without a timezone are skipped by the schedule. The manual "Generate Summary" trigger described in the testing section falls back to UTC day boundaries and works without a configured timezone.
**Delivery conditions (when the webhook does *not* fire):**
- The user has no conversations for the selected day
- All conversations for the day are either locked or have no transcribed speech
- The user has no FCM push token registered. The cron path filters out token-less users when picking recipients, and the manual "Generate Summary" endpoint returns HTTP 400 in that case — the daily summary pipeline currently treats push delivery as a hard prerequisite for firing the webhook
- A delivery for the same `(uid, date)` has already been started — Omi acquires an atomic Redis lock *before* the LLM call (TTL 2 hours), so any subsequent cron tick within that window is a no-op even if the earlier run hasn't finished or ended up skipping for one of the reasons above
Treat days without a webhook delivery as "no recap available" rather than a failure — receivers should not assume the webhook fires every day.
Your endpoint receives a POST request with the daily summary:
POST /your-endpoint?uid=user123
{
"uid": "user123",
"created_at": "2024-01-15T22:00:00.123456+00:00",
"summary": "{'id': '550e8400-...', 'date': '2024-01-15', 'headline': 'Productive day with three focused work sessions', ...}",
"summary_json": {
"id": "550e8400-e29b-41d4-a716-446655440000",
"date": "2024-01-15",
"headline": "Productive day with three focused work sessions",
"overview": "...",
"day_emoji": "💼",
"stats": {
"total_conversations": 3,
"total_duration_minutes": 87,
"action_items_count": 4
},
"highlights": [],
"action_items": [],
"unresolved_questions": [],
"decisions_made": [],
"knowledge_nuggets": [],
"locations": []
}
}Field reference:
| Field | Type | Description |
|---|---|---|
uid |
string | User identifier (also in query param) |
created_at |
string (ISO 8601 with +00:00 offset) |
Webhook send time in UTC |
summary_json |
object | Recommended. The daily summary as a real JSON object (schema below). Use this for any new integration. |
summary |
string | Legacy. The same payload serialized via Python's str(...), kept for backward compatibility. See the migration note below. |
The summary_json object has this shape (also reflects what summary represents once parsed):
{
"id": "550e8400-e29b-41d4-a716-446655440000",
"date": "2024-01-15",
"created_at": "2024-01-15T22:00:00.000000",
"headline": "Productive day with three focused work sessions",
"overview": "You had a productive day that included a project planning meeting, a deep-work coding session, and a team retrospective.",
"day_emoji": "💼",
"stats": {
"total_conversations": 3,
"total_duration_minutes": 87,
"action_items_count": 4
},
"highlights": [
{
"topic": "Q2 Roadmap",
"emoji": "🗺️",
"summary": "Locked in the Q2 feature priorities with the product team.",
"conversation_ids": ["conv_abc123"]
}
],
"action_items": [
{
"description": "Send project proposal to design team by Friday",
"priority": "high",
"completed": false,
"source_conversation_id": "conv_abc123"
}
],
"unresolved_questions": [
{
"question": "Which deployment pipeline should we adopt?",
"conversation_id": "conv_abc123"
}
],
"decisions_made": [
{
"decision": "Migrate analytics to BigQuery",
"conversation_id": "conv_abc123"
}
],
"knowledge_nuggets": [
{
"insight": "GitHub Actions reusable workflows can take typed inputs since 2023",
"conversation_id": "conv_abc123"
}
],
"locations": [
{
"name": "Home office",
"latitude": 37.7749,
"longitude": -122.4194,
"time": "09:30"
}
]
}Decide which integration type(s) you need: - **Memory Trigger**: Process completed conversations - **Real-Time Transcript**: React to live speech - **Audio Bytes**: Process raw audio - **Day Summary**: Receive a daily recap of conversations Create a webhook endpoint that can receive POST requests. For testing, use [webhook.site](https://webhook.site) or [webhook-test.com](https://webhook-test.com/).
Your endpoint should:
- Accept POST requests
- Parse JSON body (or binary for audio)
- Read `uid` from query parameters
- Return 200 OK quickly
**Example (Python/FastAPI):**
```python
from fastapi import FastAPI, Request
app = FastAPI()
@app.post("/webhook")
async def handle_memory(request: Request, uid: str):
memory = await request.json()
# Process memory data
await send_to_slack(memory["structured"]["title"])
return {"status": "ok"}
```
Open Omi app → Settings → Enable Developer Mode → Developer Settings - **Memory Triggers**: Enter URL in "Memory Creation Webhook" - **Real-Time**: Enter URL in "Real-Time Transcript Webhook" - **Audio Bytes**: Enter URL (optionally with `,seconds` suffix) in "Audio Bytes Webhook" - **Day Summary**: Enter URL in "Day Summary Webhook" Go to any memory → Tap 3-dot menu → Developer Tools → Trigger webhook with existing data Start speaking - your endpoint receives updates immediately The Day Summary webhook only fires on the scheduled cron path. The in-app "Generate Summary" trigger (Settings → Daily Summary → ⋮ menu) regenerates the summary on demand but does *not* currently POST to the developer webhook. The fastest way to validate a receiver is to enable the webhook, set its delivery hour to the next upcoming hour, and wait for the next cron tick. Use [webhook.site](https://webhook.site) to see exactly what data Omi sends before writing any code.
When submitting your integration app:
| Field | Required | Description |
|---|---|---|
| Webhook URL | Yes | Your POST endpoint for receiving data |
| Setup Completed URL | No | GET endpoint returning {"is_setup_completed": boolean} |
| Auth URL | No | URL for user authentication (uid appended automatically) |
| Setup Instructions | No | Text or link explaining how to configure your app |
Access your own personal Omi data programmatically Create conversations and memories via REST API Detailed guide for processing raw audio bytes Add custom tools users can invoke in chat Add authentication flows to your apps Send push notifications from your app Create apps without hosting a server Overview of all app types