Skip to main content
An Enhanced Radar API request can succeed and still return nothing, a null, or a result that changes later. This page explains what each of those means, so a display built on the API tells your users the right thing.

Coverage

Empty and null results

Results that change

When a request succeeds but returns nothing

1

Check coverage

Find the facility in GET /api/v0/facilities and confirm that the channels you expect have is_available set to true.
2

Check the window

since and until are compared with received_at (transcripts) or happened_at (events and PIREPs), in UTC. Make sure the window covers when the traffic happened, and remember that the maximum window is 48 hours for transcripts and events and 6 hours for PIREPs. See Selecting data.
3

Remove filters

Run the request with only since, until, and facility_id. If transcripts come back, a callsign, airline_id, or atc_channel_ids filter excluded them. Callsigns are ICAO, e.g. UAL406, not UA406.
4

Broaden the search

For GET /api/v0/events and GET /api/v0/pireps, describe what you want in different words. Results are ranked by meaning, and weak matches are left out. For PIREPs, also try a larger radius_nm.
5

Contact support

If an available channel returns nothing for a window when you expect traffic, email support@enhancedradar.com with the request and its X-Request-ID response header.