Linked Devices
Go to /display to get a pairing code to enter on this page. Paired devices show real-time data for aircraft in your monitoring area.
| Name | Type | Prefix | Created | Last used | Status |
|---|
Or generate a key manually (useful for microcontrollers):
Data Feed Source
Your PiAware / dump1090 instance. The feeder polls <URL>/data/aircraft.json once per second. Changes take effect within a few seconds.
Use another account's data by pasting an invitation key they sent you. Your account becomes read-only: you won't run your own feed, configure a monitoring area, or set an AeroAPI key — but you can still add devices that display the shared data.
AeroAPI Keys
Optional. Your personal FlightAware AeroAPI key. When set, route/aircraft lookups for your feeds use this key (billed to your FlightAware account). Stored securely and only ever shown masked.
This month's AeroAPI usage
| Endpoint | Calls | Cost / query | Total cost |
|---|
Spending limit
Cap this key's monthly cost. When enabled, the key stops being used for enrichment once your actual month-to-date spend reaches the limit, and your feeds fall back to the free sources until the 1st (UTC).
FlightAware account usage
Billed usage reported directly by FlightAware for your account (AeroAPI /account/usage).
Invitations
Invite read-only users to view your data. Generate a link and send it however you like — opening it and signing in with Google links that account to yours as read-only. Read-only users see your aircraft + monitoring area but can't change anything or trigger enrichment.
Pending invitations
| Name | Created | Link |
|---|
Read-only users
| Name |
|---|
Feeds
Feeds you own. Use the device URLs below with any of your API keys.
| ID | Name | Region | Device URLs |
|---|