The Digital Farm APIs
The APIs are the integration boundaries the ITU/FAO reference architecture pins down — every vendor implementation has to honour them. The core of them is the digital farm API, the REST binding of the data model; companion interfaces cover high-frequency sensor data and raster archives.
| API | Underlying standard | Purpose |
|---|---|---|
| Digital Farm API | the data model of the draft ITU-T Recommendation, OpenAPI 3.1, GeoJSON, OGC API – Features, AGROVOC | master data and operations — organisations, users, farms, fields, regions, cultivation, work, products, machines, animals, observations, economics, compliance, processing runs |
| Sensor Things API | OGC SensorThings API v1.1 | sensor and observation lifecycle, live data ingest. A Device of the data model points at its service through sensorThingsUrl |
| Spatio-Temporal API | OGC API · STAC | maps, layers, rasters, vectors, AI model outputs |
All of them take tokens from the platform's identity provider — see Identity, Authentication & Access.
Page structure
Every API concept page follows the same substructure:
- Purpose — what the API does
- Underlying open standard — which public spec it implements
- Core resources — the data objects and how they relate
- Capabilities — what you can actually do with it
- Code example — a short end-to-end snippet
- Reference link — to the formal API reference
Persona → API map
| Persona | Primary APIs | Secondary APIs |
|---|---|---|
| AI Service Developer | Digital Farm API (processing runs, results) · Spatio-Temporal | Sensor Things |
| Data App Developer | Digital Farm API | Spatio-Temporal |
| Sensor Integrator | Sensor Things | Digital Farm API (devices, observations) |
| Frontend / Dashboard Developer | Digital Farm API · Spatio-Temporal | Sensor Things |