Building with confidence: Introducing the B2Brouter sandbox
Last updated: 8 de June de 2026
When integrating a new API or testing invoice workflows, the last thing you want to worry about is accidentally sending a test document to a real client—or paying for test transactions.
That is why we are thrilled to introduce the B2Brouter sandbox, an isolated test environment that lets you try B2Brouter without touching real data, real recipients, or your subscription’s transaction count.
What is the B2Brouter sandbox?
The sandbox is not a pre-release or staging version of B2Brouter ; it runs the exact same code as our production environment. Only the data and outbound integrations differ.
Each sandbox is a completely self-contained workspace with its own data. Your invoices, contacts, products, templates, and API keys all live separately from your production account. Anything you create in the sandbox stays in the sandbox, ensuring your live production data remains pristine.
Core benefits: Why you will love building here
We designed the sandbox to remove friction from your development and testing cycles. Here is what you can expect:
- Zero impact on billing: Sandbox usage does not count toward your production subscription’s transaction quota. Sandbox traffic is fully separated from production billing.
- Unrestricted access: In sandbox mode, all eDocExchange-tier features are available regardless of your real subscription. Transaction count limits, user count limits, and product entitlement checks are lifted.
- Guaranteed safety: Outbound integrations are simulated only. No emails are sent , your documents are not transmitted over the PEPPOL network , and nothing you do reaches a production tax authority.
- Clear distinctions: To prevent any mix-ups, invoices and quotes downloaded from the sandbox carry a clear “No vàlida” watermark. This makes test documents impossible to mistake for real ones.
- Throwaway convenience: You can delete and recreate sandboxes freely. There is no charge for using them , and you can manage up to 5 active sandboxes per account or integration group.
Top use cases: How to leverage the sandbox
Whether you are a developer writing integration code or a sales engineer doing a product demo, the sandbox is built for you. It is perfect for:
- Trying B2Brouter end-to-end before committing to a paid plan.
- Validating your API integration before pointing it at production.
- Running training, demos, or proof-of-concept work without affecting your live data.
- Walking documents through their lifecycle (draft → sent → registered) so your integration code can exercise the success path of the state machine.
- Testing webhooks. Webhooks fire from the sandbox , and if you configure a webhook URL on a sandbox integration group, you will receive calls there as document states change.
Getting started
One of the best parts about the B2Brouter sandbox is how easy it is to interact with the API. There is no separate sandbox URL and no environment header to set.
Sandbox routing is driven entirely by the API key. Sandbox keys start with test_. When you call an endpoint with a test_ key, your request is automatically served from the sandbox environment. It is that simple!