What kinds of products can be built with the Ignav flight API?

Ignav is a self-serve API for flight prices and booking links, and it is designed around three product types: flight search apps, price trackers and alerts, and AI travel tools. If what you are building falls into one of those three shapes — you need live fares, structured itinerary data, and a link that takes the user to the airline or an OTA — Ignav is a fit. If you need something outside that scope, the same three categories are also the honest limit of what the site describes.

Flight search apps

This is the most direct use case. You send a route and date, get back structured JSON itineraries, and then fetch a booking link for the one the user picks.

The flow is two calls:

1. Search fares — start with one-way or round-trip. Flexible search also supports one or two ordered legs and open-jaw trips.
2. Fetch booking links — pass an ignav_id to request direct airline and OTA booking URLs.

A one-way search looks like this:

curl -X POST "https://ignav.com/api/fares/one-way" \
  -H "X-Api-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"origin":"SFO","destination":"JFK","departure_date":"2026-11-03"}'

The response is structured JSON. Each itinerary carries a price object with amount, currency, and a status field (the example shows "verified"), plus an outbound object with carrier, duration, and a segments array. Each segment includes marketing carrier code, flight number, operating carrier name, departure and arrival airports, local and UTC times with timezones, duration, and aircraft. The itinerary also carries cabin_class, requires_self_transfer, and the ignav_id you use for the booking link.

That field set is what makes the data usable for filtering: you can sort by price, filter by cabin class, flag self-transfer itineraries, and display times in the user's timezone without doing your own conversion.

Choose this if you are building a search-and-book interface and want to hand users off to the airline rather than handle payment yourself. The API returns booking URLs, not tickets.

Price trackers and alerts

The documented pattern here is to poll routes on a schedule, compare fares over time, and notify users when prices drop. Ignav publishes a guide specifically for this at /docs/solutions/price-tracking-alerts.

The mechanics follow from the API shape: because every search returns a price object with an amount and currency, you can store each result against a route and date, then diff new polls against your stored history. The ignav_id lets you keep a stable reference to a specific itinerary across polls.

Two practical notes from the product description:

• No rate limit. The site states there is no rate limit, which matters if you are polling many routes on a schedule.
• Only successful requests are billed. Failed requests do not count against you, which reduces the cost of polling routes that occasionally return nothing.

Choose this if your product's value is in the change over time rather than a single search. You will need your own storage layer for price history — the API returns current fares, not historical series.

AI travel tools

Ignav explicitly targets AI workflows: look up airports, search live fares, and generate booking links from an AI workflow. The site states it works with any AI agent and points to an MCP server for that purpose.

The "from question to booking link" framing on the site describes the intended pattern: every answer is a couple of calls — live fares first, then a link straight to the airline. That maps cleanly onto a tool-calling agent, where fare search and booking-link retrieval become two callable functions.

Choose this if you are building an agent or assistant that needs to answer "what does it cost to fly X to Y" and then act on the answer. The MCP server is the documented integration path.

Comparing the three

Getting started and what it costs to try

The signup path is three steps: get an API key, search fares, fetch booking links.

• 1,000 free requests, no credit card required.
• Only successful requests are billed.
• No rate limit.
• An interactive Playground is available, with cURL, Python, and JavaScript examples.

Pricing beyond the free tier is listed at /pricing; the page evidence here does not include the specific numbers, so check that page directly before committing to volume.

When Ignav is not the right fit

The three categories above are the scope the site describes. If your product needs to issue tickets, handle payments, or serve historical fare data as a queryable dataset, none of those are part of the documented API — you would be building that layer yourself on top of the fare and booking-link calls.