Skip to main content
This section covers Leaf API features that are available and functional but still subject to breaking changes. Beta endpoints use the /services/beta/ base path. Leaf may modify request/response schemas, rename fields, or adjust default values as these features mature.

What’s in beta

Assets — Manage machines, implements, and operators associated with a Leaf user. Assets are pooled from connected providers or created manually, and link to machine files for equipment-level reporting. Prescriptions — Upload and list prescription maps across providers including John Deere, CNHi, Climate FieldView, Raven Slingshot, Trimble, and Ag Leader. Layers — Retrieve imagery layers (tassel count, stand count, NDVI, RGB) from Sentera and upload layers to Climate FieldView. Input Validator — Look up and match agricultural products, varieties, and tank mixes against standardized databases. Includes automatic product matching for field operations. Operations Planning — Plan and schedule field operations ahead of execution.

How beta features graduate

When a beta feature stabilizes, Leaf moves it to the main API surface under /services/. Existing beta endpoints continue to work during a deprecation window, typically 90 days. Leaf announces graduations in the changelog.
Last modified on March 24, 2026