Skip to main content

Test vs. Live mode

eCourier runs two separate environments: Test and Live. The mode controls whether traffic goes to Peppol’s and NemHandel’s test networks or their production networks.

Mode toggle in the header​

In the dashboard (when you are inside a team), the header shows a Mode control with Test and Live buttons. The active mode is highlighted.

  • Clicking Test or Live takes you to that environment’s own instance of the team workspace (separate URLs).
  • You are always clearly in one mode or the other—there is no mixed mode in the UI.

Separate data, shared teams and users​

Test and Live are two completely separate copies of the product for your team. They do not share:

  • Companies
  • Participants and network registrations
  • Documents and message history
  • Webhooks
  • API credentials

What is shared across Test and Live:

  • Teams (your organisation/workspace)
  • Users and team membership (who belongs to which team, and their roles)

So you configure participants, webhooks, and API keys independently in each mode. Something set up in Test does not exist in Live until you create it there (and vice versa).

For the REST API, the same host is used for both modes; whether a request is test or live is determined by the API key you use (pk_test_… vs pk_live_…). See API keys.

Test mode​

eCourier never sends messages to a production access point. Peppol and NemHandel test networks are used.

Recipients must be registered on the test network. If you register participants through eCourier, do that while you are in Test mode.

Live mode​

eCourier sends messages to production access points. Peppol and NemHandel production networks are used.

Recipients must be registered on the live network. Register participants through eCourier while you are in Live mode.

Documents sent in Live mode are legally relevant production traffic. Do all integration and QA in Test mode first.