APIs at a glance
The four APIs are the actual backbone of the platform. They are the integration boundaries the ITU/FAO reference architecture pins down — every vendor implementation has to honour them.
| API | Underlying standard | Purpose |
|---|---|---|
| Farm API | GeoJSON, AgroVoc, ITU/FAO data model | Master data — orgs, users, farms, fields, regions |
| Sensor Things API | OGC SensorThings API v1.1 | Sensor & observation lifecycle, live data ingest |
| Spatio-Temporal API | OGC API · STAC | Maps, layers, rasters, vectors, AI model outputs |
| Activity API | ITU/FAO data model, AgroVoc | Plantings, operations, inputs, outputs, economics |
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 | Service Registry · Spatio-Temporal | Farm · Sensor Things · Activity |
| Data App Developer | Farm · Activity | Spatio-Temporal · Service Registry |
| Sensor Integrator | Sensor Things | Farm |
| Frontend / Dashboard Developer | Spatio-Temporal · Farm | Activity · Sensor Things |