Sandbox and production
Every Brrndops business has two completely separate environments. Your API key decides which one a request uses; there is no separate URL or flag.
| Sandbox | Production | |
|---|---|---|
| Key prefix | bd_test_ |
bd_live_ |
| Cost | Free | Billed against your plan |
| Requirements | None | Verified business and an active plan |
| Invoice numbers | TEST-INV-001, TEST-INV-002… |
INV-001, INV-002… |
| PDFs | Watermarked TEST | Clean |
POST /invoices/{id}/send |
Status changes, no email is sent | Emails your customer |
livemode on objects |
false |
true |
Data never crosses over
Section titled “Data never crosses over”Sandbox and production data are fully isolated. A sandbox key asking for a production invoice gets 404,
and the reverse is also true. Lists, numbering and request logs are separate too. Nothing you do in sandbox can
affect a real customer.
Recommended setup
Section titled “Recommended setup”- Use sandbox keys in development, CI and staging, and production keys only in production.
- Keep keys in environment variables or a secrets manager, never in source code.
- Because the request format is identical in both environments, going live is just a key swap.
The developer dashboard has the same switch at the top of every page, so you can view sandbox and production activity separately.