The Assets API gives you access to machines, implements, and operators tied to a Leaf user. Equipment data comes from two sources: automatic syncing from connected providers (John Deere, CNHi, Stara, Trimble) and manual creation through the API.Documentation Index
Fetch the complete documentation index at: https://docs.withleaf.io/llms.txt
Use this file to discover all available pages before exploring further.
How it works
When a Leaf user connects provider credentials, Leaf pulls machine, implement, and operator records from that provider. These show up withoriginType: PROVIDER_POOLED. You can also create machines manually (originType: USER_CREATED), which is useful for equipment that doesn’t exist in a cloud platform.
Each machine can be linked to machine files, giving you per-equipment usage data including distance traveled, fuel consumption, and time windows.
Implements and operators are currently read-only from providers. Implements come from John Deere and Trimble. Operators come from John Deere.
Key concepts
Machine — A vehicle or self-propelled unit (tractor, sprayer, harvester). Machines have properties likename, serialNumber, vin, make, model, category, and modelYear. Machines sourced from a provider cannot be edited or deleted; only user-created machines can.
Implement — An attachment pulled by or mounted on a machine (planter, cultivator, header). Implements are synced from providers and cannot be created or modified through Leaf.
Operator — A person who operated equipment during field work. Operators are synced from John Deere and include name, license, and status fields.
Origin types:
PROVIDER_POOLED— Synced from a connected provider. Read-only.FILE_POOLED— Extracted from uploaded machine file data.USER_CREATED— Created manually via the API. Editable and deletable.
leafFileId, start and end times, distance, and fuel consumption for that file.
What to do next
- Assets API Reference — Full endpoint details for machines, implements, and operators.