NAV

Home

Getting Started

Authentication

You do not need to authenticate in order to explore the NASA data. However, if you will be intensively using the APIs to, say, support a mobile application, then you should sign up for a NASA developer key.

Web Service Rate Limits

Limits are placed on the number of API requests you may make using your API key. Rate limits may vary by service, but the defaults are:

For each API key, these limits are applied across all api.nasa.gov API requests. Exceeding these limits will lead to your API key being temporarily blocked from making further requests. The block will automatically be lifted by waiting an hour. If you need higher rate limits, contact us.

DEMO_KEY Rate Limits

In documentation examples, the special DEMO_KEY api key is used. This API key can be used for initially exploring APIs prior to signing up, but it has much lower rate limits, so you’re encouraged to signup for your own API key if you plan to use the API (signup is quick and easy). The rate limits for the DEMO_KEY are:

How Do I See My Current Usage?

Your can check your current rate limit and usage details by inspecting the X-RateLimit-Limit and X-RateLimit-Remaining HTTP headers that are returned on every API response. For example, if an API has the default hourly limit of 1,000 request, after making 2 requests, you will receive this HTTP header in the response of the second request:

X-RateLimit-Remaining: 998

The hourly counters for your API key reset on a rolling basis.

Example: If you made 500 requests at 10:15AM and 500 requests at 10:25AM, your API key would become temporarily blocked. This temporary block of your API key would cease at 11:15AM, at which point you could make 500 requests. At 11:25AM, you could then make another 500 requests.

APOD

One of the most popular websites at NASA is the Astronomy Picture of the Day. In fact, this website is one of the most popular websites across all federal agencies. It has the popular appeal of a Justin Bieber video. This endpoint structures the APOD imagery and associated metadata so that it can be repurposed for other applications. In addition, if the concept_tags parameter is set to True, then keywords derived from the image explanation are returned. These keywords could be used as auto-generated hashtags for twitter or instagram feeds; but generally help with discoverability of relevant imagery.

Example image:

HTTP Request

GET https://api.nasa.gov/planetary/apod

concept_tags are now disabled in this service. Also, an optional return parameter copyright is returned if the image is not public domain.

Query Parameters

Parameter Type Default Description
date YYYY-MM-DD today The date of the APOD image to retrieve
hd bool False Retrieve the URL for the high resolution image
api_key string DEMO_KEY api.nasa.gov key for expanded usage

Example query

https://api.nasa.gov/planetary/apod?api_key=DEMO_KEY

Asteroids - NeoWs

NeoWs (Near Earth Object Web Service) is a RESTful web service for near earth Asteroid information. With NeoWs a user can: search for Asteroids based on their closest approach date to Earth, lookup a specific Asteroid with its NASA JPL small body id, as well as browse the overall data-set.

Data-set: All the data is from the NASA JPL Asteroid team (http://neo.jpl.nasa.gov/).

This API is maintained by SpaceRocks Team: David Greenfield, Arezu Sarvestani, Jason English and Peter Baunach.

Neo - Feed

Retrieve a list of Asteroids based on their closest approach date to Earth. GET https://api.nasa.gov/neo/rest/v1/feed?start_date=START_DATE&end_date=END_DATE&api_key=API_KEY

Query Parameters

Parameter Type Default Description
start_date YYYY-MM-DD none Starting date for asteroid search
end_date YYYY-MM-DD 7 days after start_date Ending date for asteroid search
api_key string DEMO_KEY api.nasa.gov key for expanded usage

Example query

https://api.nasa.gov/neo/rest/v1/feed?start_date=2015-09-07&end_date=2015-09-08&api_key=DEMO_KEY

Neo - Lookup

Lookup a specific Asteroid based on its NASA JPL small body (SPK-ID) ID GET https://api.nasa.gov/neo/rest/v1/neo/

Path Parameters

Parameter Type Default Description
asteroid_id int none Asteroid SPK-ID correlates to the NASA JPL small body
api_key string DEMO_KEY api.nasa.gov key for expanded usage

Example query

https://api.nasa.gov/neo/rest/v1/neo/3542519?api_key=DEMO_KEY

Neo - Browse

Browse the overall Asteroid data-set GET https://api.nasa.gov/neo/rest/v1/neo/browse/

Example query

https://api.nasa.gov/neo/rest/v1/neo/browse?api_key=DEMO_KEY

Neo - Live Documents

EPIC

The EPIC API provides information on the daily imagery collected by DSCOVR's Earth Polychromatic Imaging Camera (EPIC) instrument. Uniquely positioned at the Earth-Sun Lagrange point, EPIC provides full disc imagery of the Earth and captures unique perspectives of certain astronomical events such as lunar transits using a 2048x2048 pixel CCD (Charge Coupled Device) detector coupled to a 30-cm aperture Cassegrain telescope.

Image metadata and key information are provided by the JSON API and can be requested by date and for the most recent available date. A listing of all available dates can also be retrieved via the API for more granular control.

Development of the EPIC API began in 2015, and is supported by the web development team for the Laboratory for Atmospheres in the Earth Sciences Division of the Goddard Space Flight Center. More information regarding the API and retrieval of the imagery for download can be found on the EPIC website.

Retrievable Metadata

The following information is available for every image in the collection:


Example image:

Querying by Date(s)

Parameter Type Default Description
natural string Most Recent Natural Color Metadata on the most recent date of natural color imagery.
natural/date YYYY-MM-DD Most Recent Available Metadata for natural color imagery available for a given date.
natural/all string Dates for Natural Color A listing of all dates with available natural color imagery.
natural/available string Dates for Natural Color Alternate listing of all dates with available natural color imagery.
enhanced string Most Recent Enhanced Color Metadata on the most recent date of enhanced color imagery.
enhanced/date YYYY-MM-DD Most Recent Available Metadata for enhanced color imagery for a given date.
enhanced/all string Dates for Enhanced Imagery A listing of all dates with available enhanced color imagery.
enhanced/available string Dates for Enhanced Imagery Alternate listing of all dates with available enhanced color imagery.
api_key string DEMO_KEY API key from api.nasa.gov for expanded usage.

Example queries

https://api.nasa.gov/EPIC/api/natural/images?api_key=DEMO_KEY
https://api.nasa.gov/EPIC/api/natural/date/2015-10-31?api_key=DEMO_KEY
https://api.nasa.gov/EPIC/api/enhanced/all?api_key=DEMO_KEY
https://api.nasa.gov/EPIC/archive/enhanced/2016/12/04/png/epic_RBG_20161204003633_01.png?api_key=DEMO_KEY

More examples and usage tips can be found on the EPIC API Documentation Page.

 

EONET

More and more NASA imagery is being made available via web services (WMS, WMTS, etc.) and a significant percentage of it is being produced and published in near real time (NRT = within a few hours after acquisition). This ability means that NASA imagery can be used more routinely to examine current natural events as they happen.

Using client applications, such as NASA EOSDIS’ Worldview, users can browse the entire globe daily and look for natural events as they occur. Storms are regularly spotted in the tropics, dust storms over deserts, forest fires in the summers. These events are occurring constantly and NASA NRT imagery can represent them all using a variety of different data parameters. However, the user’s experience is tailored, and therefore restricted, by the client application. What if there was an API that provided a curated list of natural events and provided a way to link those events to event-related NRT image layers? Enter EONET.

The Earth Observatory Natural Event Tracker (EONET) is a prototype web service with the goal of:

providing a curated source of continuously updated natural event metadata; providing a service that links those natural events to thematically-related web service-enabled image sources (e.g., via WMS, WMTS, etc.). Please see our API documentation to learn more about how to use the EONET web services.

Development of EONET began in 2015 and has been supported by NASA’s Earth Observatory and Earth Science Data and Information System (ESDIS) Project.

Earth

A recent industry report estimates that total annual value of $2.19 billion, far exceeding the multi-year total cost of building, launching, and managing Landsat satellites and sensors. The value is derived from consumer use of the data. There is no inherent value in idle data. The objective of this endpoint is to unlock the significant public investment in earth observation data. This open and documented API should dramatically reduce the transaction costs to engage with the imagery.The API is powered by Google Earth Engine, and currently only supports pan-sharpened Landsat 8 imagery.

Example image:

Imagine the possibilities associated with this imagery, like monitoring deforestation at 15-meter resolution or assessing the damage from natural disasters. If you discover any cool applications, please let us know so that we can showcase them on open.nasa.gov.

Imagery

This endpoint retrieves the Landsat 8 image for the supplied location and date. The response will include the date and URL to the image that is closest to the supplied date. The requested resource may not be available for the exact date in the request. You can retrieve a list of available resources through the assets endpoint.

The cloud score is an optional calculation that returns the percentage of the queried image that is covered by clouds. If False is supplied to the cloud_score parameter, then no keypair is returned. If True is supplied, then a keypair will always be returned, even if the backend algorithm is not able to calculate a score. Note that this is a rough calculation, mainly used to filter out exceedingly cloudy images.

HTTP Request

GET https://api.nasa.gov/planetary/earth/imagery

Query Parameters

Parameter Type Default Description
lat float n/a Latitude
lon float n/a Longitude
dim float 0.025 width and height of image in degrees
date YYYY-MM-DD today date of image; if not supplied, then the most recent image (i.e., closest to today) is returned
cloud_score bool False calculate the percentage of the image covered by clouds
api_key string DEMO_KEY api.nasa.gov key for expanded usage

Example query

https://api.nasa.gov/planetary/earth/imagery?lon=100.75&lat=1.5&date=2014-02-01&cloud_score=True&api_key=DEMO_KEY

Assets

This endpoint retrieves the date-times and asset names for available imagery for a supplied location. The satellite passes over each point on earth roughly once every sixteen days. This is an amazing visualization of the acquisition pattern for Landsat 8 imagery. The objective of this endpoint is primarily to support the use of the imagery endpoint.

HTTP Request

GET https://api.nasa.gov/planetary/earth/assets

Query Parameters

Parameter Type Default Description
lat float n/a Latitude
lon float n/a Longitude
begin YYYY-MM-DD n/a beginning of date range
end YYYY-MM-DD today end of date range
api_key string DEMO_KEY api.nasa.gov key for expanded usage

Example query

https://api.nasa.gov/planetary/earth/assets?lon=100.75&lat=1.5&begin=2014-02-01&api_key=DEMO_KEY

Mars Rover Photos

This API is designed to collect image data gathered by NASA's Curiosity, Opportunity, and Spirit rovers on Mars and make it more easily available to other developers, educators, and citizen scientists. This API is maintained by Chris Cerami.

Each rover has its own set of photos stored in the database, which can be queried separately. There are several possible queries that can be made against the API. Photos are organized by the sol (Martian rotation or day) on which they were taken, counting up from the rover's landing date. A photo taken on Curiosity's 1000th Martian sol exploring Mars, for example, will have a sol attribute of 1000. If instead you prefer to search by the Earth date on which a photo was taken, you can do that too.

Along with querying by date, results can also be filtered by the camera with which it was taken and responses will be limited to 25 photos per call. Queries that should return more than 25 photos will be split onto several pages, which can be accessed by adding a 'page' param to the query.

Each camera has a unique function and perspective, and they are named as follows:

Rover Cameras

Abbreviation Camera Curiousity Opportunity Spirit
FHAZ Front Hazard Avoidance Camera
RHAZ Rear Hazard Avoidance Camera
MAST Mast Camera
CHEMCAM Chemistry and Camera Complex
MAHLI Mars Hand Lens Imager
MARDI Mars Descent Imager
NAVCAM Navigation Camera
PANCAM Panoramic Camera
MINITES Miniature Thermal Emission Spectrometer (Mini-TES)

Querying by Martian sol

Parameter Type Default Description
sol int none sol (ranges from 0 to max found in endpoint)
camera string all see table above for abbreviations
page int 1 25 items per page returned
api_key string DEMO_KEY api.nasa.gov key for expanded usage

Example queries

https://api.nasa.gov/mars-photos/api/v1/rovers/curiosity/photos?sol=1000&api_key=DEMO_KEY

https://api.nasa.gov/mars-photos/api/v1/rovers/curiosity/photos?sol=1000&camera=fhaz&api_key=DEMO_KEY

https://api.nasa.gov/mars-photos/api/v1/rovers/curiosity/photos?sol=1000&page=2&api_key=DEMO_KEY

Querying by Earth date

Parameter Type Default Description
earth_date YYYY-MM-DD none sol (ranges from 0 to max found in endpoint)
camera string all see table above for abbreviations
page int 1 25 items per page returned
api_key string DEMO_KEY api.nasa.gov key for expanded usage

Example query

https://api.nasa.gov/mars-photos/api/v1/rovers/curiosity/photos?earth_date=2015-6-3&api_key=DEMO_KEY

Mission Manifest

A mission manifest is available for each Rover at /manifests/rover_name. This manifest will list details of the Rover's mission to help narrow down photo queries to the API. The information in the manifest includes:

Key Description
name Name of the Rover
landing_date The Rover's landing date on Mars
launch_date The Rover's launch date from Earth
status The Rover's mission status
max_sol The most recent Martian sol from which photos exist
max_date The most recent Earth date from which photos exist
total_photos Number of photos taken by that Rover

It also includes a list of objects under the "photos" key which are grouped by sol, and each of which contains:

Key Description
sol Martian sol of the Rover's mission
total_photos Number of photos taken by that Rover on that sol
cameras Cameras for which there are photos by that Rover on that sol

An example entry from a sol at /manifests/Curiosity might look like:

{ sol: 0, total_photos: 3702, cameras: [ "CHEMCAM", "FHAZ", "MARDI", "RHAZ" ] }

This would tell you that this rover, on sol 0, took 3702 photos, and those are from among the CHEMCAM, FHAZ, MARDI, and RHAZ cameras.

Patents

The NASA patent portfolio is available to benefit US citizens. Through partnerships and licensing agreements with industry, these patents ensure that NASA’s investments in pioneering research find secondary uses that benefit the economy, create jobs, and improve quality of life. This endpoint provides structured, searchable developer access to NASA’s patents that have been curated to support technology transfer.

HTTP Request

GET https://api.nasa.gov/patents

Query Parameters

Parameter Type Default Description
query string None Search text to filter results
concept_tags bool False Return an ordered dictionary of concepts from the patent abstract
limit int all number of patents to return
api_key string DEMO_KEY api.nasa.gov key for expanded usage

Example query

https://api.nasa.gov/patents/content?query=temperature&limit=5&api_key=DEMO_KEY

Sounds (beta)

Sound exists in space. Sometimes. And NASA has released a series of space sounds via sound cloud. We have abstracted away some of the hassle in accessing these sounds, so that developers can play with the audio files. For example, a useful application would be an automatic filter to identify human voices in these audio files. For now, that would help identify content. Later, however, when we retrieve sounds from far-off planets, we can apply the filter to identify unknown human space colonies. That was a joke. Sort of.

HTTP Request

GET https://api.nasa.gov/planetary/sounds

Query Parameters

Parameter Type Default Description
q string None Search text to filter results
limit int 10 number of tracks to return
api_key string DEMO_KEY api.nasa.gov key for expanded usage

Example query

https://api.nasa.gov/planetary/sounds?q=apollo&api_key=DEMO_KEY

SSD/CNEOS

Welcome to JPL’s SSD (Solar System Dynamics) and CNEOS (Center for Near-Earth Object Studies) API (Application Program Interface) service. This service provides an interface to machine-readable data (JSON-format) related to SSD and CNEOS.If you are looking for human-readable data, please go to the main websites for SSD and/or CNEOS. For further information on this API and its four services, please visit the JPL SSD/CNEOS API main website or contact contact-ssd-api@jpl.nasa.gov.

This API consists of the following four services:

API Description
CAD Asteroid and comet close approaches to the planets in the past and future
Fireball Fireball atmospheric impact data reported by US Government sensors
NHATS Human-accessible NEOs data
Sentry NEO Earth impact risk assessment data

CAD

This API provides access to current close-approach data for all asteroids and comets in JPL’s SBDB (Small-Body DataBase). Defaults for query parameters are setup for a typical CNEOS web-site search: NEO Earth close-approaches less than 0.05 au in the next 60 days sorted by date.

For complete API documentation please visit the JPL SBDB Close-Approach Data API website.

Fireball

The fireball data API provides a method of requesting specific records from the available data-set. Every successful query will return content representing one or more fireball data records. See the CNEOS page on fireballs for details on this data-set.

For complete API documentation please visit the JPL Fireball Data API website.

NHATS

The NHATS API provides a method of requesting data from the NHATS-related tables in the SBDB. These data will primarily support the CNEOS “Accessible NEAs” web-page. Please see the NHATS web-page for details about NHATS.

For complete API documentation please visit the JPL NHATS API website.

Sentry

This API provides access to results from the CNEOS Sentry system. There are various "modes" used to obtain desired data. * O - object-specific details table * S - summary table * V - VI (virtual impactor) table * R - removed-objects table

For complete API documentation please visit the JPL Sentry API website.

Techport

Welcome to TechPort - NASA's resource for collecting and sharing information about NASA-funded technology development. Techport allows the public to discover the technologies NASA is working on every day to explore space, understand the universe, and improve aeronautics. NASA is developing technologies in areas such as propulsion, nanotechnology, robotics, and human health. NASA is committed to making its data available and machine-readable through an Application Programming Interface (API) to better serve its user communities. As such, the NASA TechPort system provides a RESTful web services API to make technology project data available in a machine-readable format. This API can be used to export TechPort data into either an XML or a JSON format, which can then be further processed and analyzed. Complete documentation (in Swagger 2.0 format) of the available objects, properties, RESTful URIs is available in the online API specification at:
https://api.nasa.gov/techport/api/specification?api_key=DEMO_KEY.

In general, queries can be issued to the system with the following URI format:

GET https://api.nasa.gov/techport/api/items/{id_parameter}?api_key=DEMO_KEY

Parameter Required? Value Description
id_parameter Yes Type: int
Default: None
The id value of the TechPort record. ID values can be obtained through the standard TechPort search feature and are visible in the website URLs, e.g. http://techport.nasa.gov/view/0000, where 0000 is the ID value. Alternatively, a request to /api/items will display all valid IDs in the system.

Example Queries

GET https://api.nasa.gov/techport/api/items/17792?api_key=DEMO_KEY

GET https://api.nasa.gov/techport/api/items/17792.json?api_key=DEMO_KEY

GET https://api.nasa.gov/techport/api/items?api_key=DEMO_KEY

GET https://api.nasa.gov/techport/api/items?updatedSince=2016-01-01&api_key=DEMO_KEY

For more information on Techport and additional example usage please visit http://techport.nasa.gov.

Trek WMTS

Here we have the collection of APIs that power the awesome Mars Trek and Vesta Trek NASA web-based portals for exploration. Both APIs can be leveraged using your favorite OGC RESTFul Web Map and Tile Service (WMTS) client. Please visit http://www.opengeospatial.org/standards/wmts for more information about WMTS. To help you get started, we've included some demos using the ESRI javascript client library for Mars and Vesta.

This API is maintained and provided by the NASA Solar System Exploration Research Virtual Institute (SSERVI) and the Jet Propulsion Lab (JPL) Trek team.

Available Mars Mosaics

Mosaic Preview WMTS Capabilities
Viking Color Mosaic - Global Map Preview WMTS Capabilities
CTX Mosaic - Curiosity Landing Site Preview WMTS Capabilities
HiRISE Mosaic - Curiosity Landing Site Preview WMTS Capabilities
HiRISE Mosaic - ESP_040776_2115 Preview WMTS Capabilities
HiRISE Mosaic - ESP_042252_1930_RED_B_01_ORTHO Preview WMTS Capabilities
HiRISE Mosaic - ESP_042647_1760_RED_B_01_ORTHO Preview WMTS Capabilities
HRSC Mosaic - Martian East Preview WMTS Capabilities
HRSC Color Mosaic - MC11 Preview WMTS Capabilities
HRSC Mosaic - MC11 Preview WMTS Capabilities
HiRISE Mosaic - Spirit Landing Site Preview WMTS Capabilities
HiRISE Mosaic - Opportunity Landing Site Preview WMTS Capabilities
HiRISE Mosaic - Phoenix Landing Site Preview WMTS Capabilities
HiRISE Mosaic - Sojourner Landing Site Preview WMTS Capabilities
Albedo Mosaic - Thermal Emission Spectrometer Preview WMTS Capabilities
DEM Grayscale - Mars Orbiter Laser Altimeter Preview WMTS Capabilities
Color Hillshade - Mars Orbiter Laser Altimeter Preview WMTS Capabilities
Experience Curiosity - Curiosity Landing Site Preview WMTS Capabilities
Atlas Mosaic - Mars Orbiter Camera Preview WMTS Capabilities
Infrared Night - Thermal Emission Imaging System Preview WMTS Capabilities
Infrared Day - Thermal Emission Imaging System Preview WMTS Capabilities
HRSC Mosaic - Mawrth Vallis Preview WMTS Capabilities
HRSC Color Mosaic - Mawrth Vallis Preview WMTS Capabilities

Available Vesta Mosaics

Mosaic Preview WMTS Capabilities
global_LAMO Preview WMTS Capabilities
Vesta_Dawn_HAMO_DTM_DLR_Global_48ppd 8Bit Preview WMTS Capabilities
Vesta_Dawn_Geology_Global_32ppd_IAU Preview WMTS Capabilities
Vesta_Dawn_HAMO_ClrShade_DLR_Global_48ppd_IAU Preview WMTS Capabilities
Vesta_Dawn_HAMO_MinRatio_DLR_global_74ppd_IAU Preview WMTS Capabilities
Vesta_Dawn_HAMO_Shade_DLR_Global_48ppd_IAU Preview WMTS Capabilities
Vesta_Dawn_HAMO_TrueClr_DLR_global_74ppd Preview WMTS Capabilities