Tech Update · September 2026
September 2026 platform update — bidirectional John Deere Operations Center integration, Work Records Shape, SSO and RAC, the new REST API, free testing, the Implementation Review, and legacy API migration.
The September 2026 update focuses on cross-manufacturer data exchange and an easier path to integration. This page summarizes the changes relevant to integration developers and links to the detailed documentation for each topic.
Bidirectional John Deere Operations Center integration
agrirouter now supports bidirectional data exchange with the John Deere Operations Center (JDOC), so agrirouter-ready software and machines can exchange planning and documentation data with John Deere machines and the Operations Center.
Every connected agrirouter endpoint (software and machine) is registered automatically in the JDOC. It appears there as equipment prefixed [AR] and can be addressed just like a John Deere machine.
Endpoints stay in sync automatically: when an endpoint is deleted in the agrirouter Control Center, the JDOC archives the matching [AR] equipment.
Data flows in both directions:
- Planning data out of the JDOC — Work Plans (including application maps) can be addressed to agrirouter-ready machine and software endpoints.
- Planning data into the JDOC — external application maps and work plans reach the Operations Center through agrirouter.
- Work Record data out of the JDOC — documentation data from John Deere machines is delivered to agrirouter-ready software.
- Work Record data into the JDOC — work records from agrirouter-ready machines are delivered to the Operations Center.
Work Records Shape
The Work Records Shape specification documents the structure and semantics of Shape-based work-record data: which layers, attributes, and values a Work Record contains and how to interpret them.
Shape support alone is enough to receive John Deere work records. Work Records Shape is not a precondition for receiving the data; the specification makes it easier to reliably interpret and process what you receive.
See the Work Records Shape reference for the full structure and attributes.
Single Sign-On (SSO) and Remote Application Connection (RAC)
Both features are ready for implementation on the partner side.
- Single Sign-On (SSO) lets a user switch from a partner application into the agrirouter Control Center without logging in again, to manage endpoints, connections, and routes.
- Remote Application Connection (RAC) lets a user start a connection from within your own application. A guided flow handles authorization in the target system and route review in the Control Center, then returns the user to your app, now connected.
No agrirouter account yet? If no agrirouter account exists, it is created automatically in the background during the connect flow — there is no separate registration step.
Single Sign-On: straight from your software into agrirouter, one login.
Remote Application Connection: connect your manufacturer directly from your software.
Single Sign-On4 min Remote Application Connection11 minNew REST API
The current API is REST-based and provides a modern foundation for new integrations. The developer documentation is structured for use with AI-assisted development tools and coding agents. A first integration can typically be up and running in about three to seven working days, depending on scope and system architecture.
Free testing
You can develop, integrate, and validate with first test customers before a membership becomes due. During integration, the IO tool is provided free of charge and can simulate both the software side and the machine side, and test files are available for typical test scenarios.
See the business and legal section for the development, test, and go-live phases.
Implementation Review instead of certification
There is no longer a separate certification. Instead, partners and the agrirouter team carry out an Implementation Review together to ensure integration quality before production use.
- The Implementation Review is free of charge. The previous certification fee of €2,500 no longer applies.
- A re-review is required when capabilities relevant to data exchange change, for example new or changed message types. Normal UI updates and bug fixes do not trigger a review.
Migration from the legacy API (HTTP/MQTT)
Existing partners can move from agrirouter's legacy API (HTTP/MQTT) to the new REST API. An existing legacy integration does not migrate automatically: first implement the new REST API, then move your existing endpoints and users across.
Migrating from the Legacy API4 min