Documentation Index
Fetch the complete documentation index at: https://docs.stagingspaces.app/llms.txt
Use this file to discover all available pages before exploring further.
Authentication
The StagingSpaces API uses two authentication methods depending on the endpoint.API Key Authentication
Used for: Staging, enhancement, credits, and all programmatic access. Pass your API key as a Bearer token in theAuthorization header:
Key format
| Environment | Format | Example |
|---|---|---|
| Production | sk_live_... | sk_live_a1b2c3d4e5f6g7h8 |
| Test | sk_test_... | sk_test_x9y8z7w6v5u4t3s2 |
Getting a key
- Sign up at studio.stagingspaces.app
- Go to Settings → API
- Click Generate API Key
- Save the key — it’s only displayed once
Key security
- Keys are stored as SHA-256 hashes (we never store the plaintext)
- Each key tracks
last_used_atfor audit - Revoked keys are immediately invalid
- Test keys (
sk_test_) work identically but are labeled for development
Firebase Authentication
Used for: Dashboard operations — key management, claims, usage stats, settings. These endpoints are designed for browser-based access from the StagingSpaces dashboard. If you’re building a server-to-server integration, you only need API key auth.Endpoint Auth Summary
| Endpoint | Auth Method |
|---|---|
POST /api/v1/stage | API Key |
POST /api/v1/enhance | API Key |
POST /api/v1/place-products | API Key |
GET /api/v1/credits | API Key |
POST /api/v1/keys | Firebase |
GET /api/v1/keys | Firebase |
DELETE /api/v1/keys/{id} | Firebase |
POST /api/v1/claim | Firebase |
GET /api/v1/usage | Firebase |
GET/PUT /api/v1/settings/* | Firebase |
GET/PUT /api/v1/keys/{id}/webhook | Firebase |
GET /api/health | None |