API Terms of Use

Last updated: 1 July 2026

These API Terms of Use ("API Terms") govern access to the AirportFusion public API (the "API"). They apply in addition to our general Terms of Service. By creating an API key or calling the API you accept these API Terms.

1. API keys

• Access requires an API key issued through your developer dashboard. Keys are shown once at creation; we store only a cryptographic hash.
• Keys are personal to your account (or your organisation). Keep them secret; do not embed them in public client-side code or public repositories.
• You are responsible for all requests made with your keys. If a key leaks, revoke and regenerate it immediately from the dashboard.

2. Plans, quotas and rate limits

• Each key is attached to a plan (Free, Starter, Pro, Business or Enterprise) with a monthly request quota and a per-minute rate limit, both shown on the Pricing page and in your dashboard.
• Requests beyond the rate limit receive HTTP 429 with Retry-After and X-RateLimit-* headers; requests beyond the monthly quota receive HTTP 429 with the quota_exceeded error code until the next calendar month or a plan upgrade.
• We may throttle or temporarily suspend traffic that endangers platform stability, with notice where practicable.

3. Fair use

You agree not to:

• circumvent quotas or rate limits (e.g. by rotating keys or accounts);
• use the API to systematically reconstruct, replicate or resell our underlying dataset or a substantially similar flight-search database;
• cache responses longer than 24 hours, except aggregate statistics;
• misrepresent API output as real-time airline availability or fare quotes — all values are estimates;
• use the API in safety-critical systems or anywhere inaccurate estimates could cause harm.

4. Attribution

Public-facing products using the Free, Starter or Pro plans must display a reasonably visible attribution such as "Flight search powered by AirportFusion" with a link to our website. Business and Enterprise plans may agree different attribution terms in writing.

5. Billing

Paid plans are billed monthly in advance via Stripe. Quota resets on the first day of each calendar month (UTC). Plan upgrades take effect immediately; downgrades take effect at the next billing period. Fees are non-refundable except where required by law.

6. Data and privacy

• API request metadata (endpoint, status, latency, hashed IP) is logged for quota enforcement, billing and abuse prevention — see our Privacy Policy.
• If your application sends us personal data of your own users (e.g. addresses typed by them), you are the controller of that data and must have a lawful basis for sharing it with us; we act as your processor for search execution.

7. Availability and changes

The API is provided without an uptime guarantee unless an SLA is agreed in an Enterprise contract. We may evolve the API; breaking changes to a versioned endpoint (/api/v1/…) will be announced at least 30 days in advance via the developer dashboard or email, except for urgent security fixes.

8. Termination

You may stop using the API and cancel your plan at any time. We may suspend or revoke keys that violate these API Terms, remain unpaid, or create security or legal risk. Where reasonable, we will warn you before suspension.

9. Disclaimer and liability

Section 8 and 9 of the general Terms of Service (warranties, limitation of liability) apply equally to the API. Route data, prices and durations are heuristic estimates derived from public datasets and statistical models.

10. Contact

API questions: use the developer support channel or the support email published on this site.