Skip to main content
POST
ESA Check
Check if a field has active Pesticide Use Limitation Areas (PULAs) for the products in your tank mix. Returns detailed limitation data and a white-labeled portal URL for mitigation selection.

Request Body

Required Fields

account_id
string
required
Your customer account identifier. Controls portal access and is displayed in reports.
provider_id
string
required
Your internal provider identifier, assigned by AcreBlitz.
field_name
string
required
Name of the field. Displayed in the portal and on compliance reports.
application_id
string
required
Unique identifier for the application job in your system. Used for idempotency — resubmit with the same application_id to update results rather than create duplicates.
application_method
string
required
Method of application. Use your own terminology (e.g., "Drone", "Ground Boom", "Airblast", "Helicopter") — we automatically map to the correct regulatory categories (aerial, ground, airblast).
application_date
string
required
Application date in ISO 8601 format (YYYY-MM-DD). Used for temporal validation of PULA restrictions.
field_boundary
object
required
GeoJSON Feature with Polygon or MultiPolygon geometry in EPSG:4326 (WGS84).
Example
products
array
required
Products to check. Each product object contains:
Example
crop
array
required
Crop names being treated (e.g., ["corn", "soybeans"]).
pest
array
required
Target pest names (e.g., ["aphids", "corn borer"]).

Optional Fields

provider_field_id
string
Your internal field identifier. Used as the key for report download endpoints. If omitted, application_id is used as fallback.
user_email
string
End user email address. Stored for your records.
gpa
number
Gallons per acre. Used for mitigation calculations.
include_geometry
boolean
default:"false"
Include buffered PULA geometries in the response. Useful for rendering PULA boundaries on a map.
buffer_distance_miles
number
default:"1.0"
Buffer distance around the field for PULA geometry inclusion (max 10 miles). Only applies when include_geometry is true.
droplet_size
string
Droplet size category (e.g., "medium", "coarse", "very_coarse").
boom_height
string
Boom height for ground applications ("low" or "high").

Reserved Fields (Coming Soon)

include_soil_analysis
boolean
default:"false"
Include soil analysis data in the response. Not yet implemented — currently ignored.
include_mitigations
boolean
default:"false"
Include mitigation options in the response. Not yet implemented — currently ignored.

Response

success
boolean
required
Whether the ESA check completed successfully.
esa_required
boolean
required
Whether any product in the request has ESA label language. If false, no further action is needed.
account_id
string
required
The account ID from your request.
provider_id
string
required
The provider ID from your request.
field_id
string
Internal AcreBlitz field UUID. Only present when esa_required is true.
application_event_id
string
Internal AcreBlitz application event UUID. Only present when esa_required is true.
mitigations_required
boolean
Whether the user must select mitigation practices. Only present when esa_required is true.
mitigation_portal_url
string
Secure URL to the white-labeled mitigation portal. Valid for 1 year. Only present when esa_required is true.
expires_at
string
ISO 8601 timestamp for when the portal link expires. Only present when esa_required is true.
user_email
string
The user email from your request, if provided.
products
array
required
Array of product results. Each product contains:Each PULA in the pulas array contains:Each limitation contains:
summary
object
required
Summary statistics for the check.

Examples

When one or more products have ESA label language and the field intersects active PULAs:
When no products in the tank mix have ESA label language, the API returns early without storing data or creating a portal link:

Notes

Idempotency: The application_id field makes the endpoint idempotent. Resubmitting with the same application_id updates the existing record rather than creating a duplicate. Use this to refresh results when products or application details change.
Provider Field ID Fallback: If you don’t provide provider_field_id, the application_id is used as the field identifier for report download endpoints.
Flexible Application Methods: You can use your own terminology for application_method (e.g., "Drone", "Helicopter", "Ground Boom"). The API automatically maps these to the correct regulatory categories.
GeoJSON Format: The field_boundary must be a GeoJSON Feature with a Polygon or MultiPolygon geometry in EPSG:4326 (WGS84). MultiPolygon is supported for fields with excluded areas or multiple sections.