Skip to main content

Send one application

Set ACREBLITZ_API_KEY on your backend, replace the provider/account/field identifiers, and submit a valid field boundary. This example uses Liberty Ultra with Broadcast-Ground.

Inspect the result

Read compliance.status, processing_complete, and issues. A successful request can have unresolved compliance. Keep the returned application_event_id as an opaque reference for application-time checks and portal controls. Open mitigation_portal_url when one is returned; use the entire URL unchanged. Each entry in products[] lists the PULAs on the field that limit that product for your application method. Show each limitations[].limitation text to the applicator. The API cannot evaluate every condition in that text, so a returned limitation adds LIMITATIONS_REVIEW_REQUIRED and keeps the status indeterminate until reviewed. See product PULA limitations.
If esa_required is false, inspect the issues before treating the result as not applicable. Unknown products can produce an indeterminate assessment. The no-ESA early return does not create or update a saved field/application.

Check multiple fields

Use Submit bulk checks to define common products, crops, pests, method, and date once. Each field can replace those settings independently. A bulk submission requires provider_group_id and returns 202 Accepted with a job_id. The API checks unique products across the full request first. When all are confirmed to have no ESA requirement, it returns status: "completed", esa_required: false, and all items immediately. Otherwise, poll the returned status_url, then page through results_url. These URLs are relative to https://esa.acreblitz.com. Preserve your Idempotency-Key when retrying the same submission. A succeeded bulk item means its check returned a result. Inspect that result’s compliance, even when the overall job is completed.

Continue the workflow