Business & First Class Deal Validator

Find the catches before you choose your flight.

A premium fare can still come with an economy leg, an awkward connection or unclear pricing. Review the itineraries you already have and see which details need attention before you decide.

This tool checks supplied flight options. It does not search or book flights.

Try the demo · Review your options · Pricing · Help

What you get

A focused itinerary review and a CSV comparison list. See which checks pass, which flag a problem and which need more information. Missing details stay visible, so a partly described itinerary does not become a confident answer.

Demo

Leave Demo selected to explore three fictional itineraries. Run and open REPORT.html from Output. The examples show mixed cabins and missing details; they are not current deals you can book.

The demo has no custom itinerary-review charge. Apify's automatic $0.00005 per start still applies; check the displayed maximum cost.

Start here

1. Select Evaluate and prepare a copy of your itinerary data using the segment CSV template below.
2. Paste it into Start with the segment CSV template. Use one row per flight segment and leave the other input routes empty.
3. Run and open REPORT.html. Download REVIEW.csv for your working list.

Already have a compatible Dataset or JSON export? The supported import option can save that step. Use data you are permitted to analyze; keep passenger names, booking references and payment details out of it.

Segment CSV template

customerId,quoteId,tripType,adults,price,currency,priceBasis,taxes,observedAt,expiresAt,fareConditions,direction,flight,origin,destination,departure,arrival,durationMinutes,cabins,lieFlat,selfTransfer,sourceId,pointOfSale
example,Q1,one_way,1,2000,USD,whole_party,unknown,,,,outbound,XX1,JFK,LHR,,,420,business,,,supplied-export,US

This row is fictional. Repeat itinerary-wide fields consistently across its segments. Use round_trip with both directions for a return trip. Keep unknown values blank; add observation times only when you know when the prices were collected. Upload time is not price freshness.

Pricing

Base price: $0.50 per 1,000 complete-itinerary evaluations ($0.00050 each). Platform usage is included, plus Apify's automatic $0.00005 per start. No Dataset-row surcharge.

Segments and additional checks do not multiply an itinerary's charge. Finding a problem is still a useful evaluation. Rejected imports, duplicates and information-only unknown results are not eligible. Results are saved before the custom charge; your spending limit is respected. Check current pricing before running. Unknown charge outcomes are not automatically retried.

Know what the review means

A passed check reflects the information supplied, not current availability. The Actor does not fill in missing cabin, taxes, lie-flat seating, fare terms, connection protection or observation times. It does not certify minimum connections, visa requirements or passenger protection.

That makes it useful for comparing known details and spotting questions to ask before choosing a fare. It does not replace confirmation with the airline.

Help

Ask about preparing an itinerary or understanding a result in the Issues tab. Include the run ID for a run problem. Use fictional examples in public support, not booking records or access links. A stopped run may already have results or charges; inspect that run before starting another.

Advanced reference

Input parameters

Choose one completed Dataset, supported JSON export, offersCsv or advanced normalized offers. Limits are 100 itineraries and 16 segments each; Dataset/export/CSV input is 4 MiB and complete JSON input is 8 MiB.

The default policy accepts Business/First, permits at most 15% known nonrequested-cabin time, no unknown-cabin time for approval, and two stops per direction. Advanced policy can add lie-flat, connection, elapsed-time and price-target requirements. Currency and price basis must match; no currency conversion is performed.

CSV cabins use business, first, economy, premium_economy or unknown; per-adult values are separated by |. Absolute timestamps need timezone offsets. Missing return legs do not form a complete round trip. Unknown, future or over-15-minute-old observation times cannot establish a fresh candidate. A useful rejection may coexist with other unknown evidence.

Existing Dataset or JSON export compatibility

A completed Dataset or unchanged exported JSON array can use the pinned poidata-google-flights-0.1.70 format. Select that format and supply either Existing compatible Dataset ID (with run-token READ access) or Dataset JSON export, not both. Leave segment CSV and normalized offers empty. Use sourceObservedAt only for a known source observation time.

This adapter supports one adult, no children or infants. Larger parties use normalized CSV with an explicit price basis. A supplied version marker must match; changed required fields are rejected. Local times with unknown UTC offsets do not establish connection timing or freshness. Arbitrary JSON or other scraper versions are not implied to work. Format compatibility is not permission to collect or reuse another source. No upstream acquisition service is included or required.

Output format and repeated reviews

REPORT.html is the readable review and REVIEW.csv the working list. OUTPUT links canonical JSON and reports; the Dataset is a convenience view. Partial coverage is visible. A failed Dataset append does not remove the saved report.

Monitor uses named history storage and state.scopeId, with optional baselineSnapshotId. CHANGES.json/CSV separates source, decision, clock and input changes. History is accepted for 90 days; missing or ambiguous history is disclosed. Select historyStoreId for hosted Monitor; any state.storeId must match. This grants the stated read/write access, not a recurring schedule.

Permissions

Limited Actor permissions are the default. Select only the input/history resources needed and use appropriate storage access/retention settings. Evidence excludes raw upstream error bodies and unselected fields. The charge event remains itinerary-evaluated. See the bundled changelog for implementation history.