| Alerts | Webhook notifications triggered by events in Leaf — new field operations, credential expiration, boundary changes, file processing completion, etc. You register an alert URL once and Leaf pushes events to it instead of requiring you to poll. |
| API owner | The top-level Leaf account, identified by the email address you registered with. Owns all Leaf users beneath it. Use separate API owners for test and production environments. |
| Batch upload | A single upload request containing one or more machine files. Each batch is tracked by a batch ID and progresses through RECEIVED → PROCESSING → PROCESSED (or FAILED). Query the batch status endpoint to monitor progress. |
| Configurations | Settings that control how Leaf ingests, processes, and outputs data. Applied at the API owner level (inherited by all Leaf users) or overridden per Leaf user. Changes are not retroactive — they only affect data processed after the change. |
| Custom data sync | A configuration (customDataSync) that limits Leaf to fetching field metadata only from a provider. You then select which fields to fully process. Useful for controlling costs and scope. |
| Field | A named area of land within a farm. In Leaf, the field object holds metadata (name, ID, area) but does not require a boundary. Fields can be synced from a provider or created via the API. |
| Field boundary | The geographic polygon defining a field’s extent. One active boundary per field. Required for creating field operations — without a boundary, Leaf still converts machine files and produces file summaries, but cannot clip data to the field. |
| Field operation | The merged, boundary-clipped output from one or more machine files. Represents a single activity — planting, harvest, application, or tillage — on a specific field. Each field operation has a summary and optional property map images. |
| Filtered GeoJSON | An optional processing stage where invalid or outlier data points are removed from the standard GeoJSON based on configurable rules. Enabled via configuration. |
| Leaf user | Represents a grower (or region, sub-customer, etc.) under your API owner. Holds provider credentials, fields, machine files, and field operations. Data is isolated per Leaf user. Typically one Leaf user per grower. |
| Machine file | A raw data file from a provider or direct upload containing GPS-tagged point data from field equipment. Leaf converts these through raw → standard → (optionally) filtered GeoJSON. Each machine file gets a summary with averages, min/max, and standard deviations. |
| Machine file summary | Aggregated statistics derived from the point data in a single machine file — processed and cleaned by Leaf. Output properties vary by operation type (planted, applied, harvested, tillage). |
| Magic Link | A hosted web widget you can send to growers. They click it and connect their provider account or upload files without interacting with the API directly. |
| Operation summary | Aggregated statistics for a field operation — the result of merging machine files to a field boundary. Similar to a machine file summary but scoped to a single field and activity. |
| Provider | A third-party platform that supplies agricultural data — John Deere, Climate FieldView, CNHi, CNHI FieldOps, Trimble, AgLeader, Stara, and others. Each provider requires its own license agreement and credentials. |
| Provider credentials | OAuth2 tokens or API keys attached to a Leaf user that authorize Leaf to pull data from a specific provider. One credential set per provider per Leaf user. |
| Standard GeoJSON | The cleaned, standardized GeoJSON output. Property names, units, and structure are consistent regardless of source provider or file format. This is the primary output format for machine files and field operations. |
| Webhook | See Alerts. |
