Skip to main content
POST
/
create_meeting
cURL
curl --request POST \
  --url https://api.umified.com/api/v1/create_meeting/ \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: multipart/form-data' \
  --form 'meeting_url=<string>' \
  --form 'meeting_name=<string>' \
  --form 'destination_path=<string>' \
  --form start_datetime=2023-11-07T05:31:56Z \
  --form end_datetime=2023-11-07T05:31:56Z \
  --form 'bot_name=<string>' \
  --form 'client_code=<string>'
{
  "result": {
    "bot_name": "Umified Bot",
    "session_id": "umifiedpdin20250422061939541365"
  },
  "message": "Your meeting is created successfully.",
  "status_code": 201,
  "destination": null
}

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

multipart/form-data

Details in form-data.

meeting_url
string
required

Meeting URL - Google Meet, Zoom or Teams.

Note: Teams meeting URL shall be in below format https://teams.live.com/meet/{meeting-id}?p={passcode}. Example: https://teams.live.com/meet/0123456789123?p=Ab12aBa1

meeting_name
string
required

A Meeting name.

destination_path
string

For Authorised Partners Only

Optional. S3 destination for meeting transcript file upload (must end in /). E.g. s3://bucket_name/ or s3://bucket-name/folder-name/. Here, bucket_name is the name of your S3 prod bucket.

Post meeting, once transcription is completed, the transcript file will be uploaded to: <destination_path>/<meeting-session-id>/meeting-transcript.txt.

start_datetime
string<date-time>

Required for Scheduled Meeting. Start datetime shall be strictly in ISO-8601 with timezone offset (+HH:MM). Examples: 2025-05-05T14:30:00.123456+05:30, 2025-05-05T14:30:00+04:00, 2025-05-05 14:30:00-05:00.

end_datetime
string<date-time>

Required for Scheduled Meeting. End datetime shall be strictly in ISO-8601 with timezone offset (+HH:MM). Examples: 2025-05-05T14:30:00.123456+05:30, 2025-05-05T14:30:00+04:00, 2025-05-05 14:30:00-05:00.

bot_name
string

OPTIONAL - Custom name for the bot.

client_code
string

OPTIONAL - Client code for identifying the user

Response

Response

result
object
required
message
string
required
Example:

"Your meeting is created successfully."

status_code
integer
required
Example:

201

destination
string | null
required
Example:

null