Skip to navigation

Dashboard Setup

Create your account and API key, then find your way around the MeetStream dashboard
View as Markdown

Sign up, create an API key and send your first request in a few minutes. This page also walks through each part of the dashboard so you know where every setting lives.

Get your API key

1

Create an account

Sign up for MeetStream and sign in to the dashboard at app.meetstream.ai. New accounts see a short onboarding wizard the first time they sign in.

2

Create an API key

In the sidebar, under Configure, open API Keys and click + New API Key. Give it a Key name (for example “Production” or “local dev”) and create it.

The full key is shown once, in the “Your API key is ready” dialog. Copy it into your secrets manager or .env file before you close the dialog; MeetStream cannot show it again. You can revoke a key at any time; revoked keys stop working immediately.

3

Authenticate your requests

Send the key in the Authorization header, with the Token prefix, on every call to https://api.meetstream.ai/api/v1/:

curl "https://api.meetstream.ai/api/v1/bots" \
-H "Authorization: Token <YOUR_API_KEY>"

API keys are scoped to a workspace. Bots, webhook endpoints and usage belong to the workspace whose key created them, so create keys in the workspace you plan to use. See Workspaces.

Ready to send a bot? Continue with Create your first bot, or try it without code in the API Playground.

Tour the dashboard

MeetStream dashboard Overview page with the Bots, Configure and Billing and Usage sidebar sections, the Viewing workspace switcher and the Create API Key, Create Webhook and Integrations quick actions highlighted
The sidebar groups: Bots (1), Configure (2), Billing & Usage (3), the workspace switcher (4), and the Overview quick actions (5)

Overview is the home page. Its quick actions (5) jump to Create API Key, Create Webhook and Integrations, and Try API Playground launches a bot from the browser.

The sidebar has three groups:

GroupPageWhat you do there
Bots (1)All BotsEvery bot in the workspace, with status, duration and a detail view per bot
API PlaygroundBuild a create_bot request with a form, send it live and see the JSON
Configure (2)API KeysCreate and revoke API keys
WebhooksWorkspace webhook endpoints and the delivery log (guide)
IntegrationsTranscription and AI provider keys, custom storage, signed-in bots and Zoom credentials
CalendarConnect Google or Outlook calendars and turn on auto-join (Google, Outlook)
AgentsMIA voice agents that can speak in meetings (What is MIA?)
WorkflowNot available yet (“Workflows are on the way”)
TeamInvite members and set their roles
Billing & Usage (3)UsageHours and cost per bot (Usage & Retention)
BillingCredits and payments

The Viewing workspace switcher (4) at the bottom of the sidebar changes the workspace you are looking at. API Docs opens this documentation, and your name opens the user menu with Settings.

What you see depends on your workspace role (viewer, editor, admin, owner). API Playground and Workflow need editor or higher, API Keys and Team need admin or higher, and Billing is for the owner.

All Bots

All Bots page with the Total bots, Total hours, Active now and Scheduled bots tiles, the date, platform and status filters, the Events, CSV and Refresh buttons, and the Status column highlighted
All Bots: summary tiles (1), filters and search (2), Events, CSV export and Refresh (3), and each bot's status (4)
  • Summary tiles (1): totals for the current result set, bots active right now and bots scheduled to join.
  • Filters (2): Any date, All platforms and All statuses, plus search by bot ID, name or meeting URL. Local and UTC switch the time zone of the start times.
  • Events (3) opens a reference of bot events, CSV exports the list and Refresh reloads it.
  • Status (4): the badge shows a friendly label; hover it to see the exact API status (for example API status: NotAllowed).

Click a row to open the bot’s detail page: start and stop times, platform, the Bot status timeline (every stage from Joining to Done, with the reason if the bot did not get in), and tabs for the transcript, screenshots, participants, chats, audio and video streams, Webhook Logs and Raw Data. The timeline’s stages and reasons are explained in the status and error code reference and Debugging Bots.

Integrations

Integrations page on the Transcription tab with the tab bar, the Mia Transcribe card and a Deepgram card marked Connected highlighted
Integrations: the tabs (1), MeetStream's native transcription (2), and a provider whose key is saved, marked Connected (3)

The tabs (1) are Transcription, Voice, Models, Avatar, Storage, Signed Bots, Teams Bots, Zoom and WhatsApp (Beta).

TabUse it to
TranscriptionSave your own keys for Deepgram, Assembly AI, JigsawStack or Sarvam AI, so bots can use them. Mia Transcribe (Native Transcription) (2) needs no key: select it in the bot request. Saved providers show Connected (3). See Transcription Providers.
Voice, Models, AvatarKeys for the voice, language model and avatar providers that MIA agents use
StorageSend recordings to your own bucket: Amazon S3 or Alibaba Cloud OSS
Signed BotsGoogle Meet bots that sign in to a Google account (guide)
Teams BotsMicrosoft Teams bots that sign in to a Microsoft account (guide)
ZoomYour Zoom app’s Client ID and Client Secret, required for Zoom bots (guide)

Per-platform setup

Zoom bots join through a Zoom app that you own. Create it in the Zoom App Marketplace, then save its Client ID and Client Secret under Integrations > Zoom. Follow Zoom Marketplace App Setup, then read the Zoom platform guide for supported links, the waiting room and recording permission.

No setup is needed for bots that join as guests. If your meetings only admit signed-in users, set up Google Signed-In Bots. See the Google Meet platform guide for admission rules.

No setup is needed for bots that join as guests. If your tenant blocks anonymous participants, set up Microsoft Teams Signed-In Bots. See the Microsoft Teams platform guide for lobby rules.

Before you go live

  • Add a webhook endpoint under Configure > Webhooks so you hear about every bot’s status and recordings without polling. Use a public HTTPS URL and store the signing secret. See Workspace Webhook Endpoints.
  • Test with real meetings. Bots you launch from the dashboard or the API are real bots and use your credits. Tunnels such as ngrok help you receive webhooks on your laptop (Set Up Local Server for Webhook).
  • Use the SDKs if you like. Official Node.js and Python SDKs wrap the same REST API (Official SDKs).

Need help? See Get Support, the FAQ or Debugging Bots. What changed recently is in the Changelog.