How adsblol/api works
This is the adsb.lol HTTP API, a Rapid API-compatible service for aircraft data and related receiver/network information. Clients call the FastAPI application; aircraft-filter requests are translated to ReAPI queries, while route and airport requests use VRS data and route plausibility checks. Other documented or sampled capabilities include network metrics, receiver-based map redirects, and map screenshots. Background providers gather ingest and MLAT data into Redis for API reads. The excerpts are partial, so links for unsampled route wiring and provider integrations are limited to directly supported behavior.
Main entry points: app.py API Application · api_routes.py V0 Routes · provider.py Network Provider · api_tar.py Screenshot API
Components 17
HTTP API
- API Application
src/adsb_api/app.py
Aircraft Data
- V0 Routes
src/adsb_api/utils/api_routes.py - V2 Filters
src/adsb_api/utils/api_v2.py - Route Plausibility
src/adsb_api/utils/plausible.py - VRS Data Access
src/adsb_api/utils/provider.py - ReAPI Client
src/adsb_api/utils/reapi.py
Receiver Network
- Network Provider
src/adsb_api/utils/provider.py - Feeder Data
src/adsb_api/utils/provider.py
Map Rendering
- Screenshot API
src/adsb_api/utils/api_tar.py - Browser Pool
src/adsb_api/utils/browser2.py
Other components
- API Client
- ReAPI Service
- Redis
- Ingest Services
- MLAT Servers
- Chromium
- Planespotters API
Connections 22
- API Client → API Application: sends requests
- API Application → V0 Routes: dispatches v0
- API Application → V2 Filters: dispatches v2
- V0 Routes → VRS Data Access: reads route data
- V0 Routes → Route Plausibility: checks plausibility
- V0 Routes → VRS Data Access: caches routes
- V2 Filters → ReAPI Client: queries aircraft
- ReAPI Client → ReAPI Service: fetches data
- API Application → Network Provider: reads network data
- Network Provider → Ingest Services: fetches receiver stats
- Network Provider → MLAT Servers: fetches sync data
- Network Provider → Redis: writes network snapshots
- API Application → Feeder Data: reads receiver data
- Feeder Data → Redis: reads and writes
- VRS Data Access → Redis: reads and writes
- API Application → Screenshot API: dispatches screenshot
- Screenshot API → ReAPI Service: looks up aircraft
- Screenshot API → Redis: reads and caches images
- Screenshot API → Browser Pool: renders map
- Browser Pool → Chromium: controls browser
- API Application → Planespotters API: requests aircraft photos
- API Application → Redis: caches photo responses