Migrate from V1

V1 and V2 use different hosts and contracts. Switch each integration explicitly; V2 does not serve V1 route aliases.

Topic	V2 behavior
Host and paths	Use `https://esa-v2.acreblitz.com/api/v2/...`.
Single check	Returns an assessment in the same HTTP response.
Bulk checks	Submit 1–100 fields, then poll and fetch per-field results.
Group identifier	Optional for a single check; required at the top level for bulk.
Products and crops	Bulk defaults may be replaced per field; arrays are replaced, not merged.
Pest inputs	Each product needs a product pest list or an inherited default.
Method and droplet inputs	V2 validates supported categories; arbitrary strings are rejected.
Optional details	`include_soil_analysis` and `include_mitigations` return assessment details when available.
Errors	JSON `success: false` and `error.code`; validation errors also include issue paths.
Portal links	Use returned links unchanged and honor their expiration. Providers can use token or signed-link access.
Report lookup	Use your external `provider_field_id`.

Roll out in order

Confirm your V2 hostname and API key with AcreBlitz.
Validate request construction against the single check and bulk contracts.
Handle indeterminate assessments and partial bulk failures before enabling intake.
Move one provider/account workflow at a time. Avoid submitting the same field/application concurrently through both versions.
Keep your V1 integration available while reviewing the V2 results and compliance reports.

V1-only capabilities remain in V1. Do not infer that an endpoint exists in V2 simply by changing its URL prefix. The V2 API reference lists supported routes.

Getting started

Integration guides

Roll out in order

​Roll out in order

Roll out in order