Integration Guide
Task-oriented guides for integrating farming software, telemetry platforms, and communication units with agrirouter
These guides cover integrating your application or device with agrirouter. Each one targets a specific developer persona and walks from first endpoint creation through production approval.
For implementation, the current REST API is also published as a hosted OpenAPI specification. Use it to generate clients, import the contract into API tooling, or validate requests while you follow the integration guides.
Which Integration Path Is Right for You?
Answer these two questions to find the guide that matches your use case:
Are you building a cloud application or a hardware device?
If you are building firmware for a physical device (terminal, telemetry box, ISOBUS gateway) that sits on a machine, follow the Communication Unit guide. That path uses the legacy API. If you are building a cloud or desktop application, continue to the next step.
Does your application manage a fleet of machines?
If your application is a cloud backend that manages physical machines, where each machine should appear as a separate endpoint, follow the Cloud Software guide and then the Virtual Communication Units guide. If your application is a standalone application that exchanges data with machines but does not manage them directly, follow the Cloud Software guide only.
Integration Guides
Cross-Cutting Guides
These guides apply to all endpoint types. Read them after the type-specific setup.
Understanding the Platform
Before starting integration, make sure you understand the agrirouter ecosystem and the roles of the different endpoint types.
Ecosystem: Endpoint Types and Roles6 min