agX APIs & Services

In order for multiple software providers to collect, store, and share data, the agX Platform provides a host of APIs and services. These APIs and services facilitate the collection and management of data across independent agX compliant applications.


agX Content API

Standardization from field-to-field and season-to-season is maintained by applications accessing the agX® Content API. This API not only contains reference data for corresponding with the core data schemas but also defines standards pertaining to structure of field operations, tasks, and task attributes. agX Content contains over 100,000 reference entries, and new content updates are published every few weeks. Currently, content covers the United States and Canada, with rapid progress being made in Australia, Brazil, and South Africa.

Summer 2013

agX Sync API

All applications that are agX compliant use the agX® Sync API to synchronize field data in a standardized format. This bidirectional sync includes data types such as field boundaries, management zones, soil sampling, fertilizer, planting, and crop protection. The agX Sync API is the gatekeeper that ensures data standards are being maintained while adhering to strict, permission-based security protocols.

Summer 2013




agX Enterprise Data Services

Enterprise Data Services (EDS) allow corporate IT to access collected data for use in their custom backend environments. This high-end solution uses Amazon Web Services (AWS) to extract and transfer data to a third-party enterprise environment. Legal and technical contracts specify the accessible types of data, how users grant access to their data, and the frequency of data transfer. The data transfer protocol is communicated through XML schema using the Well-Known Text (WKT) geospatial markup language.

Winter 2013


agX Common Field Boundary API

When a field boundary is created or edited, it is assigned a globally unique identification (GUID) with a corresponding time stamp. The Common Field Boundary (CFB) API standardizes boundaries by allowing agX® compliant applications to work from the same boundary file. If a boundary is edited, the edits are applied across all applications. The CFB ensures spatial integrity by not allowing fields to be added that have bow ties or break other basic polygon rules.

Release Date