Environments
Production, staging, and mock environments for the RevKeen API
RevKeen exposes separate environments for live traffic, persisted pre-production testing, and schema-only mocking.
Environment matrix
| Environment | Base URL | Auth | Purpose |
|---|---|---|---|
| Production | https://api.revkeen.com/v2 | rk_live_* via x-api-key | Live transactions and real customer data |
| Staging | https://staging-api.revkeen.com/v2 | rk_sandbox_* via x-api-key | Integration testing, QA, demos, and release validation |
| Mock | https://mock-api.revkeen.com/v2 | Auth not enforced | Schema validation, client prototyping, and CI smoke checks |
Recommended promotion path
- Start in Mock when you only need response shapes, frontend prototyping, or schema validation.
- Move to Staging when you need persisted data, webhook delivery, and realistic lifecycle testing.
- Promote to Production only after the same flows are stable in staging.
Choosing the right environment
| Scenario | Recommended environment |
|---|---|
| UI prototyping or contract validation | Mock |
| Local app integration and QA | Staging |
| End-to-end billing flow validation | Staging |
| Webhook testing | Staging |
| Real customer traffic | Production |
Environment-specific behavior
- Production creates live side effects and should only be used with live keys and real workflows.
- Staging is the default integration environment and the right place for webhook and end-to-end validation.
- Mock does not persist state, does not emit webhooks, and does not validate tenant auth.
Use Mock for shape validation. Use Staging when you need persistence, realistic lifecycle flows, or webhook testing.