Meetings Search

info

The Meetings Search API provides a comprehensive way to retrieve and search through your meeting records with built-in pagination support. This endpoint is particularly useful for applications that need to display meeting history or analyze meeting data.

tip

For optimal performance, consider keeping the per_page parameter between 10 and 50. This helps balance between response time and data volume.

API Endpoint

note

All API requests must be authenticated using your API key in the request headers.

[POST] /v1/integrations/meetings/search

Request

info

The endpoint supports pagination by default to help you manage large datasets efficiently and improve response times.

Request Body

caution

Always validate the page and per_page parameters in your client application to ensure they are positive integers.

The request accepts a JSON object with the following parameters:

{
  "page": 1,
  "per_page": 20
}

Parameter	Type	Description
page	integer	The page number to retrieve (starts from 1)
per_page	integer	Number of items to return per page

Success Response (200)

A successful response returns a JSON object containing:

{
  "page": 1,
  "per_page": 10,
  "total": 55,
  "data": [
    {
      "id": "QPF6U3eO3YeCFZLXsIfd",
      "meeting_url": "https://",
      "status": "Completed",
      "summary": "Özet",
      "title": "Deneme",
      "user_ref": "8x",
      "language": "tr",
      "transcriptions_url": {
        "tr": "https://"
      },
      "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-08T17:33:43.197Z",
      "created_at": "2024-08-08T17:33:43.297Z",
      "deleted_at": null
    }
  ]
}

Error Response (401)

danger

Always handle authentication errors appropriately in your application. If you receive a 401 error, your API key may be invalid or expired.

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

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

Response Fields

info

Understanding the response structure is crucial for properly parsing and utilizing the API data in your application.

Main Response Object

Field	Type	Description
page	integer	Current page number
per_page	integer	Number of items per page
total	integer	Total number of items available
data	array	Array of meeting objects

Meeting Object

note

All timestamps in the response are in ISO 8601 format and in UTC timezone.

Field	Type	Description
id	string	Unique identifier for the meeting
meeting_url	string	URL of the meeting
status	string	Meeting status (e.g., "Completed")
summary	string	Brief summary of the meeting
title	string	Meeting title
user_ref	string	User reference ID
language	string	Language code of the meeting
type	string	Meeting platform (e.g., "Google")
start_time	string	Meeting start time (ISO 8601)
end_time	string	Meeting end time (ISO 8601)
created_at	string	Creation timestamp (ISO 8601)
deleted_at	string	Deletion timestamp (ISO 8601) or null