Integration APIs
Position, history and subscription endpoints let other products use aviation data. API keys and quotas organize access.
Portfolio
FlightRouteAPI — aviation data for applications
FlightRouteAPI combines aviation data APIs with a web dashboard and public demonstrations. Users subscribe to aircraft registrations, access available positions, explore collected tracks and check published schedules. A Go backend works with PostgreSQL and PostGIS, while React and TypeScript provide the web interface.
Challenge
Aviation sources have different availability and freshness. The challenge was to unify positions, history and schedules in a clear API contract with observation timestamps and source limitations.
Solution
We built subscription-driven collection, spatial storage, REST and WebSocket endpoints, and a fleet dashboard. OpenAPI documentation supports integration. The product distinguishes fresh observations from last known positions and does not treat missing data as proof that an aircraft is not flying.
Key features
- Aircraft subscriptions by registration
- Position, altitude, speed, heading and observation timestamps
- Recorded tracks and altitude profiles
- Publicly available schedules with coverage limitations
- REST API, WebSocket and OpenAPI documentation
- Accounts, API keys and subscription limits
- Aviation maps and GNSS quality demonstrations
From observations to integrations
One product for API developers and dashboard users.
Dashboard and maps
Fleet views and aircraft details support data inspection. Public demonstrations expose available responses and integration status.
Freshness and coverage
Availability depends on received observations and schedule sources. History contains collected records; full historical backfill or reception everywhere is not promised.