Get started with the Podium API
Create your API key, secure it, and start building
One place to learn, create, store, and pay for access — with best practices baked in: orgs, roles, usage tracking, and rotation.
1. Sign in
Create org or join existing; verify email; enable 2FA.
2. Billing
Choose plan, add card, set spend caps.
3. API Keys
Create, scope, and store secrets securely.
4. Build
Use quickstarts; monitor usage & limits.
API Keys
Create, scope, and manage keys. This is a demo UI — wire to your backend routes.
Tip: Use separate keys per environment and service.
Server Prod pod_live_3f9a…
Scopes: orders:write, payments:write, events:read • IP: 203.0.113.0/24
Created: 2025-10-10 • Last used: 2025-10-25
Key best practices
Security tips you can enforce via policy.
- Use separate keys per environment and microservice.
- Scope keys to least privilege (read vs. write).
- Rotate quarterly or on incident; audit last-used.
- Use IP allowlists for server keys; never expose client-side.
- Store in your secrets manager; never commit to Git.
Environment variables
# .env
PODIUM_API_KEY=pod_live_***
PODIUM_ENV=productionUsage & limits
Monitor requests per day, rate limits, and spend caps. Export CSV or subscribe to webhooks.
12,450
Requests this month
1,000 req/min
Rate limit
$1,000
Spend cap
Explore More
Learn about the platform, features, or dive deeper into documentation