Environments

agrirouter operates two independent environments: Production and QA (Quality Assurance). Accounts, endpoints, and data in one environment are fully isolated from the other. Production is the default environment for partner integrations. Use it throughout development, testing, and live operation.

Production environment

Production is where all partner integrations run, from the first line of code through live operation with end users. Your integration connects to real agrirouter accounts and exchanges real agricultural data from day one, and your credentials stay valid for the full lifecycle of your application.

When you need a counterpart to exchange messages with during development, the IO-Tool can act as a test receiver on Production.

QA environment

The QA environment is reserved for internal agrirouter team use and for partners DKE has explicitly directed to it, typically to validate a new platform feature before it ships to Production. Data in QA may be reset periodically.

Endpoints in one environment cannot communicate with endpoints in the other. If you ever test against QA, make sure every component (including any IO-Tool instance) is configured for the same environment.

Environment URLs

Each environment has its own set of API endpoints and UI URLs. For the complete list, see the appendix.

Environment URLs1 min

Availability area

agrirouter currently operates in the EU area. Both the Production and QA environments are hosted within the EU region.

Next steps

With your developer account set up and the environments clear, create your first endpoint.

Your First Endpoint9 min