Developers / test environments

Isolated test environments

Use a separate test machine client for API calls or a separate product human session for the browser Explorer. Both use api.test.d0.eu with product-specific audiences. Production credentials cannot be reused. The Console reports a service outage explicitly when a test runtime is unavailable.

Open Test Explorer →

The Explorer requires sign-in. The references below are public.

Platform DNS

Activate an organization-owned .test domain, then read and change persistent simulated DNS records. Registrar, public DNS, orders, S3 and clusters are excluded.

https://api.test.d0.eu/platform/v1

Read DNS test reference →

Accounting

Activation seeds synthetic accounts and a period. Explore accounts, periods, draft entries and trial balance. Posting, external delivery and webhooks are closed.

https://api.test.d0.eu/accounting/v1

Read Accounting test reference →

E-Invoice

Commission a trusted validation policy, store the fixed UBL fixture, then queue a real test validation and inspect its findings. Issuance is disabled.

https://api.test.d0.eu/einvoice/v1

Read E-Invoice test reference →

ERiC

The human Explorer lists fixed synthetic outcomes. A separate test machine client with DPoP can run simulations. Native execution and transmission stay disabled.

https://api.test.d0.eu/eric/v1

Read ERiC test reference →

Machine access uses dedicated test resources and product scopes. Register its public key at d0 identity; keep private keys outside the browser. Each product checks the current organization and its own local permissions. The API bases above include /v1; use the exact OAuth resource in each reference when requesting a token.