Avinor Flydata

What you can build

• Hold the hotel shuttle for a late arrival

  Poll arrivals for your airport with direction A. When a flight tied to an expected guest carries status E with a later time, the operator proposes moving the shuttle run and shows the flight record it read.

  With Shuttle Timing, Arrival Prep

• Warn on inbound freight delays

  Match the flightId values on your inbound air freight to the departure feed. A status of C or E on the matched flight becomes a proposed delay notice to the receiving site.

  With Inbound Delay

• Rebalance a landside crew for a bank of arrivals

  Read the seven-hour arrivals window each cycle. When arrivals bunch beyond the plan, the operator proposes shifting break times or offering an open shift for your approval.

  With Intraday Balance, Event Surge

Requirements

• IATA codes for the Avinor airports you watch, taken from airportNames/v1.0
• A poll interval of three minutes or longer for flights; reference lists no more than once every 24 hours
• The attribution text placed close to the data and visible to the end user
• Prior contact with Avinor before any use that places a large load on the service

Authentication

No key. Requests to asrv.avinor.no are open; URLs and parameters are case-sensitive, and every display must carry the 'Flight data from Avinor' label linked to www.avinor.no.

Limits

• One airport per XmlFeed request; the feed covers Avinor's own airports and not private ones such as Sandefjord Torp
• No push or webhook; changes are found by polling with the lastUpdate parameter
• Avinor provides no technical support and may end access for uses it deems harmful to its reputation
• The default window is one hour back and seven hours ahead; wider windows must be asked for on each call

Questions and answers

Do I need an API key for Avinor Flydata?

No. The XML services on asrv.avinor.no are open. Avinor does require that any content from the services carries the label 'Flight data from Avinor' as a link to www.avinor.no, placed close to the data and clearly visible to the end user.

How often can I poll the feed?

Avinor recommends retrieving flight times every three minutes. The status code, airport name, and airline name lists change rarely, and Avinor says fetching them more often than every 24 hours is unnecessary. Use the lastUpdate parameter to fetch only records changed since your last call.

How does a delay or cancellation show up?

Each flight carries a status element with a code and a UTC time. E means a new time, N new information, C cancelled, A landed, and D departed. Gate, belt_number, and check_in fill in as the airport assigns them.