Skip to main content
Use V2 to check one pesticide application or submit a group of fields for asynchronous processing. You receive PULA requirements, runoff and drift assessments, and portal links for review. Base URL: https://esa.acreblitz.com. All API routes use the /api/v2 prefix. V1 is deprecated. This documentation covers the supported V2 endpoints.

Quickstart

Run a single check and inspect the assessment.

Bulk checks

Submit up to 100 fields with shared products and crops.

Migrate to V2

Review request validation and response changes.

API reference

Browse every V2 endpoint.

​
Interpret an assessment

Read Understanding compliance determinations for the full runoff and drift workflow, setup violations, status precedence, and when to refresh saved results. An HTTP 200 response or success: true means the request was handled. Read compliance.status, compliance.processing_complete, and compliance.issues before making a decision. A completed calculation can remain indeterminate when applicability, weather, or field conditions need review. An ESA assessment does not grant unrestricted application clearance. Review the product label, returned PULA text, and unresolved conditions.

​
Soil reuse and refreshed results

After portal changes, use get application compliance or get group compliance to read current runoff scoring, saved requirements, and full drift details. These read-only endpoints use Cache-Control: no-store. Their last_assessment is historical; retrieval does not produce a new overall compliance verdict. V2 reuses soil when the field boundary and processing version match. A changed field boundary triggers fresh processing. Background soil enrichment does not rewrite a returned assessment; resubmit the same application to refresh it. Bulk polling responses use Cache-Control: no-store. Do not cache job status as a final assessment.