Getting started
Single Sign-On
How to sign in to your account, where API keys live, and how team workspaces share access.
Every API request authenticates with an rtvk_ API key, and API keys are created in the web dashboard. This page covers how you and your teammates sign in to that dashboard, where keys are managed, and how access is shared on a team plan.
Sign-in methods
Sign in at realtimevoicekit.com/en/login with any of three methods. All three reach the same account and dashboard.
| Method | How it works |
|---|---|
| Email and password | Create an account with your work email, verify it through the confirmation email, and sign in with your password. Password resets are self-serve from the login page. |
| Sign in with Google | One-click sign-in with your Google account. If you have no account yet, one is created on first sign-in with the same email. |
| Sign in with GitHub | One-click sign-in with your GitHub account, convenient for developer teams. An account is created on first sign-in. |
Where your API keys live
API keys are managed in the developer section of the dashboard at realtimevoicekit.com/en/app/v2. From there you can create a key, name it after the service or environment that will use it, and revoke it at any time.
- Keys start with the
rtvk_prefix and are sent asAuthorization: Bearer rtvk_your_api_keyon every request. - The full key is shown exactly once, at creation. Only a short prefix is displayed afterwards, so store the key in your secret manager immediately.
- Keys are stored hashed on the server; a lost key cannot be recovered, only replaced.
- Revocation is immediate: requests with a revoked key stop authenticating.
API key security
- Server-side only. Never ship an API key in browser JavaScript, mobile apps, or public repositories. Calls belong on your backend, which holds the key in an environment variable or secret manager.
- One key per environment. Separate keys for development, staging, and production keep a leaked test key from exposing production and make revocation painless.
- Rotate without downtime. Create the replacement key, deploy it, confirm traffic authenticates, then revoke the old key.
- Revoke first, investigate second. If a key may have leaked, revoke it in the dashboard immediately; a fresh key is one click away.
- Name keys after their consumer. A key named billing-worker-prod is easy to audit and safe to revoke; a key named test-2 is neither.
Team workspaces
On the Teams plan, your account can run a shared workspace with 5 seats included. Teammates are invited by email from the dashboard, sign in with their own account using any of the methods above, and share access to the workspace and its transcripts. There are no shared passwords: each member keeps an individual identity, and removing a member removes their access without touching anyone else.
- The workspace entitlement comes from the owner's Teams subscription; invited members do not need their own paid plan for workspace access.
- Invites are sent to email addresses, so they work regardless of whether the invitee signs in with a password, Google, or GitHub.
- The Teams plan includes 5 workspace seats.
Need help?
For sign-in or access questions not covered here, including larger team requirements, email support@realtimevoicekit.com.