Initiate a group booking request via your GDS (Sabre, Amadeus, or Travelport) group fare API, specifying the route, travel dates, minimum group size (typically 10+ passengers), and a name of record for the group.
Receive a group quote that includes a block of seats at a negotiated rate; note the expiry timestamp of the fare lock and the deposit or full-payment deadline.
Provide passenger names on a rolling basis as travelers confirm — most group bookings allow name submission up to a deadline before departure rather than requiring all names upfront.
Monitor the filled seats count against the block size; release any unused seats before the release deadline to avoid being charged for unfilled seats.
Collect payments in tranches as required by the group fare contract (deposit, final payment); trigger these via your payment gateway and record against the group PNR.
At ticketing deadline, submit the ticketing command via the GDS to issue all tickets in the group PNR simultaneously.
Known gotchas
Group fares require direct GDS PCC (pseudo city code) access or an accredited travel agency relationship; they are not available via standard API consumer accounts.
Name change rules for group bookings are often more flexible than individual fares but still have deadlines; document the name change cutoff from the group contract.
Minimum group size thresholds vary by airline and route — failing to meet the minimum after seat releases may result in the remaining seats reverting to published individual fares.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp