Documentation Index
Fetch the complete documentation index at: https://docs.vexa.ai/llms.txt
Use this file to discover all available pages before exploring further.
Vexa uses user-provided meeting identifiers. You always pass:
platform (google_meet | teams | zoom)native_meeting_id (format depends on the platform)
Microsoft Teams meetings also require:
passcode (the ?p= value from the Teams link)
Google Meet
Microsoft Teams
Zoom
Use the meeting code from the URL:
- URL:
https://meet.google.com/abc-defg-hij
native_meeting_id: abc-defg-hij
Google Workspace accounts may use custom nickname URLs (e.g. https://meet.google.com/my-team-standup). These are also supported.Example request body:{
"platform": "google_meet",
"native_meeting_id": "abc-defg-hij"
}
Teams requires both the numeric meeting ID and the p= value.
- URL:
https://teams.live.com/meet/1234567890123?p=YOUR_PASSCODE
native_meeting_id: 1234567890123passcode: YOUR_PASSCODE
Enterprise URLs (teams.microsoft.com, gov.teams.microsoft.us) and deep link formats are also supported. See Teams platform docs for the full list.Example request body:{
"platform": "teams",
"native_meeting_id": "1234567890123",
"passcode": "YOUR_PASSCODE"
}
Use the numeric meeting ID (9-11 digits). If your link has ?pwd=..., you can pass it as passcode.
- URL:
https://us05web.zoom.us/j/12345678901?pwd=...
native_meeting_id: 12345678901passcode: optional (pwd=...)
ZoomGov URLs (zoomgov.com) are also supported.Example request body:{
"platform": "zoom",
"native_meeting_id": "12345678901",
"passcode": "OPTIONAL_PWD"
}
