Sandbox and production

eurinvoice has two environments, sandbox and production. They are separate configurations, and a sandbox process cannot reach a production rail.

The guardCopy the link to this section

A sandbox process refuses a production rail address, and a test proves it. Each stored invoice and each event carries its environment, and a key works only in the environment it was made for. A call that names the other environment answers 400.

Each route sends through its own rail: an authority's system, a Peppol access point or a Plateforme Agréée. Routes and countries names them.

The sandboxCopy the link to this section

In the sandboxsandbox

The sandbox is live at https://api-sandbox-eu.eurinvoice.com, in Frankfurt. It has its own database, its own store for credentials and its own keys. It holds sample data only. No rail credential is stored there yet, so a route that needs one reaches submitted without anything being sent, until the rails' test systems are connected. Hosting and data says where it runs.

Getting a keyCopy the link to this section

We issue a sandbox key on request. There is no sign-up form and no portal. Production keys follow the go-live checks on what the client brings. To ask for sandbox access, see sandbox access.

ProductionCopy the link to this section

Plannedproduction

Planned: a separate production deployment with its own database, credential store and keys. It will point each route at its rail's live system. It is not built.