Skip to main content

​
Umified API Overview

Welcome to the Umified API documentation. This API allows you to programmatically integrate with Umified, our meeting assistant bot that joins Google Meet, Zoom, and Microsoft Teams meetings to record audio and generate comprehensive meeting transcriptions.

​
API Workflow

The Umified API follows this workflow:
  1. Account & Authentication: Sign-up/login for an Umified account and obtain a Bearer token
  2. Bot Configuration: Customize your bot’s name and message (optional)
  3. Meeting Management: Create instant or scheduled meetings for recording
  4. Retrieve Transcriptions: Access recordings and transcriptions post meeting completion.

​
Base URL

All API requests should be made to: 
https://api.umified.com/api/v1/

​
Core Endpoints

Authentication
  • POST /sign_up/ - Create a new Umified account and obtain access token.
  • POST /sign_in/ - Sign in and obtain access token.
  • DELETE /delete_account/ - Delete account.
Meeting Management
  • POST /create_meeting/ - Create a new meeting (instant or scheduled)
  • PUT /update_meeting/ - Update a scheduled meeting.
  • GET /transcription?session_id={id} - Fetch meeting transcription and return as JSON dictionary.
  • GET /transcription?session_id={id}&token={access_token} - Download meeting transcription as a TXT file.
  • GET /meeting_info?session_id={id} - Fetch meeting details / status including recording url.
Bot Management
  • POST /add_bot/ - Add a custom bot with bot message for user.
  • PUT /update_bot/ - Update the custom bot configuration (bot name and bot message)

​
Authentication

All API endpoints require authentication using Bearer tokens. You’ll receive an access token after signing in with your email and password. Include this token in all subsequent API requests: 
Authorization: Bearer YOUR_ACCESS_TOKEN

​
Standard Error Response

Umified API uses conventional HTTP response codes to indicate the status of requests. Error responses follow this format: 
{
  "message": "Detailed error message",
  "status_code": 400,
  "destination": null
}

​
Code Example: Authentication

Below snippet shows how to sign in to Umified via api call: 
// Request a Bearer token
fetch('https://api.umified.com/api/v1/sign_in/', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({
    email: '[email protected]',
    password: 'your-password'
  })
})
.then(response => response.json())
.then(data => {
  // Store your access token
  const accessToken = data.result.access_token;
  console.log('Authentication successful!');
})
.catch(error => console.error('Authentication failed:', error));
After signing in to the Umified API, you’ll receive a 200 OK response in case of successful sign in or a 401 Unauthorized error incase of invalid credentials: 
{
    "result": {
        "refresh_token": "A long-lived token used to obtain new access tokens.",
        "access_token": "The primary token (Firebase ID token) used to authenticate API requests and verify the user's identity.",
        "expires_in": "time in seconds",
        "local_id": "A unique identifier for the user in Firebase Authentication"
    },
    "message": "You are signed in successfully.",
    "status_code": 200,
    "destination": null
}