FAQ
Common questions about the Ignav API.
Who is Ignav best for?
Developers building flight search apps, price trackers and fare alerts, AI travel tools, or travel content sites. See the Solutions section for implementation guides.
What data does Ignav provide?
Live one-way and round-trip flight fares with pricing, carrier details, flight segments, durations, and baggage info. You can also fetch direct booking links for any itinerary.
How many routes and airports are covered?
Ignav covers thousands of airports worldwide across domestic and international routes. Coverage spans major carriers and low-cost airlines in over 80 markets.
How fresh is the fare data?
Fare data changes continuously. Prices and availability can change between requests.
What is an ignav_id?
A unique identifier attached to each itinerary in a fare search response. Pass it to the booking links endpoint to get direct booking URLs.
How does pricing work?
$2 per 1,000 successful requests. Your first 1,000 requests are free. Failed requests (4xx/5xx) are never billed. See the pricing page for details.
What counts as a billable request?
A billable request is a successful (HTTP 200) one-way search, round-trip search, booking link lookup, or airport search. Validation errors, auth failures, and upstream errors don't count.
Are there per-account rate limits?
No. API key requests do not have a per-account rate limit. Usage is priced per successful request.
Can I filter by airline, stops, or cabin class?
Yes. Use airlines_include or airlines_exclude for carrier filters, max_stops for connections, and cabin_class for economy through first class. See the full parameter list.
Do you offer SDKs or client libraries?
The API is a standard REST API with JSON request/response bodies, so any HTTP client works. Code examples in the docs are available in cURL, Python, and JavaScript. Fare and booking examples can be opened directly in the playground.
Do you publish an OpenAPI spec?
Yes, it's available at /api/openapi.json.
Do I need booking links for every result?
No. Booking links are optional. You can display fare data on its own and only fetch booking links when a user is ready to book. This is common for price trackers and content embeds.
Can I use Ignav for commercial applications?
Absolutely. Ignav is built for production use. For high-volume applications, contact us.
How should I handle changing fares?
Fares change continuously. Treat displayed prices as approximate, use phrasing like "from $299," and always link to a booking page where the user sees the live price at checkout. Don't cache results for more than a few hours.
What happens if a request fails?
The API returns a structured error response with a machine-readable code and human-readable message. Upstream errors (status 424) are safe to retry. We don't charge for unsuccessful requests.
What should I do in production?
Retry network failures and HTTP 424 responses with backoff. Short cache windows are fine, but treat fares and availability as continuously changing data.
Empty itinerary arrays are valid successful responses, not errors. Also note that outbound.carrier and inbound.carrier are airline display names; use marketing_carrier_code when you need a code.
Related docs
Ready to get started?
Create a free account to get your API key, or try the playground — no signup required.