Dashboard Setup
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
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.
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.
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

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:
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

- 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

The tabs (1) are Transcription, Voice, Models, Avatar, Storage, Signed Bots, Teams Bots, Zoom and WhatsApp (Beta).
Per-platform setup
Zoom: add your Zoom app credentials first
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.
Google Meet: works out of the box
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.
Microsoft Teams: works out of the box
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
ngrokhelp 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.
