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 optionalX-Platform-Attributionheader 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 underdata. One event comes back at the top level. Itsobjectisevent_seriesfor a series of dates listed as one event, andevent_listingfor any other. - Times are UTC.
starts_atandends_atare in UTC. Convert them into the event’stimezoneto show local times. - Labels and values.
typeandstatuscome back as English labels, such asFly-in. Thetypes[]filter takes values, such asfly_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.

