Get Meeting

info

The Get Meeting endpoint provides detailed information about a specific meeting, including its metadata, participants, chat messages, and todo items.

API Endpoint

note

This endpoint requires authentication and a valid meeting ID.

[GET] /v1/integrations/meetings/:id

Request

Request Parameters

Field	Type	Required	Description
id	string	Yes	The unique identifier of the meeting to retrieve

Response

tip

All timestamp fields are returned in ISO 8601 format in UTC timezone.

Success Response (200)

A successful response returns a JSON object containing the meeting details:

{
  "id": "QPF6U3eO3YeCFZLXsIfd",
  "meeting_url": "https://",
  "status": "Completed",
  "summary": "Özet",
  "title": "Deneme",
  "user_ref": "8x",
  "language": "tr",
  "transcriptions_url": {
    "tr": "https://"
  },
  "video_duration": 50,
  "creator": {
    "email": "noreply@mesai.co",
    "self": true
  },
  "todo_items": [
    {
      "id": 1,
      "checked": false,
      "content": "1. Yazılımcıların deneyimleri ve tutumları göz önünde bulundurularak organizasyonun yazılım geliştirme ve eğitim programlarına yönelik yaklaşımının gözden geçirilmesi.",
      "creator": "AI",
      "created_at": "2024-08-08T17:36:23.129Z",
      "updated_at": "2024-08-08T17:36:23.129Z"
    }
  ],
  "chat_messages": [
    {
      "id": "c31714Zd-cb13-4bd1-800b-0474dbb27ccd",
      "message": "Dit",
      "sender": {
        "id": "300",
        "name": "Neo Mesai",
        "is_host": false
      },
      "created_at": "2024-06-10T19:08:28.251Z"
    }
  ],
  "permissions": [
    {
      "id": "ebb00c04-a667-4dac-aef5-9b0f0bcf2055",
      "email": "noreply@mesai.co",
      "role": "VIEWER",
      "created_at": "2024-04-16T14:59:42.425Z"
    }
  ],
  "participants": [
    {
      "id": "9712cf90-65c8-4785-8abf-10d5285a86e1",
      "name": "Neo Mesai",
      "duration": 57
    }
  ],
  "type": "Google",
  "start_time": "2024-08-08T17:33:43.197Z",
  "end_time": "2024-08-08T18:33:43.197Z",
  "created_at": "2024-08-08T17:33:43.297Z",
  "deleted_at": null
}

Error Response (401)

danger

This error occurs when the request is not properly authenticated or the user doesn't have permission to access the meeting.

In case of an error, the response will have the following structure:

{
  "code": -1,
  "domain": 0,
  "message": "error"
}

Response Fields

Meeting Object

Field	Type	Required	Description
id	string	Yes	Unique identifier for the meeting
meeting_url	string	Yes	URL of the meeting
status	string	Yes	Current status of the meeting (e.g., "Completed")
summary	string	No	Brief summary or description of the meeting
title	string	Yes	Title or name of the meeting
user_ref	string	Yes	Reference ID of the user associated with the meeting
language	string	Yes	Primary language code of the meeting
transcriptions_url	object	No	Object containing transcription URLs keyed by language code
video_duration	number	Yes	Duration of the meeting video in seconds
creator	object	Yes	Information about the meeting creator
todo_items	array	No	List of todo items created during the meeting
chat_messages	array	No	List of chat messages exchanged during the meeting
permissions	array	Yes	List of user permissions for accessing the meeting
participants	array	Yes	List of users who participated in the meeting
type	string	Yes	Platform where the meeting was held (e.g., "Google")
start_time	string	Yes	Start time of the meeting in ISO 8601 format
end_time	string	Yes	End time of the meeting in ISO 8601 format
created_at	string	Yes	Timestamp when the meeting was created
deleted_at	string	No	Timestamp when the meeting was deleted, or null if active

Child Objects

The response includes several nested objects and arrays. Each child object has its own structure as shown in the example response above.