Bots
Send the notetaker into a meeting
Dispatches a bot to a live meeting link. Three things are worth knowing before you call it: only one bot per account can be live at a time, so a second call returns 409 and retrying will not help; it counts against the monthly recording allowance, and at the cap returns 409 with the reason; and the link must be on a supported platform. Send an Idempotency-Key so a retry after a timeout cannot start a second bot.
post
https://api-notetaker.nabrah.ai/ext/v1/botsBody
joinUrlstring · urirequiredtitlestringRequest
curl -X POST https://api-notetaker.nabrah.ai/ext/v1/bots \
-H "Authorization: Bearer $NABRAH_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"joinUrl": "string",
"title": "string"
}'Responses
201The bot was dispatched. usage carries meetings left, the minutes cap, and when limits reset.401No key, an unknown key, or one that has been revoked or has expired.403The key is read only, or lacks the reach for this route.404No such record — or one that belongs to another account.409A bot is already live for this account (ALREADY_RECORDING), a colleague's bot is in this call (TEAM_ALREADY_RECORDING), the monthly meetings are used (RECORDING_QUOTA_REACHED), or the team changed while this was being counted (USAGE_RETRY — send it again). Usage refusals are never remembered by Idempotency-Key.422The body or query failed validation; details names the field.429Too many requests. Retry-After says how long to wait.{
"data": {
"runId": "00000000-0000-0000-0000-000000000000",
"reference": "string",
"status": "string",
"phase": "string",
"usage": {
"remaining": 0,
"maxMinutes": 0,
"resetsAt": "2026-01-01T09:00:00.000Z"
}
}
}