Environments
B2Brouter has three environments. Choose based on what you are trying to do.
| Environment | Base URL | API key prefix | When to use |
|---|---|---|---|
| Sandbox | https://api.b2brouter.net | test_… | Daily development, payload validation, onboarding, small integrations |
| Staging | https://api-staging.b2brouter.net | stag_… | Large integrations, cross-system tests, high-volume simulations, full end-to-end flows |
| Production | https://api.b2brouter.net | prod_… (or no prefix for legacy) | Live traffic |
Sandbox — start here
Section titled “Sandbox — start here”Sandbox is the recommended environment for initial development and day-to-day testing. It is isolated, free to use, and available immediately — no setup ticket required.
Key properties:
- Uses the same base URL as production (
https://api.b2brouter.net). Routing to sandbox is determined entirely by the API key: keys starting withtest_go to sandbox; all others go to production. - Outbound sends (email, PEPPOL, tax authority submissions) are simulated — documents advance through their lifecycle without contacting any real system.
- All eDocExchange features are available regardless of your real subscription.
- Usage does not count against your production transaction quota.
See Sandbox for setup instructions and a full feature reference.
Staging — for large or broad integrations
Section titled “Staging — for large or broad integrations”Staging is a full-stack test environment with its own domain (api-staging.b2brouter.net) and its own database. Use it when:
- You need to test a large integration with multiple accounts, high transaction volumes, or complex cross-system flows.
- You need a persistent shared environment across a development team.
- You are integrating with a country-specific authority whose own test endpoint (DGFiP QAS, KSeF test, ZATCA sandbox, etc.) connects to B2Brouter’s staging environment.
To get started with staging, register on the staging app and then open a support ticket to request the necessary API permissions — staging accounts start with limited access.
Note. For everything else — trying the API, validating payloads, writing integration tests, onboarding — use Sandbox instead. Staging requires more setup and is better suited for broader test scenarios.
Production
Section titled “Production”Live environment. All real transactions, billing, and PEPPOL registrations happen here. Do not use for development or testing.