Environments
Sandbox and production environments for the Scribeberry API.
Scribeberry provides two isolated environments for development and production use.
Sandbox
The sandbox environment is for development, testing, and integration work. It's fully functional but processes are not billed.
| Setting | Value |
|---|---|
| Base URL | https://sandbox.api.scribeberry.com |
| Key prefix | sk_test_ |
| Billing | Free / not charged |
| Rate limits | Relaxed (100 req/min) |
| Data retention | 30 days |
Production
The production environment is for live, customer-facing traffic. Requests are metered and billed according to your plan.
| Setting | Value |
|---|---|
| Base URL | https://api.scribeberry.com |
| Key prefix | sk_live_ |
| Billing | Active (per your plan) |
| Rate limits | Per plan (default: 60 req/min) |
| Data retention | Per your agreement |
Environment Isolation
Sandbox and production are completely isolated:
- Templates created in sandbox do not exist in production (and vice versa)
- API keys from one environment will not work in the other
- Usage in sandbox does not count toward your production billing
- Data is stored separately
ℹ️ Info: When you're ready to go live, create new templates in the production environment and update your API key to
sk_live_. Your integration code stays the same — just swap the key and remove thebaseUrloverride.
Recommended Workflow
- Develop with sandbox keys and the sandbox base URL
- Test your integration end-to-end in sandbox
- Deploy by switching to
sk_live_keys and removing thebaseUrloverride - Monitor usage in the Scribeberry Console →