Start here
Get started with Beladed APIs
Move from account setup to a verified development request, then choose the product workflow you want to build.
Before you begin
- Account
- Business and Streamer accounts operate supported products. Personal accounts use documented consumer flows.
- Environment
- Start on api.beladed.dev with isolated development resources.
- Credential
- Choose no key, a publishable key, a secret key, or an approved OAuth client based on the operation.
- Platform
- Server, web, extension, iOS, Android, and React Native have different credential boundaries.
1. Create least-privilege credentials
| Credential | Where it belongs | Use |
|---|---|---|
| No key | Any client | Explicitly public reads and redirect destinations |
| Publishable key | Approved web origin or extension | Narrow browser-safe operations; never grants administrative access |
| Secret key | Your trusted server only | Account-scoped reads and mutations |
| OAuth client | Backend authorization flow | Approved partner integrations |
Open Developer settings, select only the required products and permissions, and store the secret once in your server-side secrets manager.
2. Make a development request
curl https://api.beladed.dev/api/healthA healthy response confirms connectivity. Product operations require the credential and account eligibility shown on their reference page.
3. Choose a product workflow
Open a product guide for prerequisites, account roles, platform architecture, API operations, webhooks, testing, and production readiness.
4. Prepare production
- Complete product onboarding and required verification.
- Create production-scoped credentials.
- Verify allowed origins and webhook signatures.
- Exercise retries and idempotency in development.
- Switch host and credentials together; never mix environments.