v2.4.0
Summary
Launch Pad 2.4.0 introduces the Logged Data Upload API as a preview, documents the full guidance job API, adds a reference-line upsert endpoint, and moves every error response to the RFC 9457 problem+json contract.
Breaking Changes
RFC 9457 problem+json error contract
All error responses now return application/problem+json with the standard type, title, and status members plus a stable error object (code, message, optional details) and a correlationId for support. The 402 insufficient-credits and 429 rate-limit responses are reshaped to extend this contract, and requests with a wrong or missing API key now return a 401 with an explanatory body instead of an empty response. Clients that parse error bodies should read error.code and error.message.
Before
{
"message": "Not enough credits available.",
"code": "INSUFFICIENT_CREDITS",
"creditsAvailable": 0,
"creditsRequired": 1
}After
{
"type": "https://tools.ietf.org/html/rfc9110#section-15.5.3",
"title": "Payment Required",
"status": 402,
"error": {
"code": "InsufficientCredits",
"message": "Not enough credits available."
},
"creditsAvailable": 0,
"creditsRequired": 1,
"correlationId": "0HNE9QJ4K2M5F:00000001"
}New Features
1. Logged Data Upload (Preview)
Upload logged field data to Launch Pad as a zip archive and turn it into a field operation ready for planning. The data format is detected automatically on the server (an explicitly supplied format still wins), and the target field is optional: pass a fieldId, grower/farm/field names, or nothing at all and the hierarchy is created from the file name. Available as a preview - contact API Support to get access.
| Method | Endpoint | Description |
|---|---|---|
| POST | /api/companies/{companyId}/field-operations/file-upload |
Upload a logged-data zip archive (up to 1 GB) and create a field operation from it |
| GET | /api/companies/{companyId}/field-operations/uploads/{fieldOperationId} |
Processing status of an uploaded field operation |
| GET | /api/companies/{companyId}/user-files/{userFileId}/logged-data-format |
Probe a previously uploaded user file for its logged-data format |
| POST | /api/companies/{companyId}/user-files/{userFileId}/process-as-logged-data |
Process a previously uploaded user file as logged data |
2. Guidance Job API Documented
The guidance job endpoints are now part of the public documentation, with workflow guidance connecting them to the Direct API and the routing endpoints. Integrators can regenerate guidance and routes for an existing plan with full control over the options instead of starting over.
| Method | Endpoint | Description |
|---|---|---|
| POST | /api/guidance |
Start a guidance generation job for a path plan |
| POST | /api/zone-guidance |
Start a guidance generation job for specific zones |
| GET | /api/guidance/jobs/{jobId} |
Poll the status and results of a guidance job |
3. Reference Lines
Create or update a reference line that plans can be built from.
| Method | Endpoint | Description |
|---|---|---|
| POST | /api/reference-lines |
Create or update a reference line |
Improvements
- Richer endpoint documentation for routing: request workflow, polling guidance, and how to combine the routing endpoints with Direct API responses.
- Boundary export endpoints now document their response content types (GeoJSON, KML, WKT).
New Schemas
| Schema | Description |
|---|---|
ApiProblemDetails |
RFC 9457 problem details with a stable error object and correlation id; specialized variants exist per status code (BadRequestProblemDetails, UnauthorizedProblemDetails, ForbiddenProblemDetails, PaymentRequiredResponse, RateLimitErrorResponse, ClientClosedRequestProblemDetails, InternalErrorProblemDetails) |
FieldOperationStatus |
Processing status of an uploaded field operation |
LoggedDataFormatProbe |
Detected logged-data format of an uploaded user file |
ReferenceLineUpsert |
Reference line to create or update |
GuidanceJobRequest |
Guidance job request for a path plan |
GuidanceZoneRequest |
Guidance request for a specific zone |
GuidanceStraightOptions |
Options for straight-track guidance |
GuidanceCurvedOptions |
Options for curved-track guidance |
Questions?
For questions about these API changes, please contact [email protected] or refer to the API documentation.