Browse Asteroids

nasa.neo_browse
ActionBusiness appsconnection required

Calls the NASA API with the connection's credentials.

Page through the whole NeoWs near-Earth asteroid data set.

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, none required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
page
Which page of the data set to read; the first page is 0.
numberNo—≥ 0—
size
How many asteroids to return per page; NASA's own default is 20.
numberNo—≥ 1—

Output

One shape.

result

FieldTypeExample
page
NASA's paging block: size, number and totals.
object—
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,
  "page": {}
}

See Browse Asteroids 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.