@duffel/api 4.26.0 → 4.27.1

package/dist/typings.d.ts

@@ -460,7 +460,7 @@ declare module '@duffel/api/Stays/StaysTypes' {
     export type StaysLoyaltyProgrammeReference = 'wyndham_rewards' | 'choice_privileges' | 'marriott_bonvoy' | 'best_western_rewards' | 'world_of_hyatt' | 'hilton_honors' | 'ihg_one_rewards' | 'leaders_club' | 'stash_rewards' | 'omni_select_guest' | 'i_prefer' | 'accor_live_limitless' | 'my_6' | 'jumeirah_one' | 'global_hotel_alliance_discovery' | 'duffel_hotel_group_rewards';
     export type StaysPaymentMethod = 'balance' | 'card';
     export type StaysPaymentType = 'guarantee' | 'deposit' | 'pay_now';
-    export type StaysSource = 'bookingcom' | 'priceline' | 'travelport' | 'expedia' | 'sabre' | 'duffel_hotel_group';
+    export type StaysSource = 'bookingcom' | 'priceline' | 'travelport' | 'expedia' | 'sabre' | 'duffel' | 'duffel_hotel_group';
     export interface StaysRate {
             /**
                 * The currency of the base_amount, as an ISO 4217 currency code.
@@ -1769,7 +1769,7 @@ declare module '@duffel/api/booking/BatchOfferRequests/BatchOfferRequests' {
 declare module '@duffel/api/booking/OfferRequests/OfferRequests' {
     import { Client } from '@duffel/api/Client';
     import { Resource } from '@duffel/api/Resource';
-    import { CreateOfferRequest, CreateOfferRequestQueryParameters, DuffelResponse, OfferRequest, PaginationMeta } from '@duffel/api/types';
+    import { CreateOfferRequest, CreateOfferRequestQueryParameters, DuffelResponse, OfferRequest, OfferRequestItinerariesView, PaginationMeta } from '@duffel/api/types';
     /**
         * To search for flights, you'll need to create an `offer request`.
         * An offer request describes the passengers and where and when they want to travel (in the form of a list of `slices`).
@@ -1804,12 +1804,17 @@ declare module '@duffel/api/booking/OfferRequests/OfferRequests' {
                 * To search for flights, you'll need to create an `offer request`.
                 * An offer request describes the passengers and where and when they want to travel (in the form of a list of `slices`).
                 * It may also include additional filters (e.g. a particular cabin to travel in).
-                * @param {Object} [options] - the parameters for making an offer requests (required: slices, passengers; optional: cabin_class, return_offers)
+                * @param {Object} [options] - the parameters for making an offer requests (required: slices, passengers; optional: cabin_class, return_offers, view, include_split_ticket)
                 * When `return_offers` is set to `true`, the offer request resource returned will include all the `offers` returned by the airlines.
                 * If set to false, the offer request resource won't include any `offers`. To retrieve the associated offers later, use the List Offers endpoint, specifying the `offer_request_id`.
+                * When `view` is set to `'itineraries'`, offers are grouped per slice into a hierarchy of itineraries and fare brands.
+                * Combine `view: 'itineraries'` with `include_split_ticket: true` to surface split-ticket candidates.
                 * @link https://duffel.com/docs/api/offer-requests/create-offer-request
+                * @link https://duffel.com/docs/guides/selling-split-ticket-itineraries
                 */
             create: <QueryParams extends CreateOfferRequestQueryParameters>(options: CreateOfferRequest & QueryParams) => Promise<DuffelResponse<QueryParams extends {
+                    view: "itineraries";
+            } ? OfferRequestItinerariesView : QueryParams extends {
                     return_offers: false;
             } ? Omit<OfferRequest, "offers"> : OfferRequest>>;
     }
@@ -2412,7 +2417,7 @@ declare module '@duffel/api/booking/AirlineInitiatedChanges/AirlineInitiatedChan
 
 declare module '@duffel/api/booking/OfferRequests/OfferRequestsTypes' {
     import { Airline, CabinClass, PassengerType, Place, PlaceType } from '@duffel/api/types';
-    import { Offer } from '@duffel/api/booking/Offers/OfferTypes';
+    import { Offer, OfferSliceSegment } from '@duffel/api/booking/Offers/OfferTypes';
     export interface OfferRequestSlice {
             /**
                 * The [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) date on which the passengers want to depart
@@ -2640,6 +2645,16 @@ declare module '@duffel/api/booking/OfferRequests/OfferRequestsTypes' {
                 * whereas return trips will need two.
                 */
             slices: CreateOfferRequestSlice[];
+            /**
+                * When set to `true` and the offer request contains more than one slice,
+                * Duffel will fire additional one-way searches per slice to find
+                * split-ticket itinerary candidates. Split-ticket offers are only returned
+                * when combined with the `view=itineraries` query parameter.
+                *
+                * Requires this capability to be enabled on your Duffel account.
+                * @link https://duffel.com/docs/guides/selling-split-ticket-itineraries
+                */
+            include_split_ticket?: boolean;
     }
     export type TimeRangeFilter = {
             from: string;
@@ -2670,6 +2685,18 @@ declare module '@duffel/api/booking/OfferRequests/OfferRequestsTypes' {
                 */
             departure_time: TimeRangeFilter | null;
     }
+    /**
+        * The shape of the offer request response.
+        *
+        * - `offers` (default) — a flat list of offers under `data.offers`.
+        * - `itineraries` — offers are grouped per slice into a hierarchy of
+        *   itineraries and fare brands under `data.slices[].itineraries[]`. This is
+        *   the view required to surface split-ticket candidates created with
+        *   `include_split_ticket: true`.
+        *
+        * @link https://duffel.com/docs/guides/selling-split-ticket-itineraries
+        */
+    export type OfferRequestView = 'offers' | 'itineraries';
     export interface CreateOfferRequestQueryParameters {
             /**
                 * When set to `true`, the offer request resource returned will include all the offers returned by the airlines.
@@ -2678,6 +2705,14 @@ declare module '@duffel/api/booking/OfferRequests/OfferRequestsTypes' {
                 * You should use this option if you want to take advantage of the pagination, sorting and filtering that the [List Offers](https://duffel.com/docs/api/offers/get-offers) endpoint provides.
                 */
             return_offers?: boolean;
+            /**
+                * Controls the shape of the response. Defaults to `offers`, which returns a
+                * flat list of offers. Set to `itineraries` to receive offers grouped by
+                * slice, itinerary and fare brand — required to retrieve split-ticket
+                * candidates produced by `include_split_ticket: true`.
+                * @link https://duffel.com/docs/guides/selling-split-ticket-itineraries
+                */
+            view?: OfferRequestView;
             /**
                 * The maximum amount of time in milliseconds to wait for each airline search to complete.
                 * This timeout applies to the response time of the call to the airline and includes
@@ -2692,6 +2727,101 @@ declare module '@duffel/api/booking/OfferRequests/OfferRequestsTypes' {
                 */
             supplier_timeout?: number;
     }
+    /**
+        * Discriminator for offers returned under the `itineraries` view.
+        *
+        * - `single_ticket` — a single offer from one airline that covers every slice
+        *   in the original offer request.
+        * - `split_ticket` — an offer that covers a single slice, intended to be
+        *   combined with offers for the remaining slices (potentially from a
+        *   different airline) to fulfil the journey.
+        *
+        * @link https://duffel.com/docs/guides/selling-split-ticket-itineraries
+        */
+    export type ItineraryOfferType = 'single_ticket' | 'split_ticket';
+    /**
+        * An offer returned under the `itineraries` view.
+        *
+        * It is structurally the same as a regular {@link Offer} (minus
+        * `available_services`, which is only populated by the Get single offer
+        * endpoint) but carries a `type` discriminator describing whether the offer
+        * covers the full journey or a single slice that needs to be combined with
+        * other offers.
+        */
+    export interface ItineraryOffer extends Omit<Offer, 'available_services'> {
+            /**
+                * Whether the offer covers every slice from a single airline
+                * (`single_ticket`) or only the slice it is nested under and needs to be
+                * combined with other offers to complete the journey (`split_ticket`).
+                */
+            type: ItineraryOfferType;
+    }
+    /**
+        * A fare brand grouping offers that share the same itinerary segments.
+        */
+    export interface ItineraryBrand {
+            /**
+                * The airline's marketing name for the fare brand, e.g. "Economy Basic".
+                */
+            fare_brand_name: string;
+            /**
+                * The offers available for this fare brand on this itinerary.
+                */
+            offers: ItineraryOffer[];
+    }
+    /**
+        * One way the airline can fly a passenger from the slice's origin to its
+        * destination. A single itinerary is a fixed list of segments which may be
+        * sold under one or more fare brands.
+        */
+    export interface Itinerary {
+            /**
+                * The segments that make up this itinerary, in the order they are flown.
+                */
+            segments: OfferSliceSegment[];
+            /**
+                * The fare brands available for this itinerary, each carrying one or more
+                * bookable offers.
+                */
+            brands: ItineraryBrand[];
+    }
+    /**
+        * A slice as represented in the `itineraries` view of an offer request.
+        *
+        * Unlike {@link OfferRequestSlice}, it does not include the `departure_date`
+        * or origin/destination type fields directly — the per-segment scheduling
+        * lives inside `itineraries[].segments[]`.
+        */
+    export interface OfferRequestItinerariesViewSlice {
+            /**
+                * The city or airport the passengers want to depart from.
+                */
+            origin: Place;
+            /**
+                * The city or airport the passengers want to travel to.
+                */
+            destination: Place;
+            /**
+                * The itineraries available for this slice, each grouping offers by fare
+                * brand.
+                */
+            itineraries: Itinerary[];
+    }
+    /**
+        * The response payload returned when an offer request is created with the
+        * `view=itineraries` query parameter. Offers are grouped per slice rather than
+        * returned as a flat list, which is required to surface split-ticket
+        * candidates produced by `include_split_ticket: true`.
+        *
+        * @link https://duffel.com/docs/guides/selling-split-ticket-itineraries
+        */
+    export interface OfferRequestItinerariesView extends Omit<OfferRequest, 'slices' | 'offers'> {
+            /**
+                * The slices that make up this offer request, each carrying the itineraries
+                * and offers available for that slice.
+                */
+            slices: OfferRequestItinerariesViewSlice[];
+    }
     export {};
 }
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@duffel/api",
-  "version": "4.26.0",
+  "version": "4.27.1",
   "description": "Javascript client library for the Duffel API",
   "main": "dist/index.js",
   "module": "dist/index.es.js",
@@ -59,7 +59,7 @@
     "node-fetch": "2.7.0"
   },
   "devDependencies": {
-    "@babel/core": "7.29.7",
+    "@babel/core": "8.0.0",
     "@babel/preset-env": "7.29.7",
     "@babel/preset-typescript": "7.29.7",
     "@commitlint/cli": "17.8.1",