Overview
The Streambird Auth API uses Bearer token authentication. All Users, Phone Numbers, Emails, and OTPs are associated with anApp as the container.
Most endpoints require your App’s Secret API Key, while certain client-side endpoints (used via SDK) accept a Public Token instead.
API Keys
Streambird provides two types of API keys:- Secret API Keys (
sk_test_...orsk_live_...) - Used for server-side API calls. Keep these secure and never expose them in client-side code. - Public Tokens - Used for client-side SDK integration. Safe to use in frontend applications.
Never share your secret API keys in publicly accessible areas such as GitHub, client-side code, or browser inspector.
Making Authenticated Requests
Include your API key in theAuthorization header of your requests using the Bearer scheme:
Header Format
Example Request
Example with JavaScript
Example with Python
Test vs Live Keys
- Test Keys (
sk_test_...) - Use these keys for development and testing. They won’t affect production data. - Live Keys (
sk_live_...) - Use these keys for production. All operations will affect real users and data.
Getting Your API Keys
You can find your API keys in the Streambird Dashboard:- Log in to your Streambird Dashboard
- Navigate to Settings → API Keys
- Copy your test or live API key
- Use it in your API requests as shown above
Rotate your API keys regularly and immediately revoke any keys that may have been compromised.

