Base URL
/api/v1.
Authentication
All endpoints require a valid API key in theX-API-Key header. See Authentication for details.
Endpoints
| Method | Endpoint | Description |
|---|---|---|
POST | /api/v1/esa-check | Check ESA/PULA restrictions for a pesticide application |
GET | /api/v1/fields/{provider_field_id}/reports/enlist | Download Enlist Mitigation PDF report |
GET | /api/v1/fields/{provider_field_id}/reports/runoff | Download EPA Runoff Mitigation PDF report |
Status Codes
| Code | Meaning | Description |
|---|---|---|
200 | Success | Request completed successfully |
400 | Bad Request | Invalid parameters or malformed request body |
401 | Unauthorized | Invalid or missing API key |
404 | Not Found | Field or report not found |
500 | Internal Server Error | Server error — contact support if it persists |
502 | Bad Gateway | Upstream report generation failed |
504 | Gateway Timeout | Report generation timed out |
Idempotency
The ESA Check endpoint is idempotent based on theapplication_id field. Submitting the same application_id with updated data will refresh the results for that application rather than creating a duplicate. This makes it safe to retry requests or update application details.
Rate Limiting
API requests are rate limited to ensure fair usage. If you exceed the limit, you will receive a429 Too Many Requests response. Contact support if you need a higher rate limit for your integration.