Aircraft · ADS-B
Current aircraft positions and approved history. ADS-B stands for Automatic Dependent Surveillance–Broadcast.
Aircraft endpoints →Layer400 developers · Cloud API v1
Build with received aircraft
and drone data.
Your server asks Layer400 for an area. The Cloud API returns the positions our network received, as JSON your software can use.
How the Cloud API works.
- Receivers listen. Participating receivers hear aircraft ADS-B and drone Remote ID broadcasts.
- Layer400 prepares the data. The network creates timestamped position records with public track references.
- Your server requests an area. It sends an HTTPS GET request with an approved API key.
- You use the JSON response. Feed your dashboard or analyse received activity under your agreed access terms.
Live means polling for current positions. Historical queries return retained position observations. Coverage follows reception; it is not a complete inventory of everything in the sky.
Choose the data you need.
Drones · Remote ID
Current drone positions and approved history from supported Remote ID broadcasts.
Drone endpoints →Each live or history layer has its own permission. See every returned field, unit and example response.
Approval comes before access.
Use your normal Layer400 account to describe your company, use case and requested layers. The request is emailed to the administrator. Submitting a request never activates access. After explicit approval you can create a key and see your limits, usage and expiry.
Future Raspberry Pi API.
A Pi software API is planned. Its endpoints, authentication and release date have not been published. This developer centre will house that reference when it is available. Cloud API keys do not grant access to a receiver.
Discuss a receiver integration →Documentation reviewed 2 October 2026. Coverage and access conditions.