Priced by watched flights

Pay for flights, not requests.

A watched flight is one subscription to one flight on one date, however many webhooks it sends. Lookups are included, and every plan has the whole API.

Free$0/mo

Three real flights a month, every event, commercial use allowed.

  • 3 watched flights / month
  • 120 lookups / month
  • Commercial use allowed
  • Stops at the limit
Get a free key
Hobby

A side project that ships.

$9/mo
  • 100 watched flights / month
  • 4,000 lookups / month
  • 60 requests / minute
  • Extra flights at $0.08 each
Starter

A small fleet or an early product.

$19/mo
  • 500 watched flights / month
  • 20,000 lookups / month
  • 120 requests / minute
  • Extra flights at $0.05 each
Growth

A product with flights at its core.

$49/mo
  • 2,000 watched flights / month
  • 80,000 lookups / month
  • 300 requests / minute
  • Extra flights at $0.03 each
Scale

Several products, or a busy season.

$99/mo
  • 5,000 watched flights / month
  • 200,000 lookups / month
  • 600 requests / minute
  • Extra flights at $0.02 each
Need more?

Custom quotas, an SLA, invoicing, and a direct line to the engineers.

  • Tens of thousands of flights a month
  • Quotas shaped to your traffic
  • Uptime commitment in writing
Talk to us
All 23 change types, on every plan
Signed webhooks with retries, on every plan
Delivery log and test events, on every plan
Leg selection and timeline, on every plan

All prices in USD, before tax. Plans are billed monthly; a request over the per-minute limit answers 429.

Why not poll it yourself?

On a request-priced API, watching a flight means a poller you write, run and keep alive, and somewhere between 70 and 500 requests per flight depending on how nervous you are. The diffing, the signatures, the retries at three in the morning and the log that tells you what was delivered are all yours to build.

Here that is one watched flight. We poll on an adaptive schedule, diff every answer, deliver only the changes, retry when your endpoint is down, and keep the log.

Poll every 5 minutes for the last 6 hours
72 requests
Poll every 3 minutes for a full day
480 requests
Plus a poller, a differ, a retry queue and a delivery log
your engineering time
One watched flight on FlightByte
1 line item

Request counts assume one status call per poll. Our own schedule spends roughly 40 to 120 upstream polls per flight, and that cost is inside the price.

The fine print, in plain words

How billing works

What counts as a watched flight?
One subscription to one flight on one date, counted when it is created. FlightByte polls it on its own schedule until the flight arrives; however many webhooks that produces, it is still one watched flight. Lookups are counted separately and are cheap because they are cached.
What happens when I reach a limit?
Lookups over the per-minute or monthly quota answer 429 with a Retry-After header. Extra watched flights are billed at your plan's overage rate, so a busy month never stops halfway, and nothing already being watched is ever dropped. Free is the exception: the fourth subscription in a month answers 402, and the three you have keep running.
How do I pay?
Free needs no payment at all. Paid plans are billed monthly in USD, and self-serve billing is not live yet: request a key with the plan you want and we set up payment by email before the key is issued. Enterprise plans are invoiced.
Can I change plans?
Yes, at any time; the new quotas apply immediately and the difference is prorated on the next invoice. Downgrades take effect at the end of the billing month.
Get started

Start free, grow from there.

3 watched flights a month on the house, every event, no card. Move up when the numbers do.

A free key in a minute, no card. On a paid plan? Request a key