Skip to main content
Base URL: https://esa.acreblitz.com. Every endpoint requires X-API-Key.

​
Processing and persistence

Single checks return a response after required processing. When ESA is required, the saved field/application and response are updated together. No-ESA early returns do not create or update those records. Bulk intake checks the unique products used across the full request. If all are confirmed to have no ESA requirement, it returns a completed job and all item results immediately. Other jobs enter the processing queue, where each field uses the same assessment workflow as a single check. Job completion and compliance are separate outcomes. Results remain available for 30 days after the job completes; save the results you need. Standalone soil and runoff baseline requests do not save a field/application. Field processing saves a field and automatic runoff credits without creating an application. Compliance retrieval reads current selections and saved requirements without rerunning a check. Group retrieval requires account_id and supports pagination. Both use Cache-Control: no-store and distinguish current runoff scoring from the last saved assessment and drift computation.

​
Response and request conventions

JSON requests use Content-Type: application/json. Field boundaries use GeoJSON in EPSG:4326. Application identifiers belong to your provider and account. Treat returned job and application-event identifiers as opaque API references. Single checks can need up to the service’s request deadline (90 seconds by default). Client/proxy timeouts should allow the configured deadline. Bulk completion depends on queue wait and field processing; no fixed one-minute job completion time is guaranteed. See error handling and authentication.