Skip to main content
POST
Assess ESA and PULA requirements for one pesticide application.

Request

string
required
Your assigned provider identifier. It must match the API key.
string
required
Your customer account identifier.
string
required
Field name shown in the portal and compliance reports.
string
required
Your application identifier, unique within this provider and account. Resubmit this application to refresh its assessment.
string
required
Supported method: for example Broadcast-Ground, Broadcast-Air, Drone, or Airblast. Unsupported values return 422. Liberty Ultra is ground only.
string
required
A valid calendar date in YYYY-MM-DD format.
object
required
GeoJSON Feature containing a Polygon or MultiPolygon in EPSG:4326. Rings must be closed; self-intersections are rejected. Maximum 5,000 positions across the field boundary.
object[]
required
One to 100 product objects. See the product fields below.
string[]
required
Crop names. An explicit empty array is accepted.
string
Your field identifier, used for compliance report requests. If omitted or null, the application identifier is used.
string
Your work-order or job identifier. Optional for a single check; required for bulk submissions.
string[]
Default pests for products without their own pest list. Every product must have a nonempty effective pest list.
string
Optional applicator or grower email address; nullable.
number
Positive spray gallons per acre. Required to normalize rates expressed per 100 Gal or 100 Cu Ft; nullable.
string
ASABE category or code: EF, VF, F, M, C, VC, EC, or UC. Unsupported values return 422; nullable.
string
low or high for ground applications; nullable.

Product fields

Response options

boolean
default:"false"
Include PULA field-boundary data when available.
boolean
default:"false"
Include analysis under compliance.soil.analysis when soil is available.
boolean
default:"false"
Include available options under compliance.mitigation_options.
number
default:"1"
PULA search buffer distance, clamped to 0–10 miles.

Response

success describes request handling. Read compliance.status, processing_complete, soil, runoff, drift, and issues for the assessment. compliance.scope is requirements_and_gaps; its version is the assessment format version, independent of the API URL version. Product results include esa_required, registration status, effective pests, and PULA limitations. For ESA-required checks, the response also includes an opaque application_event_id and a mitigation_portal_url when available. mitigation_portal_url_expires_at is the signed-link expiration in signed-link mode and null in token mode. expires_at describes the field portal’s availability, which can have a different lifetime. Use the returned link unchanged.

Repeat a check

The provider/account/application identity is reused. Resubmitting updates the saved assessment when ESA processing is required. A no-ESA early return does not update an existing saved application. A changed field boundary refreshes its derived data. Background soil enrichment requires a new check to refresh the assessment. The example response below shows selected fields only; values depend on product, field, and review state.

Errors

Processing can return 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. A workflow can also return 422 UNSUPPORTED_APPLICATION_METHOD; HTTP input validation normally catches this first as INVALID_REQUEST. See assessment issues for incomplete evidence 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.