How growers map to providers
Each provider has its own concept of the data owner:- John Deere — Growers correspond to John Deere “Clients.” The
nameproperty comes directly from the Client name. - Other providers — The mapping varies. Some providers have a direct grower equivalent; others do not.
providerName, providerGrowerId).
Grower resource
name property is present only when a name is available from the provider or was set manually.
Creating a grower
POST /services/fields/api/users/{leafUserId}/growers
name field is accepted. Leaf assigns the grower an auto-generated integer ID.
Updating a grower
PUT /services/fields/api/users/{leafUserId}/growers/{id}
You can update the name field.
Listing growers
GET /services/fields/api/growers
Returns a paged list of all growers. Filter by provider, leafUserId, or use page and size for pagination.
Enabling preview fields by grower
WhencustomDataSync is enabled, you can activate all preview fields under one or more growers at once:
POST /services/fields/api/growers/enableSync
PREVIEW mode and queues them for the next full sync. It’s faster than enabling fields individually when you want to onboard an entire grower.
Farms
Farms group fields under a grower. They work the same way as growers: synced from providers or created manually.POST /services/fields/api/users/{leafUserId}/farms creates a farm. You can pass name and optionally growerId to link it to a grower.
GET /services/fields/api/farms lists all farms, filterable by growerId, provider, and leafUserId.
What to do next
- Fields Overview — The full Grower/Farm/Field hierarchy.
- Managing Fields — Working with fields and boundaries.
- API Reference: Growers — Full endpoint reference for grower and farm operations.

