Asteroid Feed

nasa.neo_feed
ActionBusiness appsconnection required

Calls the NASA API with the connection's credentials.

List near-Earth asteroids by their closest approach date.

Connection

Required
Yes — the node will not save without one
Auth type
API key
Providers
NASA
Secret shape
the API key, or {"api_key": "…"}
Config it needs
base_url, images_base_url
Resolved by
config.connection_id, else node.connection_id

Configuration

2 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
start_date
First closest-approach date to search from.
stringYes—matches ^\d{4}-\d{2}-\d{2}$2015-09-07
end_date
Last closest-approach date to search to; NASA uses seven days after the start date when it is blank, and refuses a wider window.
stringNo—matches ^\d{4}-\d{2}-\d{2}$2015-09-08

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "end_date": "2015-09-08",
  "start_date": "2015-09-07"
}

Output

One shape.

result

FieldTypeExample
near_earth_objects
NASA's own response, keyed by close-approach date.
object—
asteroids
The same asteroids flattened across every date.
array—
element_count
NASA's own count of matching asteroids.
number—
asteroids[].id
The asteroid's NeoWs id.
string—
asteroids[].neo_reference_id
The asteroid's JPL SPK-ID.
string—
asteroids[].name
The asteroid's designation.
string—
asteroids[].nasa_jpl_url
Its page in the JPL small-body database.
string—
asteroids[].absolute_magnitude_h
Its absolute magnitude.
number—
asteroids[].estimated_diameter
Estimated diameter in four units.
object—
asteroids[].is_potentially_hazardous_asteroid
Whether JPL classifies it as potentially hazardous.
boolean—
asteroids[].close_approach_data
Each close approach: date, relative velocity, miss distance and orbiting body.
array—
count
How many asteroids are in this response.
number—
{
  "asteroids": [
    {
      "absolute_magnitude_h": 0,
      "close_approach_data": [],
      "estimated_diameter": {},
      "id": "",
      "is_potentially_hazardous_asteroid": false,
      "name": "",
      "nasa_jpl_url": "",
      "neo_reference_id": ""
    }
  ],
  "count": 0,
  "element_count": 0,
  "near_earth_objects": {}
}

See Asteroid Feed run in a workflow.

In a technical demo we add the NASA connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.