Dashboard
API Keys
Manage API keys for SDK authentication
API Keys
API keys authenticate your application with the Owostack API. Each key is scoped to a specific organization.
Creating an API Key
- Go to API Keys in the sidebar
- Click Create API Key
- Enter a name for the key (e.g., "Production Server")
- Copy the key immediately - it's only shown once!
Security: API keys are shown only once at creation. Store them securely. If lost, create a new key and revoke the old one.
Key Format
Owostack API keys follow this format:
owo_sk_xxxxxxxxxxxxxxxxxxxxowo_- Owostack prefixsk_- Secret key indicatorxxxx...- Unique identifier
Using API Keys
In the SDK
import { Owostack } from "@owostack/core";
const owo = new Owostack({
secretKey: process.env.OWOSTACK_SECRET_KEY,
});Direct API Calls
curl https://api.owostack.com/v1/check \
-H "Authorization: Bearer owo_sk_your_key_here" \
-H "Content-Type: application/json" \
-d '{"customer": "user_123", "feature": "premium"}'Key Management
Viewing Keys
The dashboard shows:
- Key name and creation date
- Last used timestamp
- First 7 characters (masked)
Revoking Keys
- Click the ⋮ menu next to the key
- Select Revoke
- Confirm the action
Revoking a key immediately invalidates it. Any applications using that key will receive 401 errors.
Best Practices
- Use environment variables - Never hardcode keys in source code
- Rotate regularly - Create new keys periodically
- Separate by environment - Use different keys for dev/staging/prod
- Descriptive names - Name keys by their use (e.g., "Vercel Production")