Sandbox and Environment Copy for Testing eLogii Integration with Current Systems

What this means for distribution businesses

Changing import rules or notification templates on your live system is risky. The sandbox environment provides a separate testing space with its own API endpoint at api-sandbox.elogii.com and independent API keys. Courier operations can test new client import profiles in sandbox before going live. Grocery distributors can trial new route optimisation settings without affecting real deliveries. For ecommerce operators, sandbox testing of API integrations prevents breaking the order flow. The sandbox operates independently from production, allowing safe experimentation with configuration changes, import rules, and integration endpoints.

What this means for field service businesses

An HVAC company wants to restructure their zone boundaries and team assignments. Testing those changes on the live system could cause dispatching chaos for a day. The sandbox provides a separate environment with its own API endpoint and authentication keys for safe testing. Pest control businesses can test new form templates and POD workflows in sandbox before field deployment. Electrical contractors can trial updated skills and certification configurations. For facilities management companies, sandbox testing of new client onboarding configurations prevents first-week service failures. Production and sandbox environments have separate API keys generated at Configuration, API.

How it works

• Separate sandbox environment at api-sandbox.elogii.com with independent API keys and configuration
• Test configuration changes, import rules, and integrations without affecting live operations
• Production environment at api-35.elogii.com remains unaffected during sandbox testing
• API keys for sandbox and production are generated separately at Configuration, API
• Sandbox provides a safe space for validating workflow changes before production deployment