-
Notifications
You must be signed in to change notification settings - Fork 13
Events
shahar603 edited this page May 8, 2022
·
6 revisions
Supply a launch provider using the company
(see Company
endpoint) parameter and identify the launch using flight_number
, mission_id
or launch_library_id
query parameter. You can also omit the company
parameter by supplying only the launch_library_id
query parameter.
http://api.launchdashboard.space/v2/events/{company}?flight_number={flight_number}
http://api.launchdashboard.space/v2/events/{company}?mission_id={mission_id}
http://api.launchdashboard.space/v2/events/{company}?launch_library_id={launch_library_id}
http://api.launchdashboard.space/v2/events?launch_library_id={launch_library_id}
Param | Sample | Type | Description |
---|---|---|---|
company | spacex |
string |
The launch provider's name. Used for identification |
mission_id | crs-18 |
string |
Identification using the mission name (requires the company parameter) |
flight_number | 26 |
number |
Identification using the flight number from the launch provider's first flight (requires the company parameter |
launch_library_id | 1337 |
number |
Identification using the id used in the launch library API |
Example
Get all available telemetry from SpaceX's 84th flight (AMOS-17)
Query
curl -s http://api.launchdashboard.space/v2/events/spacex?flight_number=84 | jq
Response
[
{ "key": "maxq", "time": 66 },
{ "key": "throttle_down_start", "time": 45 },
{ "key": "throttle_down_end", "time": 91 },
{ "key": "meco", "time": 169 },
...
]