Overview

recallai({ key: process.env.RECALLAI_API_KEY, region: 'eu-central-1' })

• Region. One of us-west-2, us-east-1, eu-central-1 or ap-northeast-1. A pasted host such as eu-central-1.recall.ai is read as its region; any other value is rejected, so requests only ever go to the four Recall hosts. Without a region, requests go to us-west-2. A 401 usually means the key and the region do not match.
• Bots cost money. bots.create sends a bot to the meeting, and Recall bills for its time there. Without join_at, or with one less than 10 minutes out, the bot joins right away; Recall recommends scheduling at least 10 minutes ahead. bots.update and bots.delete work only on a scheduled bot that has not joined yet.
• In-call actions. The botActions calls (chat, recording, pinning, audio, video and screenshare output) need the bot in the call; otherwise Recall answers 400. The calls that start something return the updated bot; the stop*Output* and stopScreenshare calls return nothing. leaveBotCall and deleteBotMedia cannot be undone.
• Transcripts after the call. recordings.createTranscript takes the provider as an object keyed by provider name, for example { recallai_async: { language_code: 'en' } }. Recall allows five a minute per bot.
• Calendar V1. The meeting calls (calendar.listMeetings, retrieveMeeting, updateMeeting, refreshMeetings) and the user calls (calendar.retrieveUser, updateUser, deleteUser, disconnectPlatform) act for one calendar user and take their calendar_auth_token. Get it from calendar.authenticate; it is valid for a day. Calendar V2 (calendars.* and the calendar event calls) uses the API key alone.
• Paging. bots.list pages by page number, or by cursor when you pass use_cursor. calendar.listUsers returns every user unless you pass paginate: true; then it pages by page number. The other lists return next as a URL; pass its cursor value back to get the next page.
• Rate limits. Most lists allow 60 requests a minute per workspace. A 429 is retried up to five times, waiting for Recall’s Retry-After.
• Webhooks. The plugin does not receive Recall’s webhooks. Bot and recording status changes arrive there; Recall asks integrations not to poll bots.list for them.
• No local data. Every call returns live data from Recall.

• 111 typed API operations

​

Setup

npm install corsair @corsair-dev/recallai

yarn add corsair @corsair-dev/recallai

pnpm install corsair @corsair-dev/recallai

bun add corsair @corsair-dev/recallai

import Database from 'better-sqlite3';
import { createCorsair } from 'corsair';
import { recallai } from '@corsair-dev/recallai';

export const corsair = createCorsair({
	plugins: [
		recallai(),
	],
	database: new Database('corsair.db'),
	kek: process.env.CORSAIR_KEK!,
	hub: {
		projectApiKey: process.env.CORSAIR_API_KEY!,
		signingSecret: process.env.CORSAIR_SIGNING_SECRET!,
	},
});

recallai()

const { connectUrl } = await corsair.manage.connect.createLink({
	plugin: 'recallai',
	tenantId: 'acme',
});
// redirect the user's browser to connectUrl

​

Example API calls

const tenant = corsair.withTenant('acme');
await tenant.recallai.api.bots.list({
	status: ['done'],
});

const tenant = corsair.withTenant('acme');
await tenant.recallai.api.bots.create({ meeting_url: 'https://meet.google.com/abc-defg-hij', bot_name: 'Meeting Notetaker' });

​

What’s next