Farm Market iD API - FAQs
Public API Portal

Frequently Asked Questions

Public API Help

Version 1


The General area is where you can find nonspecific questions and answers to help guide your path while using the Farm Market iD API.

Top of page

What are media types?

Media types are used in the API to let consumers choose the format of the data they want to receive.

What media types does the API return?

In the header of the Request simply change the Content-Type.

Acceptable Type for Farm Market iD API is the following: "application/json"

Some common examples of Content Types are:
  • “text/plain”
  • “text/html”
  • “application/xml”
  • “application/json”
  • “image/jpeg”
  • “image/png”

How do I format or make a request?

Simply open a browser of your choice, type the URL:

Scroll down the page to view the available URI(Endpoints), using the GET | POST methods; you will see how to make a request. Using the browser, you can retrieve “Sandbox” data, that mimics the output of the possible data returned from each of the endpoints.

For example:

Error Handling – I received HTTP Status codes: [100-199 | 200-299 | 300-399 | 400-499 | 500-599], what does this mean?

HTTP Status Code Reference:
[100 - 199] Informational Responses
the request was received, continuing process
[200 - 299] Successful Responses
the request was successfully received, understood, and accepted
[300 - 399] Redirects
further action needs to be taken in order to complete the request
[400 - 499] Client Errors
the request contains bad syntax or cannot be fulfilled
[500 - 599] Server Errors
the server failed to fulfil an apparently valid request


The V1_Land area provides land and grower specific data, containing past, present, and future information regarding land, crops, irrigation, and much more.

Top of page

How can I find land?

Beginning with our broadest URI (endpoint); having a relative location; this endpoint can assist in locating a specific piece of land, crop status, and much more.

For example:


** The results returned provide detailed specifics concerning land and crops. **

How can I find out what grower owns or operates a particular piece of land?

Try using either of the following routes:

  • GET api/v1/land/{fmid_land_id}/crop-year/{year}
  • GET api/v1/land/{fmid_land_id}/crop/{season_type}

How can I find out what year and crops are grown on a particular piece of land?

Use the following route:

  • GET api/v1/land/{fmid_land_id}/crop-year/{year}

This route will provide Land Crop details for a provided FMID_Land_Id and year; if you enter ‘ALL’, or ‘all’ in lieu of a specific year; all crop details and the year would be returned.


The V1_Grainbin section of the API allows a consumer to capture the number of grain bins a farmer has in their operations. Additionally, combining that data with the location of each bin helps to determine how far that storage is spread out.

Top of page

How do I find a grainbin?(starting with our broadest search to locate targeted data)

If you have a general area where you have targeted a specific land, you may want to use the following route to obtain more granular data.

  • GET api/v1/grainbin/lat/{lat}/lon/{lon}/radius/{radius_in_meters}Minimum 1 and a Maximum of 10,000 meters

How to take specific data from our broad search to find more specific details relating to that grainbin; traversing V1_Grainbin?

For example, if after searching a broader search and you have obtained a FMID_Bin_Id you can use that identifier in other routes to find more specific details.

GET api/v1/grainbin/{fmid_bin_id}/pos/{radius_in_miles} Minimum 1 and a Maximum of 50 miles
Provides POS location details based on a specified radius of the bin location.

** The Point of Sale location details provide the more specific details relative to that grain bin. **

Another example, if after searching a broader search and you have obtained a FMID_Land_Id you can use that identifier in other routes to find more specific details.

GET api/v1/grainbin/land/{fmid_land_id}
Provides grain bin details for a specified FMID_Land_Id.


The V1_Grower section of the API allow a consumer to capture grower field boundaries linking U.S farmland to the operators and owners. Efficiently enabling users to consume the farmer’s entire crop and livestock mix from over 200 crop and livestock codes and summaries. URIs (endpoints) featured in Version allows access of seven years worth of grower data, related growers that either own or co-operate the farm.

Top of page

How to traverse V1_Grower to locate specific data? For example, I have only a Grower_ID, but I would like to know what land is associated with that specific grower.

Using the Farm Market iD API URI (endpoint): GET api/v1/grower/{grower_id}/land

Enter the requested parameter; {grower_id}, the Results returned provides all associated FMID_Land_Ids to the specific Grower_ID. That FMID_Land_Id could be used in other URIs (endpoints) to targeted more specific areas.

How do I obtain a Growers' Gross Farm Income (GFI)?

GFI, can be obtained in several different ways, to demonstrate one way. A consumer must have a valid grower's id; use the ID in one of the routes that contains the words enterprise-type. Supplying the required parameters to the URI of the route type will provide an Enterprise_Code, Enterprise_Year, and an Enterprise_Code.


The V1_Geospatial has been provided to deliver the geometic shape and the pixelated coordinates of the land or grower objects. This section is the most granulated data within our API.

Top of page

Why is Geospatial Intelligence important for the Ag Market?

Geospatial intelligence is helping the Ar Market in making critical decison relating to many areas within agriculture. This information allows leaders to know what is happening, why and where events are occuring.

Can I receive Common Land Unit (CLU) data from the Geospaital URI (endpoint)?

A Common Land Unit (CLU) is the smallest unit of land that has a permanent, contiguous boundary, a common land cover and land management, a common owner and a common producer in agricultural land associated with USDA farm programs. CLU boundaries are delineated from relatively permanent features such as fence lines, roads, and/or waterways.

Farm Market iD has this data and is provided as GeoJSON from the land requests in the Geospatial Controller. GeoJSON is simply another format used for spatial data, which is suitable for machine to machine communication.

The API does not limit the data to CLU data only, and will return all FMID Land data also.

What is GeoJSON?

GeoJSON is an open standard format designed for representing simple geographical features, along with their non-spatial attributes.

The features include points: addresses and locations, line strings: streets, highways and boundaries, polygons: countries, provinces, tracts of land, and multi-part collections of these types.

What data is being returned in our V1_Geospatial object?

Although the data is returned in one property: Land_Geometry as a GeoJSON object. The data contained within this object contains the following items:

GET & POST methods for Geospatial Grower Output:
[lat decimal, lon decimal]
fmid_land_id, grower_id, zip_cd, primary, producer_cd, acres, crop, fips_cd, county, lat, lon
GET & POST methods for Geospatial FMID_Land_Id Output:
[lat decimal, lon decimal]
fmid_land_id, lat, lon, acres, crop, fips_cd, zip_cd, mtrs, name_status, crop_status


The V1_Dictionary has been provided to assist for the purpose of translating codes into values. Additionally, Farm Market iD uses a custom agriculture annual system and store upto seven years of annual data.

Top of page

What is the purpose of V1_Dictionary Endpoints?

This area is a collection of informative information that will help you to decode a code returned in a result set. Also help a consumer to determine what years represent our season types, decode a specific FIPS Code, and much more.

How to traverse the V1_Dictionary Endpoint?

Use any of the URI(endpoints) within the V1_Dictionary routes, enter a code, "all", or "All"; usually will provide a list of code(s) and the value associated with those particular code(s). Some of the URI(endpoints) within the Farm Market iD API requires a particular code in order to access certain data. The dictionary is available to assiste with that.


The V1_Log has been provided to track traffic and users of API. The returned data provides who, when, and what routes are being utilizated by an organiazation.

Top of page

Why does these routes not require any parameters?

This route uses the API-Keys that is populated within the Header of every request. The route records each specific IP Address for any user of the API.

What is the maximum number of months I can retrieve data for in log details route?

The route retrieves the last 1,000 requests.

Can I retrieve user specific log data?

No. The log data is recorded based upon the API-Keys that is populated within the Header of every request.

Enhancement Requests

If the featured URIs (endpoints) are not quite meeting your current needs, we ask that you submit an enhancement request detailing your specific requirements. Each request will be evaluated individually and incorporated quaterly if applicable.

Thank you

To Top