API Changelog

v2.1.0 adds new endpoints for routing to a target geometry, gives John Deere exports an opt-out for tramline reduction, exposes pre-validation notices on export jobs, and supports the {{FieldName}} placeholder in export naming templates.

v2.0.0 introduces a zone-based path plan architecture. Path plans organize data hierarchically - each field part becomes a zone with its own guidance settings, geometry, and routes. New endpoints support bulk operations, equipment scenario analysis, slope generation, and shared plan access.

This release introduces new route customization options for path plan generation, adds support for cross-hatch patterns, and includes minor parameter naming improvements for consistency.

Renamed endpoints to follow RESTful conventions, added path plan groups management, introduced API rate limiting, and improved documentation quality.

Launch of the public API documentation via Scalar. Over 100 endpoints are now documented and accessible through the API docs portal, covering boundaries, fields, farms, growers, companies, equipment, guidance, routing, path plans, exports, and sharing.

Routing improvements including consistent route options between UI and API, wheel traffic route summaries, headland connection rework, and improved error handling for routes.

Introduction of API key authentication, route coverage metrics, and significant routing improvements including headland traversal rework and forced straight connectors.

Initial public release of the Launch Pad API. Core platform for path plan generation, field and boundary management, equipment configuration, routing optimization, and file exports for John Deere, PTx Trimble, and ISO-XML formats.