Crops
Create crop
Create a crop on a farm and field owned by the authenticated user.
POST
Authentication
Requires a key with thecrops:write scope. See Authentication.
Request body
UUID of the parent farm. Must be owned by the authenticated user.
UUID of the field. Must belong to
farmId. Required per the Operations Attachment Principle.1–200 characters. Free-text crop name (e.g.
"wheat", "date palm").Positive number in the farm’s
areaUnit. Accepts string or number.Up to 200 characters. Free-text variety.
UUID linking to the admin Crop Library. Prefer this over
cropType when the crop is in the catalog.UUID linking to the admin variety record.
ISO 8601 datetime.
ISO 8601 datetime.
One of
winter, summer, autumn, spring, year_round.2000–2100.
Tons.
In the farm’s
currency.In the farm’s
currency.One of
planned, planted, growing, harvested, failed.Up to 5,000 characters.
Response
Returns the created crop wrapped underdata. See List crops for the full field reference.
Errors
| Status | When |
|---|---|
400 VALIDATION_ERROR | Schema validation failed (details carries per-field messages), OR fieldId doesn’t belong to farmId |
401 | Missing, malformed, expired, or revoked API key |
403 INSUFFICIENT_SCOPE | Key lacks crops:write scope |
404 NOT_FOUND | farmId not owned by the authenticated user (or soft-deleted) |
429 RATE_LIMIT_EXCEEDED | Per-user rate limit reached |
5xx | Server error |