This isn’t legal advice. Confirm fare and availability accuracy with your legal or compliance team before publishing a flight catalog.
File format
- CSV, TSV, RSS XML, or ATOM XML, one row per flight (or per origin-destination-date combination), with a header row naming each column.
- All column headers must be in US English.
- Unlike the other five catalog types, flights don’t have a dedicated ID column. Meta generates the ID automatically from the origin and destination airport codes.
Column template
This is a representative subset, not the complete spec: Meta’s flight feed also covers fields for number of stops, travel class, and one-way versus round-trip, plus a feedless option that skips the file entirely and pulls flight data from your site directly. Verify the full column list and both setup paths (feed-based and feedless) against Meta’s documentation linked above.
Format rules
pricefollows the pattern used across every Meta catalog type: a number plus a three-letter ISO 4217 currency code.- Dates are typically expected in
YYYY-MM-DD; confirm against the current template before a first upload, since Meta’s exact date format expectations weren’t independently verifiable for this page.
Data and compliance rules
Official documentation
- Set up a Flight Catalog
- Set up a Flight Catalog Using a Feedless Solution
- Advertising Standards, Transparency Center