Skip to main content
POST
cURL

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.

Pattern: ^s3://notetaker-transcripts-prod-032265101474-eu-west-1(?:/[A-Za-z0-9!\.\_\-\*'\(\)]+)*/$
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.

Pattern: ^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(?:\.\d+)?(?:Z|[+\-]\d{2}:\d{2})$
Example:
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.

Pattern: ^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(?:\.\d+)?(?:Z|[+\-]\d{2}:\d{2})$
Example:
bot_name
string

OPTIONAL - Custom name for the bot.

client_code
string

OPTIONAL - Client code for identifying the user

Example:

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