ScribeberryScribeberry Docs

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.

SettingValue
Base URLhttps://sandbox.api.scribeberry.com
Key prefixsk_test_
BillingFree / not charged
Rate limitsRelaxed (100 req/min)
Data retention30 days
const sb = new Scribeberry({
  apiKey: 'sk_test_...',
  baseUrl: 'https://sandbox.api.scribeberry.com',
});

Production

The production environment is for live, customer-facing traffic. Requests are metered and billed according to your plan.

SettingValue
Base URLhttps://api.scribeberry.com
Key prefixsk_live_
BillingActive (per your plan)
Rate limitsPer plan (default: 60 req/min)
Data retentionPer your agreement
const sb = new Scribeberry({
  apiKey: 'sk_live_...',
  // baseUrl defaults to https://api.scribeberry.com
});

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 the baseUrl override.

  1. Develop with sandbox keys and the sandbox base URL
  2. Test your integration end-to-end in sandbox
  3. Deploy by switching to sk_live_ keys and removing the baseUrl override
  4. Monitor usage in the Scribeberry Console →

On this page