ESA Check
ESA Check
ESA Check
Check ESA/PULA restrictions for a pesticide application
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.Documentation Index
Fetch the complete documentation index at: https://docs.acreblitz.com/llms.txt
Use this file to discover all available pages before exploring further.
Request Body
Required Fields
Your customer account identifier. Controls portal access and is displayed in reports.
Your internal provider identifier, assigned by AcreBlitz.
Name of the field. Displayed in the portal and on compliance reports.
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.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 in ISO 8601 format (
YYYY-MM-DD). Used for temporal validation of PULA restrictions.GeoJSON Feature with Polygon or MultiPolygon geometry in EPSG:4326 (WGS84).
Example
Products to check. Each product object contains:
| Field | Type | Required | Description |
|---|---|---|---|
epa_number | string | No | EPA registration number (nullable for adjuvants) |
product_name | string | Yes | Product name |
rate | number | Yes | Application rate |
rate_unit | string | Yes | Rate unit (e.g., "fl oz/acre") |
Example
Crop names being treated (e.g.,
["corn", "soybeans"]).Target pest names (e.g.,
["aphids", "corn borer"]).Optional Fields
Your internal field identifier. Used as the key for report download endpoints. If omitted,
application_id is used as fallback.End user email address. Stored for your records.
Gallons per acre. Used for mitigation calculations.
Include buffered PULA geometries in the response. Useful for rendering PULA boundaries on a map.
Buffer distance around the field for PULA geometry inclusion (max 10 miles). Only applies when
include_geometry is true.Droplet size category (e.g.,
"medium", "coarse", "very_coarse").Boom height for ground applications (
"low" or "high").Reserved Fields (Coming Soon)
Include soil analysis data in the response. Not yet implemented — currently ignored.
Include mitigation options in the response. Not yet implemented — currently ignored.
Response
Whether the ESA check completed successfully.
Whether any product in the request has ESA label language. If
false, no further action is needed.The account ID from your request.
The provider ID from your request.
Internal AcreBlitz field UUID. Only present when
esa_required is true.Internal AcreBlitz application event UUID. Only present when
esa_required is true.Whether the user must select mitigation practices. Only present when
esa_required is true.Secure URL to the white-labeled mitigation portal. Valid for 1 year. Only present when
esa_required is true.ISO 8601 timestamp for when the portal link expires. Only present when
esa_required is true.The user email from your request, if provided.
Array of product results. Each product contains:
Each PULA in the
Each limitation contains:
| Field | Type | Description |
|---|---|---|
epa_number | string | EPA registration number |
product_name | string | Product name |
product_status | string | null | Registration status ("Active", "Inactive", or null if not found) |
esa_required | boolean | null | Whether this specific product has ESA label language |
pulas | array | PULAs affecting this product (empty if no ESA restrictions) |
pulas array contains:| Field | Type | Description |
|---|---|---|
pula_id | integer | PULA identifier |
event_name | string | Regulatory event name (e.g., "NMFS BiOps 2024") |
status | string | PULA status (e.g., "effective") |
effective_date | string | Date the PULA became effective |
codes | string | Limitation codes |
geometry | object | null | GeoJSON geometry (only if include_geometry=true) |
limitations | array | Specific limitations for this PULA |
| Field | Type | Description |
|---|---|---|
limitation_id | integer | Limitation identifier |
code | string | Limitation code (e.g., "RPMDZ") |
limitation | string | Full limitation text |
mitigation_options | array | Required mitigation types (e.g., ["epa_runoff"]) |
Summary statistics for the check.
| Field | Type | Description |
|---|---|---|
total_pulas | integer | Total PULAs found affecting the field |
total_limitations | integer | Total limitations across all PULAs |
products_checked | integer | Number of products checked |
products_with_limitations | integer | Number of products with active limitations |
Examples
ESA Required — Full Response
ESA Required — Full Response
When one or more products have ESA label language and the field intersects active PULAs:
ESA Not Required — Early Exit
ESA Not Required — Early Exit
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.
