Next Week: Required Logins and Data Licensing Updates

NEON is updating how users access NEON data and the data license for NEON data products. The original announcement of this change is here; this notification serves as a reminder and an announcement of the launch date.

Starting June 30, 2026, NEON data users will be required to create a user account and either sign in or use an API token to download NEON data. In addition, NEON data products will move from a CC0 license to a Creative Commons Attribution 4.0 International (CC BY 4.0) license. These changes will help us ensure reliable data access for the NEON user community, clarify expectations for attribution, and improve our understanding of how these NSF-funded NEON data are used so we can better serve the community.

What is changing:

• Required sign‑in and tokens for downloads: You will need to create a NEON user account (if you do not have one already) and sign in to download data from the Data Portal or use an API token to download data from the API or neonUtilities. Without authentication, you can still browse information about NEON resources and view limited “snapshot” visualizations, but downloads and long time‑series visualization will be disabled.
• License update to CC BY 4.0: NEON data will be offered under CC BY 4.0. Attribution is required when you use NEON data, including a link to the license and an indication of any changes. Recommended citations will remain unchanged.
• No change to sensitive data protections: Data types previously protected (e.g., federally threatened and endangered species, state or site host species of concern) remain under the same protections.

Why NEON is making these changes:

• Why require logins and tokens?
  • In recent years, the number of automated bots and data scrapers has increased drastically. Requiring user logins will enable NEON to continue to host its free datasets in a more sustainable manner, enabling prioritization of human data users. 
  • Connecting downloads to user accounts will help NEON and the NSF understand data use to better serve the NEON data user community.
  • Required logins are standard practice for many free data providers, and this change aligns with scientific community best practices.
• Why move from the CC0 to CC BY license?
  • The CC BY license provides clearer expectations for citation and acknowledgement that are critical for tracking impact from research and applications that use NEON data.
  • CC BY requires attribution: “You must give appropriate credit, provide a link to the license, and indicate if changes were made… not in any way that suggests the licensor endorses you or your use.” See the CC BY 4.0 license: https://creativecommons.org/licenses/by/4.0/
  • Data previously downloaded under CC0 will remain under that license; and we continue to request citation and acknowledgement per community norms.

How this affects the use of NEON data:

• When the change takes effect, you will not be able to download any NEON data without a user login or token.
• NEON code packages (R neonUtilities and Python neonutilities) have been updated to work with the new API changes and alert users to the token requirement.
  Large synthesis projects and automated pipelines may require minor updates to include token‑based authentication and to ensure attribution is carried through to outputs and documentation.
• If you already cite NEON data and use authentication for data downloads, your workflows should need little to no change.

What you need to do:

• Create or sign in to your NEON user account (see the User Accounts page).
• Generate a personal API token on your NEON “My Account” page.
• Update neonUtilities to version 4.0.0 (R users) or neonutilities to version 2.0.0 (Python users).
• Update any scripts or workflows to include your token (see the token tutorial for R/Python neonUtilities). 
• If you maintain public code or documentation (e.g., GitHub repositories, workflows, or teaching materials) that use NEON data, please update them to include token authentication and CC BY attribution guidance so your users experience a smooth transition. But do not include the token itself in public-facing documents or code; your token should not be shared.
• Continue to follow NEON’s citation guidance and include attribution per CC BY 4.0 for new data use.

Questions or need help?

• See the NEON User Accounts page and API token tutorial (Set up a NEON API token) or token video (How to Create and Use a NEON API Token in R and Python) for step‑by‑step guidance.
• If you have additional questions about attribution, licensing, or technical implementation of the required tokens, please reach out through NEON’s Contact Us form and include “Required Logins or CC BY License” in the text and we will be happy to assist.