Skip to main content
POST
Refresh an application assessment with current wind and application setup.

Request

string
required
Opaque application-event reference from a previous ESA check.
number
required
Wind direction in degrees, greater than or equal to 0 and less than 360.
number
required
Wind speed, 0–80 mph.
number
Optional observed temperature, -100–200 degrees Fahrenheit; nullable.
number
Optional observed humidity, 0–100; nullable.
string
Optional supported method; otherwise use the saved method.
string
Optional supported category/code; nullable. An omitted value uses the saved value; explicit null clears it.
string
Optional low or high; nullable. An omitted value uses the saved value; explicit null clears it.
number
Optional positive spray gallons per acre; nullable. An omitted value uses the saved value; explicit null clears it.
object[]
Up to 100 rate changes. Each requires product_index (zero-based), epa_number, nonnegative rate, and nonempty rate_unit; optional rate_unit_state and positive row_spacing_inches. The index and registration must match the saved product.
string
none, buffer, treatable, or both; defaults to none.

Assessment behavior

The endpoint resolves your saved application, applies current weather/setup inputs and rate changes, and returns a refreshed check plus application_time. Weather and the assessment are saved for that application. It checks the application revision; conflicting changes return 409. application_time includes submitted inputs, effective rates, reductions, manual mitigation claims, feature scope, feature counts, per-edge buffers, and product-specific buffer details. Requested field-boundary output is returned under application_time.geometry and is not retained in the saved assessment snapshot. The returned compliance.status is authoritative for this assessment. Manual claims and conditions that cannot be verified remain explicit issues; a calculated buffer alone is not application clearance. Protected features are read for this request so new nearby features can affect the result. The example shows selected response fields.

Errors

Endpoint-specific errors include 404 APPLICATION_NOT_FOUND; 422 NO_FIELD_GEOMETRY, PRODUCT_MISMATCH, INVALID_APPLICATION, or UNSUPPORTED_APPLICATION_METHOD; and 409 DUPLICATE_FIELD, FIELD_OWNERSHIP_CONFLICT, DUPLICATE_APPLICATION, APPLICATION_FIELD_CONFLICT, PROCESSING_CONFLICT, FIELD_CHANGED, or APPLICATION_CHANGED. Signed portal setup can return 503 PORTAL_SAS_UNCONFIGURED. See assessment issues for unresolved conditions returned with HTTP 200. All routes can also return authentication, validation, rate-limit, and dependency errors. Use the error catalog and examples to choose a retry or correction. Keep X-Request-ID when present.