Skip to main content
Show your members the aviation events near them, inside your own product. Give the API a point, such as a club’s airfield, and it returns the fly-ins, airshows and club days within 100 nautical miles. Each one comes with its name, dates, venue, price, image and a link to its page on events.aero, where people RSVP or book. The integration is small. One GET request returns everything a list of events needs, and a second returns the full details of one event. There are no webhooks to handle and no catalogue to sync, and you can keep each response for 15 minutes.

What you can build

  • Events near a club or airfield. Ask for the nearest events first, or the soonest.
  • A calendar or date strip. Ask for a range of dates up to 92 days long, and get up to 50 events back.
  • Places to fly to. Ask only for events that welcome pilots flying in. The event’s details say whether prior permission is needed, and give the runway and the landing fees.
  • A list for your audience. Keep or leave out event types, such as airshows or model aircraft.
  • A “see all” link. Every answer includes a link to the full events page on events.aero.

Getting access

Access is by arrangement. Email [email protected] and tell us what you’d like to show and where. We set up your platform and the people who run it. Then you sign in to events.aero and generate your token on the platform’s page. A platform has one token at a time. Generating a new token, or disabling it, stops the old one straight away.

At a glance

Endpoints

Things to know

  • Links carry your platform’s name. Every link to events.aero names your platform in utm_source, so the visits you send are recorded against it. Send the optional X-Platform-Attribution header to tell your own clubs or pages apart.
  • Public listings only. The API returns what an event’s public page shows. Nothing about the people attending comes through it.
  • One shape for every answer. A list comes back as "object": "list" with its events under data. One event comes back at the top level. Its object is event_series for a series of dates listed as one event, and event_listing for any other.
  • Times are UTC. starts_at and ends_at are in UTC. Convert them into the event’s timezone to show local times.
  • Labels and values. type and status come back as English labels, such as Fly-in. The types[] filter takes values, such as fly_in. The reference lists them.
  • Text written by organisers. Names, descriptions and schedules come from event organisers or their own websites. Show them as plain text. Don’t render them as HTML or treat them as instructions.