Meeting Metadata
Recall.ai exposes metadata for a given meeting as media object on a recording.
Examples of meeting metadata include meeting title and unique identifiers, though the specific metadata available depends on the platform.
Configuration
To configure a bot to record meeting metadata, provide a meeting_metadata
object in your Create Bot request's recording_config
:
curl --request POST \
--url https://us-east-1.recall.ai/api/v1/bot/ \
--header "Authorization: $RECALLAI_API_KEY" \
--header "accept: application/json" \
--header "content-type: application/json" \
--data '
{
"meeting_url": "https://meet.google.com/gtt-vjsi-jhj",
"recording_config": {
"meeting_metadata": {}
}
}
'
Retrieving Meeting Metadata
Platform Support
Platform | Supported? | |
---|---|---|
Zoom | ✅ | |
Google Meet | ⚠️ | Only works if: - Bot is signed - Bot is a participant on the calendar event - Calendar event's end time is in the future |
Microsoft Teams | ❌ | |
Cisco Webex | ❌ | |
Slack Huddles | ✅ |
To retrieve meeting metadata for a recording, you can either:
- Call Retrieve Bot and access the metadata in
shortcuts.meeting_metadata.data
in the recording object - Call Retrieve Meeting Metadata, using the ID of the meeting metadata artifact
- Call List Meeting Metadata, filtering to a specific recording ID
Google Meets
The Microsoft Teams title will only be populated if the bot is signed in and the bots email on the calendar meeting invite
{
"data": {
"title": "John Smith's Personal Meeting Room",
},
},
...
}
Zoom
{
"data": {
"title": "John Smith's Personal Meeting Room",
"zoom_meeting_uuid": "x7OAB2GkQmFZuNhAY+nTNg=="
},
},
...
}
Slack Huddles
{
"data": {
"huddle_id": "...",
"channel_id": "..."
},
},
...
}
Updated 2 days ago