glamorous-church-16794
03/01/2026, 12:36 PMtall-airline-16756
03/01/2026, 12:36 PMtall-airline-16756
03/01/2026, 12:36 PMglamorous-church-16794
03/01/2026, 12:36 PMtall-airline-16756
03/01/2026, 12:37 PMLIVEKIT_URL, LIVEKIT_API_KEY, and LIVEKIT_API_SECRET. Here’s how to get each one.
1. Create (or open) a LiveKit Cloud project
• Sign in to https://cloud.livekit.io/ and create a new project (or open an existing project).
1. Get the API key and secret
• In your project’s Settings page you’ll see the API credentials. Copy:
◦ LIVEKIT_API_KEY
◦ LIVEKIT_API_SECRET
1. Get the LiveKit URL
• The project dashboard shows the project’s WebSocket URL. That is your LIVEKIT_URL and typically looks like:
◦ wss://<your-project-subdomain>.livekit.cloud
• For self-hosted LiveKit, use your server’s WebSocket address instead (for example <ws://localhost:7880> for a local dev server or your custom domain with TLS).
If you’d like, tell me:
• Whether you’re using LiveKit Cloud or self-hosting, and
• Which SDK/platform you’re configuring (browser, iOS, Android, or server),
and I’ll give the exact place in the dashboard to find these values and an example .env snippet you can paste into your app.
Sources: Mini tutorial: setting up a LiveKit Cloud project | Deploy LiveKit Agents with GitHub Actions | LiveKit | Build a multilingual voice agent that automatically switches languages | Li... | server-sdk-js | livekit/livekit_composite | DeepWikiglamorous-church-16794
03/01/2026, 12:37 PMtall-airline-16756
03/01/2026, 12:37 PMLIVEKIT_API_SECRET or get a new one.
A few common reasons you might not see the secret:
• The secrets are only shown in the project Settings once (for security). If you didn’t copy it when it was first generated it may be hidden afterward.
• Your account role/permissions might not allow viewing API secrets.
What to do next
1. Open your project on https://cloud.livekit.io/ and go to Settings → API keys.
2. If the secret is shown there, copy it now and store it in a secure place (this is the only time it’s fully visible).
3. If the secret is not visible:
◦ Look for a button labeled Regenerate or Create new key and use that to issue a new key pair (you’ll get a new API_KEY + API_SECRET). Copy and save the secret immediately.
◦ If you don’t see an option to create/regenerate keys, you may not have the required permissions on that project.
If you’d like, tell me:
• Whether you’re using LiveKit Cloud or a self-hosted instance, and
• Your project role (owner/admin or member),
and I’ll give exact steps for regenerating a key or guide you on where to ask within your organization for permission.