The NEON API (Application Programming Interface) can be used to quickly access NEON data and information about our data products and sampling locations. This API provides a simple means of constructing URLs that return information in a common machine-readable format, JSON (JavaScript Object Notation). To learn more, visit the FAQ, our GitHub repository, or our Using the NEON API tutorial. We also provide an R package that you can use to download and reformat the data.    


Tell us what you think: If you have design ideas, functionality requests, bug notes, examples of how you used the API, or anything else you would like us to know, please file an issue and tell us about it! This API will be enhanced as we receive feedback from the community.

Swagger UI

Endpoint Notes


The /products endpoint provides information about NEON data products, including availability by site and month (also see the data product catalog). In the API, data products are specified using a 13 character code. For instance, Chemical properties of groundwater uses product code DP1.20092.001, where DP1 refers to data level 1 (quality controlled), 20092 is the unique numeric id of the data product, and 001 refers to the revision. All of our data products are currently provisional and annotated as revision 1.


The /sites endpoint provides information about NEON field sites where data are currently available.  Numerous data products are produced from each site. Site names are abbreviated into four-letter site codes -- for example, the Arikaree River site abbreviation is ARIK. For more information about sites, you can find a listing on our main website. If you need to know about our remote sensing data availability, visit the Airborne Data webpage.


The /locations endpoint provides more detailed information about where NEON collects data than the /sites endpoint. A location is any discrete place or administrative region in the NEON system, ranging from our huge ecoregions (domains) to single data collection points. There are more than 150,000 locations in the NEON system. Examples of locations include Domain 02, or the Central Plains Experimental Range, Plot 11, mammal collection point A10, or Niwot Ridge Mountain Research Station Megapit MP1. Note that location names are case-sensitive.

REALM is the top of the location hierarchy, and contains all of the domain names as "locationChildren". Each domain, in turn, contains all of its site codes. Each site contains towers, measurement plots, observation spots, and more. By traversing this hierarchy of locations, information about any point in the NEON system is available.


The /data endpoint shows which monthly data files are available, and provides URLs to downloadable files. Several terabytes of data are presently available. To keep data files to a reasonable size, they are generally arranged in product/site/monthly chunks. Even so, files can be large and you may find it worthwhile to check the size attribute before downloading. Also note that the provided URLs are from an Amazon S3 service and expire about 24 hours after generation. If the time between when you obtain a URL and start downloading the file is more than 24 hours, you may need to obtain a new URL before proceeding.


The /taxonomy endpoint provides acess to NEON's taxon lists for major groupings such as plants, algae, beetles, and small mammals. Taxon lists are compiled from a variety of published sources, and are primarily used by field staff to constrain data entry to verified scientific names and known geographic ranges. For more information, visit the Taxonomic Lists webpage. Note that the offset and limit parameters currently have default values of 50; you may wish to use an offset value of 0 and adjust the limit value to support larger recordsets. Also note that the scientificname parameter only supports exact, not fuzzy, string matching.


NEON Data Policy