Skip to content

Environments

Ditio has a test and a production environment, each with its own hosts and its own credentials. A client created in production does not work in test, and vice versa. Every page in this documentation takes its URLs from the same source as the table below, so they always match it.

API Production Test Token scope
Integration API https://integration.ditio.no https://core-api.ditio.dev/core ditioapiv3
Reporting (Data Extraction) API https://integration.ditio.no/reporting https://core-api.ditio.dev/reporting reportingapiv1
Mass Transport (Machine Integration) https://core-api.ditio.app/masstransport https://core-api.ditio.dev/masstransport masstransportapiv1
Identity (token endpoint host) https://identity.ditio.app https://identity.ditio.dev None. This host only issues tokens.
SCIM provisioning (Tenant URL) https://integration.ditio.no/scim https://core-api.ditio.dev/scim None. SCIM uses the tenant token Ditio issues for your Microsoft Entra tenant.

The identity host is where you fetch tokens (/connect/token); see Authentication. Which scope each API needs is in Which scope for which host.

Test Build and verify here first Integration core-api.ditio.dev/core Reporting core-api.ditio.dev/reporting Mass Transport core-api.ditio.dev/masstransport Identity identity.ditio.dev Production Live customer data Integration integration.ditio.no Reporting integration.ditio.no/reporting Mass Transport core-api.ditio.app/masstransport Identity identity.ditio.app

All code samples in this documentation read their base URLs from environment variables and default to test, so you switch environments in one place. The variables and their test and production values are in Authentication.