Crops
Update crop
Update mutable fields on a crop. Only provided fields are touched.
PUT
Authentication
Requires a key with thecrops:write scope.
Path parameters
Crop UUID.
Request body
All fields are optional. Only fields you include in the body are updated; omitted fields are left unchanged. To changefieldId, the new field must belong to the same farm as the crop’s current field.
UUID. Must belong to the crop’s current farm.
1–200 characters.
Up to 200 characters. Pass
null to clear.UUID. Pass
null to clear.UUID. Pass
null to clear.In the farm’s
areaUnit.ISO 8601 datetime. Pass
null to clear.ISO 8601 datetime. Pass
null to clear.One of
winter, summer, autumn, spring, year_round. Pass null to clear.2000–2100. Pass
null to clear.Tons. Pass
null to clear.In the farm’s
currency. Pass null to clear.In the farm’s
currency. Pass null to clear.One of
planned, planted, growing, harvested, failed. To set harvested and auto-populate actualHarvestDate, prefer the dedicated status endpoint.Up to 5,000 characters. Pass
null to clear.Response
Returns the updated crop wrapped underdata.
Errors
| Status | When |
|---|---|
400 INVALID_ID | {id} is not a valid UUID |
400 VALIDATION_ERROR | Schema validation failed, OR new fieldId doesn’t belong to the crop’s farm |
401 | Missing, malformed, expired, or revoked API key |
403 INSUFFICIENT_SCOPE | Key lacks crops:write scope |
404 NOT_FOUND | Crop doesn’t exist, is soft-deleted, or belongs to a farm the user doesn’t own |
429 RATE_LIMIT_EXCEEDED | Per-user rate limit reached |
5xx | Server error |