Book a demo

Asteroid Lookup

nasa.neo_lookup
ActionBusiness appsconnection required

Calls the NASA API with the connection's credentials.

Read one asteroid's full NeoWs record by its JPL SPK-ID.

Ask about NASAAll NASA nodesProvider API docs ↗

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

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

FieldTypeRequiredDefaultConstraintsExample
asteroid_id
The asteroid's NASA JPL small-body SPK-ID, as returned by the asteroid feed or browse.
stringYes——3542519

Example configuration

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

{
  "asteroid_id": "3542519"
}

Output

One shape.

result

FieldTypeExample
id
The asteroid's NeoWs id.
string—
neo_reference_id
The asteroid's JPL SPK-ID.
string—
name
The asteroid's designation.
string—
nasa_jpl_url
Its page in the JPL small-body database.
string—
absolute_magnitude_h
Its absolute magnitude.
number—
estimated_diameter
Estimated diameter in four units.
object—
is_potentially_hazardous_asteroid
Whether JPL classifies it as potentially hazardous.
boolean—
close_approach_data
Every recorded and predicted approach.
array—
orbital_data
Its orbit as JPL last determined it.
object—
{
  "absolute_magnitude_h": 0,
  "close_approach_data": [],
  "estimated_diameter": {},
  "id": "",
  "is_potentially_hazardous_asteroid": false,
  "name": "",
  "nasa_jpl_url": "",
  "neo_reference_id": "",
  "orbital_data": {}
}

Related NASA nodes

See Asteroid Lookup 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.

Book a technical demoTalk to sales