Fieldprint API – Order of Fieldprint Analysis
The /v5/Calculator endpoint requires a complete crop interval history from 2008 to the present. Each interval in the history represents one crop year on the field. However, the API only generates a full Fieldprint Analysis — with all eight sustainability metrics and benchmarks — for one interval per request. This page explains how the API determines which interval gets analyzed and how to generate analyses for multiple years.
Access to the Fieldprint Platform and API requires Field to Market membership and an active Data Management Licensing Agreement. Learn more about membership and our data partner program to get started.
The Key Rule
The analysis year is determined by the most recent harvest_year value across all entries in the crop_intervals array. The API will compute the full suite of sustainability metrics — Land Use, Soil Conservation, Soil Carbon, Energy Use, GHG Emissions, Irrigation Water Use, Water Quality, and Biodiversity — for that interval only.
For example, if your request includes crop intervals from 2008 through 2024 and the most recent interval is 2024 Corn (grain), the API will analyze the 2024 Corn interval — even if you intended to analyze 2023 Soybean. The earlier intervals in the history provide the crop rotation context needed by the environmental models (particularly SWAT+ for Soil Carbon), but they do not receive their own analysis.
Two Levels of Interval Data
Not every interval in the crop history needs the same level of detail. There are two tiers of data that the API expects:
| Data Level | Applies To | What’s Needed |
|---|---|---|
| Full Data | The analysis year (most recent interval) | Complete activities with all inputs — tillage operations, planting, harvest, fertilizer applications, cover crops, irrigation, and any crop-specific fields. This is the interval that receives the Fieldprint Analysis. |
| Minimum Data | All historical intervals (prior years) | The core fields needed to estimate annual soil carbon stock changes: crop type, yield, commercial nitrogen, tillage class, cover crop, and irrigation status. Use the /v5/FieldData/PrefillFieldHistory endpoint to generate default values for these intervals. |
/v5/FieldData/PrefillFieldHistory endpoint can generate a baseline crop history from 2008 to the present using USDA Cropland Data Layer (CDL) data for your field geometry. This gives you a starting point for the historical intervals that you can then refine with known management details.
Generating Analyses for Multiple Years
Because the API analyzes only the most recent interval per request, generating Fieldprint Analyses for multiple crop years requires multiple sequential requests. Each request should include the full crop history up through the year you want analyzed — but stop at that year.
Work from the earliest desired analysis year forward to the most recent:
The 2022 interval should contain full data. Earlier intervals need minimum data only.
Result: Fieldprint Analysis for 2022 Corn (grain).
The 2023 interval should contain full data. The 2022 interval can now revert to minimum data.
Result: Fieldprint Analysis for 2023 Soybean.
The 2025 interval should contain full data. All prior intervals need minimum data only.
Result: Fieldprint Analysis for 2025 Corn (grain).
Example Scenario
Suppose a QDMP has collected full management data for three years on a field with a corn/soybean rotation and wants to generate Fieldprint Analyses for 2022, 2023, and 2025.
| Request | Intervals Included | Analysis Year | Crop Analyzed |
|---|---|---|---|
| 1st | 2008 – 2022 | 2022 | Corn (grain) |
| 2nd | 2008 – 2023 | 2023 | Soybean |
| 3rd | 2008 – 2025 | 2025 | Corn (grain) |
Each request produces a separate Fieldprint Analysis with its own set of metrics, benchmarks, and (if options.report.generate is true) a PDF report URL. The soil carbon results will be most accurate for later years because the model has more rotation history to work with.
Common Mistakes
Reach out to support@fieldtomarket.org with additional questions on implementation.
This documentation reflects the Fieldprint Platform API v5.0.2 as of April 2026. The Fieldprint Platform is actively developed and implementation details may evolve between releases. While we work to keep this reference accurate, we encourage API partners to validate behavior against the live API and reference data endpoints. The Field to Market team is available to support your integration — contact support@fieldtomarket.org or your partner liaison with any questions.