curl --request POST 'https://esa.acreblitz.com/api/v2/applications/019953f8-8c00-7000-8000-000000000002/drift-buffer/compute' \
--header "X-API-Key: $ACREBLITZ_API_KEY" \
--header 'Content-Type: application/json' \
--data '{
"wind_direction_deg": 180,
"wind_speed_mph": 8,
"temperature_f": 72,
"humidity_percent": 55,
"application_method": "Broadcast-Ground",
"droplet_size": "VC",
"boom_height": "low",
"gpa": 15,
"rate_updates": [
{
"product_index": 0,
"epa_number": "7969-500",
"rate": 28,
"rate_unit": "fl oz/ac",
"rate_unit_state": "L"
}
],
"geometry": "both",
"include_non_managed_areas": true
}'
{
"success": true,
"application_event_id": "019953f8-8c00-7000-8000-000000000002",
"application_time": {
"checked_at": "2026-10-05T14:10:00.000Z",
"status": "met",
"drift_status": "met",
"feature_scope": "global_only",
"non_managed_feature_count": 0,
"exclusion_feature_count": 0,
"inputs": {
"wind_direction_deg": 180,
"wind_speed_mph": 8,
"temperature_f": 72,
"humidity_percent": 55,
"application_method": "Broadcast-Ground",
"droplet_size": "very_coarse",
"boom_height": "low",
"gpa": 15
}
},
"products": [
{
"epa_number": "7969-500",
"product_name": "Liberty Ultra",
"pest": ["Waterhemp"],
"product_status": "Active",
"esa_required": true,
"pulas": []
}
],
"summary": { "total_pulas": 0, "total_limitations": 0, "products_checked": 1, "products_with_limitations": 0 },
"compliance": {
"version": 1,
"scope": "requirements_and_gaps",
"status": "met",
"drift": {
"status": "met",
"scope": "application_setup_and_treatable_area",
"requires_buffer": true,
"has_treatable_area": true
}
}
}
{
"application_time": {
"non_managed_feature_count": 1,
"non_managed_areas": {
"type": "FeatureCollection",
"features": [
{
"type": "Feature",
"geometry": {
"type": "Polygon",
"coordinates": [[[-95.4041, 43.1018], [-95.3989, 43.1018], [-95.3989, 43.0991], [-95.4041, 43.0991], [-95.4041, 43.1018]]]
},
"properties": {
"feature_type": "wetland",
"source": "protected_feature",
"distance_m": 18.4,
"product_epas": ["7969-500"],
"rules_matched": []
}
}
]
}
}
}
Portal and application controls
Compute application-time drift buffers
Refresh an application assessment with current wind and application setup
POST
/
api
/
v2
/
applications
/
{application_event_id}
/
drift-buffer
/
compute
curl --request POST 'https://esa.acreblitz.com/api/v2/applications/019953f8-8c00-7000-8000-000000000002/drift-buffer/compute' \
--header "X-API-Key: $ACREBLITZ_API_KEY" \
--header 'Content-Type: application/json' \
--data '{
"wind_direction_deg": 180,
"wind_speed_mph": 8,
"temperature_f": 72,
"humidity_percent": 55,
"application_method": "Broadcast-Ground",
"droplet_size": "VC",
"boom_height": "low",
"gpa": 15,
"rate_updates": [
{
"product_index": 0,
"epa_number": "7969-500",
"rate": 28,
"rate_unit": "fl oz/ac",
"rate_unit_state": "L"
}
],
"geometry": "both",
"include_non_managed_areas": true
}'
{
"success": true,
"application_event_id": "019953f8-8c00-7000-8000-000000000002",
"application_time": {
"checked_at": "2026-10-05T14:10:00.000Z",
"status": "met",
"drift_status": "met",
"feature_scope": "global_only",
"non_managed_feature_count": 0,
"exclusion_feature_count": 0,
"inputs": {
"wind_direction_deg": 180,
"wind_speed_mph": 8,
"temperature_f": 72,
"humidity_percent": 55,
"application_method": "Broadcast-Ground",
"droplet_size": "very_coarse",
"boom_height": "low",
"gpa": 15
}
},
"products": [
{
"epa_number": "7969-500",
"product_name": "Liberty Ultra",
"pest": ["Waterhemp"],
"product_status": "Active",
"esa_required": true,
"pulas": []
}
],
"summary": { "total_pulas": 0, "total_limitations": 0, "products_checked": 1, "products_with_limitations": 0 },
"compliance": {
"version": 1,
"scope": "requirements_and_gaps",
"status": "met",
"drift": {
"status": "met",
"scope": "application_setup_and_treatable_area",
"requires_buffer": true,
"has_treatable_area": true
}
}
}
{
"application_time": {
"non_managed_feature_count": 1,
"non_managed_areas": {
"type": "FeatureCollection",
"features": [
{
"type": "Feature",
"geometry": {
"type": "Polygon",
"coordinates": [[[-95.4041, 43.1018], [-95.3989, 43.1018], [-95.3989, 43.0991], [-95.4041, 43.0991], [-95.4041, 43.1018]]]
},
"properties": {
"feature_type": "wetland",
"source": "protected_feature",
"distance_m": 18.4,
"product_epas": ["7969-500"],
"rules_matched": []
}
}
]
}
}
}
Refresh an application assessment with current wind and application setup.
For an application-time assessment,
Request
Optional supported category/code; nullable. An omitted value uses the saved value; explicit null clears it.
Optional
low or high; nullable. An omitted value uses the saved value; explicit null clears it.Optional positive spray gallons per acre; nullable. An omitted value uses the saved value; explicit null clears it.
Up to 100 rate changes. Each requires
product_index (zero-based), epa_number, nonnegative rate, and nonempty rate_unit; optional rate_unit_state and positive row_spacing_inches. The index and registration must match the saved product.When
true, returns the non-managed areas the drift buffer was measured from under application_time.non_managed_areas. Defaults to false.Assessment behavior
See Understanding compliance determinations for runoff and drift scoring, setup violations, overall status, and when to refresh a result. The endpoint resolves your saved application, applies current weather/setup inputs and rate changes, and returns a refreshed check plusapplication_time. Weather and the assessment are saved for that application. It checks the application revision; conflicting changes return 409.
application_time includes submitted inputs, effective rates, reductions, manual mitigation claims, feature scope, feature counts, per-edge buffers, and product-specific buffer details. Requested field-boundary output is returned under application_time.geometry and is not retained in the saved assessment snapshot.
Read compliance.drift.status for drift and compliance.status for the overall application assessment. application_time.drift_status repeats the drift result; application_time.status repeats the overall result. Runoff shortfalls and unresolved PULA restrictions can prevent an overall pass even when drift is met.
| Drift status | Meaning |
|---|---|
met | The supplied setup satisfies the configured drift rules and a treatable area has been calculated. Spray only within that area. A remaining buffer is a restriction to follow, not a failure. |
not_met | A known setup violation exists, such as droplets below the label minimum, a high boom where the rule requires low, a disallowed mitigation selection, or no treatable area remaining. Correct the setup and recompute. |
indeterminate | Required inputs or rules cannot be resolved, or a manual drift practice remains unverified. Read the issue codes. |
not_applicable | No drift requirement applies. |
compliance.drift.scope is application_setup_and_treatable_area. requires_buffer and has_treatable_area describe the calculated result; both are null when setup or rule resolution prevents calculation. A met result can have requires_buffer: true. It assesses your submitted setup and the calculated area; it does not certify where spraying actually occurred.
Use geometry: "both" to receive the buffer and treatable area together. geometry: "none" only omits the field-boundary output; it still performs the calculation and returns the same status. If setup is invalid or required rules are unresolved, requested output conservatively marks the entire field as buffer with treatable: null. When the calculated buffer consumes the whole field, drift returns not_met with NO_TREATABLE_AREA.
A successful calculation clears the generic DRIFT_CONDITIONS_UNVERIFIED issue. Specific issues remain: unknown products, missing required droplet/boom inputs, unresolved rate/wind tiers, unsupported omni-directional or downslope placement, and unverified manual practices prevent a drift pass. Rate-specific wind tiers take precedence over method-level tiers. Wind outside configured tiers returns WIND_SPEED_UNRESOLVED; the API does not infer an unconfigured wind limit. Temperature and humidity are recorded inputs, not currently evaluated label thresholds.
Non-managed areas
Some labels measure the drift buffer from a non-managed area, such as a wildlife area, wetland, or sensitive neighboring crop. For these rules, the field boundary always takes precedence. Any part of a non-managed area inside the field boundary is ignored, so an area that overlaps the field is treated as starting at the field edge. Each field edge facing the drift direction is then buffered inward by the buffer distance minus the gap to the area in front of it. Areas upwind of the field, beyond the buffer distance, or entirely inside the field boundary do not create a buffer. Setinclude_non_managed_areas: true to see which areas were considered. application_time.non_managed_areas is a GeoJSON FeatureCollection of the areas within about 1,000 ft (305 m) of the field that apply to a product with this kind of rule for your application method. Each area appears once, even when several products in the tank mix apply to it. The list shows every area evaluated, so an area can appear without changing the buffer. Like the field-boundary output, it is not retained in the saved assessment snapshot.
| Property | Description |
|---|---|
feature_type | Kind of area, such as wetland or sensitive_crop |
source | protected_feature for a mapped protected area, or sensitive_field for a nearby planted field with a sensitive crop |
distance_m | Shortest distance from the field boundary to the area, in meters; 0 when they touch or overlap |
product_epas | EPA registration numbers in the tank mix whose drift rules apply to this area |
rules_matched | Sensitivity rules matched for a sensitive_field; empty for protected features |
application_time.non_managed_feature_count is always returned and counts the areas before they are combined across products.
Protected features are read for each request so new nearby features can affect the result. Recompute after changing application conditions or mitigation selections. Application compliance and group compliance expose the saved drift.last_computation.drift_status; those GETs do not run a new placement calculation. Older snapshots have a null drift_status until recomputed.
The response also includes the refreshed products[] with each product’s PULA limitations and the summary counts, in the same shape as an ESA check. Any matching limitation adds LIMITATIONS_REVIEW_REQUIRED, which keeps the overall status indeterminate even when drift is met.
The first example shows selected response fields for an application with a remaining buffer, a treatable area, satisfied runoff, and no PULA limitations or other unresolved restrictions. The second shows application_time.non_managed_areas for an application near a wetland; the coordinates are shortened.
curl --request POST 'https://esa.acreblitz.com/api/v2/applications/019953f8-8c00-7000-8000-000000000002/drift-buffer/compute' \
--header "X-API-Key: $ACREBLITZ_API_KEY" \
--header 'Content-Type: application/json' \
--data '{
"wind_direction_deg": 180,
"wind_speed_mph": 8,
"temperature_f": 72,
"humidity_percent": 55,
"application_method": "Broadcast-Ground",
"droplet_size": "VC",
"boom_height": "low",
"gpa": 15,
"rate_updates": [
{
"product_index": 0,
"epa_number": "7969-500",
"rate": 28,
"rate_unit": "fl oz/ac",
"rate_unit_state": "L"
}
],
"geometry": "both",
"include_non_managed_areas": true
}'
{
"success": true,
"application_event_id": "019953f8-8c00-7000-8000-000000000002",
"application_time": {
"checked_at": "2026-10-05T14:10:00.000Z",
"status": "met",
"drift_status": "met",
"feature_scope": "global_only",
"non_managed_feature_count": 0,
"exclusion_feature_count": 0,
"inputs": {
"wind_direction_deg": 180,
"wind_speed_mph": 8,
"temperature_f": 72,
"humidity_percent": 55,
"application_method": "Broadcast-Ground",
"droplet_size": "very_coarse",
"boom_height": "low",
"gpa": 15
}
},
"products": [
{
"epa_number": "7969-500",
"product_name": "Liberty Ultra",
"pest": ["Waterhemp"],
"product_status": "Active",
"esa_required": true,
"pulas": []
}
],
"summary": { "total_pulas": 0, "total_limitations": 0, "products_checked": 1, "products_with_limitations": 0 },
"compliance": {
"version": 1,
"scope": "requirements_and_gaps",
"status": "met",
"drift": {
"status": "met",
"scope": "application_setup_and_treatable_area",
"requires_buffer": true,
"has_treatable_area": true
}
}
}
{
"application_time": {
"non_managed_feature_count": 1,
"non_managed_areas": {
"type": "FeatureCollection",
"features": [
{
"type": "Feature",
"geometry": {
"type": "Polygon",
"coordinates": [[[-95.4041, 43.1018], [-95.3989, 43.1018], [-95.3989, 43.0991], [-95.4041, 43.0991], [-95.4041, 43.1018]]]
},
"properties": {
"feature_type": "wetland",
"source": "protected_feature",
"distance_m": 18.4,
"product_epas": ["7969-500"],
"rules_matched": []
}
}
]
}
}
}
Errors
Endpoint-specific errors include404 APPLICATION_NOT_FOUND; 422 NO_FIELD_GEOMETRY, PRODUCT_MISMATCH, INVALID_APPLICATION, or UNSUPPORTED_APPLICATION_METHOD; and 409 DUPLICATE_FIELD, FIELD_OWNERSHIP_CONFLICT, DUPLICATE_APPLICATION, APPLICATION_FIELD_CONFLICT, PROCESSING_CONFLICT, FIELD_CHANGED, or APPLICATION_CHANGED. Signed portal setup can return 503 PORTAL_SAS_UNCONFIGURED. See assessment issues for unresolved conditions returned with HTTP 200.
All routes can also return authentication, validation, rate-limit, and dependency errors. Use the error catalog and examples to choose a retry or correction. Keep X-Request-ID when present.
