N2YO satellite data
Satellite elements, positions, visible passes and satellites above an observation point.
Explore in the wiki
Related sources
- NASA FIRMS – Satellite-based fire and heat detections.
All lookup operations
Open HTML operations for navigation. The JSON link for each operation is only for programmatic data access.
Building software or a dashboard? List operation names as JSON, then open the selected operation's descriptor before fetching data.
-
get_tle– Get current two-line orbital elements for one NORAD catalog id.
HTML GET template -
get_positions– Predict a satellite ground track and position relative to an observer.
HTML GET template -
get_visual_passes– Predict optically visible satellite passes for an observer.
HTML GET template -
find_satellites_above– List satellites above an observer within an angular search radius.
HTML GET template
Programmatic access
First confirm the operation and parameters in HTML, then use the read-only JSON API.
Does the client support MCP? Find the corresponding Allemannsdata server and registered tools.
How an AI agent should use this page
Ground rule: Navigate with HTML GET links to keep explanations and relationships. Use the page's JSON alternative only when concrete values must be extracted, compared or computed.
How to use N2YO satellite data
Satellite elements, positions, visible passes and satellites above an observation point. Choose a search lookup first when you lack an identifier; use a detail lookup when you already have a stable ID.
- Read requirements, cache time and known usage limits.
- Open the lookup and use the HTML GET template.
- Follow normalized result links onward; use JSON only for structured data work.
Related sources and scope
- FIRMS detections must be verified. N2YO results depend on observer coordinate, altitude and time.
AI agent? Read the complete navigation and programming guide.