Pricing APIs

Frontend integration contract for itinerary pricing flows.

⚠️ Deprecation Note

• PUT /v1/itinerary/:id/pricing-selection (admin) is deprecated/removed from admin flow.
• Admin must use PUT /v1/itinerary/:id/pricing-table for pricing updates.
• Customer pricing selection is now merged into POST /v1/bookings via required pricingSelection payload.

Removed in current release

• PUT /v1/itinerary/:id/customer-pricing-selection has been removed.
• Migration path: send customer selection in POST /v1/bookings under pricingSelection.

Base

• Base path: /v1/itinerary
• Auth: Bearer JWT (except public lead pricing endpoint)

Category enum values

Pricing categories use HotelCategoryEnum numeric values:

• 1 = LUXURY
• 2 = PREMIUM
• 3 = SUPER_DELUXE
• 4 = DELUXE
• 5 = STANDARD

Discount type values (when present in summary):

• 1 = FLAT
• 2 = PERCENTAGE

---

1) GET /v1/itinerary/:id/price-details

Source of truth for pricing table mode, defaults, and summary.

Supported query params

• adults (number)
• children (number)
• extraMattressCount (number; pricing-only, excluded from traveler/slab count)
• selectedCategory (number enum value; applied in customer/b2c flow)
• selectedTransferId (number)
• selectedVehicleName (string)
• selectedCapacityMin (number)
• selectedCapacityMax (number)
• includeDinnerSupplement (true/false)
• channel (b2b or b2c)

GET /price-details recalculates summary from the supplied query params (selection context) in real time.

Compatibility: legacy query params childrenWithoutBed and childrenWithBed are still accepted as aliases for children and extraMattressCount.

Common response envelope

{
  "message": "SUC_PRICE_DETAILS_FETCHED",
  "data": {
    "itineraryId": 958,
    "pricingTableType": "hotel_transfer",
    "mappingSnapshot": {
      "hasActivities": true,
      "hasHotels": true,
      "hasTransfers": true
    },
    "defaultCategory": 5,
    "availableCategories": [5, 2, 1],
    "selection": {
      "selectedCategory": 5,
      "selectedVehicleSlab": {
        "transferId": 3002,
        "vehicleName": "Innova / Xylo / Similar",
        "capacityMin": 1,
        "capacityMax": 3
      },
      "travelerDetails": {
        "adults": 2,
        "children": 1,
        "infants": 0
      },
      "extraMattressCount": 0,
      "includeDinnerSupplement": false,
      "displayMode": 1
    },
    "pricingTable": {},
    "summary": {
      "channel": "b2b",
      "currency": "INR",
      "baseCost": 0,
      "markupPercent": 5,
      "markupAmount": 0,
      "gstPercent": 5,
      "gstAmount": 0,
      "tcsPercent": 0,
      "tcsAmount": 0,
      "discountType": 1,
      "discountValue": 0,
      "discountAmount": 0,
      "grandTotal": 0,
      "tcsApplicable": false
    }
  }
}

---

2) pricingTable by scenario

A) activities_only

{
  "pricingTableType": "activities_only",
  "pricingTable": {
    "activitiesOnly": {
      "adultPrice": 5000,
      "childPrice": 2000
    }
  }
}

B) hotel_only

{
  "pricingTableType": "hotel_only",
  "pricingTable": {
    "categoryPerPersonPrices": [
      {
        "category": 5,
        "perPersonPrice": 15100,
        "primaryMappedHotelName": "Taj City Center"
      },
      {
        "category": 2,
        "perPersonPrice": 18400,
        "primaryMappedHotelName": null
      }
    ],
    "hotelRows": [
      {
        "category": 5,
        "plan": "CP",
        "extraBedPrice": 4050,
        "childWithoutBedPrice": 2100,
        "dinnerSupplementPrice": 1950
      },
      {
        "category": 2,
        "plan": "CP",
        "extraBedPrice": 5500,
        "childWithoutBedPrice": 3800,
        "dinnerSupplementPrice": 2400
      }
    ]
  }
}

C) transfer_only

{
  "pricingTableType": "transfer_only",
  "pricingTable": {
    "transferRows": [
      {
        "transferId": 3001,
        "vehicleName": "Wagon R / Similar",
        "capacityMin": 1,
        "capacityMax": 3,
        "pricePerPerson": 15100
      },
      {
        "transferId": 3002,
        "vehicleName": "Innova / Xylo / Similar",
        "capacityMin": 1,
        "capacityMax": 3,
        "pricePerPerson": 18400
      },
      {
        "transferId": 3002,
        "vehicleName": "Innova / Xylo / Similar",
        "capacityMin": 4,
        "capacityMax": 6,
        "pricePerPerson": 12350
      }
    ]
  }
}

D) hotel_transfer

{
  "pricingTableType": "hotel_transfer",
    "pricingTable": {
      "categoryPerPersonPrices": [
        {
          "category": 5,
          "perPersonPrice": 15100,
          "primaryMappedHotelName": "Taj City Center"
        }
      ],
      "rows": [
        {
        "category": 5,
        "plan": "CP",
        "extraBedPrice": 4050,
        "childWithoutBedPrice": 2100,
        "dinnerSupplementPrice": 1950,
        "vehiclePricing": [
          {
            "transferId": 3001,
            "vehicleName": "Wagon R / Similar",
            "capacityMin": 1,
            "capacityMax": 3,
            "pricePerPerson": 15100
          },
          {
            "transferId": 3002,
            "vehicleName": "Innova / Xylo / Similar",
            "capacityMin": 1,
            "capacityMax": 3,
            "pricePerPerson": 18400
          },
          {
            "transferId": 3002,
            "vehicleName": "Innova / Xylo / Similar",
            "capacityMin": 4,
            "capacityMax": 6,
            "pricePerPerson": 12350
          }
        ]
      }
    ]
  }
}

---

3) Customer pricing selection via booking create

Customer write path:

• Customer: POST /v1/bookings (booking-jwt)
  • requires pricingSelection payload
  • computes and stores pricing snapshot on booking (booking.priceDetails)

Request (pricingSelection block inside booking payload)

{
  "channel": "b2b",
  "selectedCategory": 5,
  "selectedVehicleSlab": {
    "transferId": 3002,
    "vehicleName": "Innova / Xylo / Similar",
    "capacityMin": 1,
    "capacityMax": 3
  },
  "travelerDetails": {
    "adults": 2,
    "children": 1,
    "infants": 0
  },
  "extraMattressCount": 0,
  "includeDinnerSupplement": true,
  "displayMode": 1
}

Response

Booking response includes booking.priceDetails in same structure as GET /price-details with recalculated summary.

Notes:

• selectedCategory is meaningful for hotel-involved flows.
• selectedVehicleSlab is meaningful for transfer-involved flows.
• Backward compatibility: pricingSelection.travelerDetails.childrenWithoutBed and pricingSelection.travelerDetails.childrenWithBed are accepted as legacy aliases.
• vehiclePricing[] and transferRows[] include transferId for transfer reference binding.
• In pricingSelection.travelerDetails, children and infants are optional; pricing computation uses adults + children for traveler/slab count.
• extraMattressCount is pricing-only and must be sent outside travelerDetails.
• In hotel_transfer and hotel_only, pricingTable.categoryPerPersonPrices provides category-wise per-person prices (markup included, dinner supplement excluded) for category card display, plus primaryMappedHotelName for that category.
• If no primary mapped hotel exists for a category, primaryMappedHotelName is null.
• Bundle pricing capacity rows require transferId; vehicle name is resolved from transfer master.
• Capacity bands are stored in bundle pricing rows (not derived from transfer in response):
  • always include 1-3
  • if transfer seater > 3, also include 4-seater
• In activities_only, customer selection does not accept activity prices; prices come from admin pricing-table config.
• Do not send pricingTable.rows (or any rows) in pricingSelection; selection inputs only.

---

4) PUT /v1/itinerary/:id/pricing-table (admin only)

Upsert pricing master rows (rate card) for each scenario.

• Auth: JWT + TRIP permission
• Purpose: update base price table values (not traveler selection)
• Admin pricing table updates are b2b configuration operations.

A) hotel_transfer payload

{
  "scenario": "hotel_transfer",
  "rows": [
    {
      "category": 5,
      "plan": "CP",
      "extraBedPrice": 4050,
      "childWithoutBedPrice": 2100,
      "dinnerSupplementPrice": 1950,
      "vehiclePricing": [
        {
          "transferId": 3001,
          "capacityMin": 1,
          "capacityMax": 3,
          "pricePerPerson": 15100
        }
      ]
    }
  ]
}

B) hotel_only payload

{
  "scenario": "hotel_only",
  "hotelRows": [
    {
      "category": 5,
      "plan": "CP",
      "extraBedPrice": 4050,
      "childWithoutBedPrice": 2100,
      "dinnerSupplementPrice": 1950
    }
  ]
}

C) transfer_only payload

{
  "scenario": "transfer_only",
  "category": 5,
  "transferRows": [
    {
      "transferId": 3001,
      "capacityMin": 1,
      "capacityMax": 3,
      "pricePerPerson": 12000
    }
  ]
}

category is optional for transfer_only; if omitted, backend uses itinerary default category (fallback standard).

D) activities_only payload

{
  "scenario": "activities_only",
  "displayMode": 1,
  "activitiesOnly": {
    "adultPrice": 5000,
    "childPrice": 2000
  }
}

Response (all scenarios)

{
  "message": "SUC_PRICING_TABLE_SAVED",
  "data": {
    "itineraryId": 958,
    "pricingTableType": "hotel_transfer",
    "pricingTable": {},
    "selection": {},
    "summary": {}
  }
}

Notes:

• This endpoint updates the pricing master table.
• POST /bookings pricingSelection updates customer selection inputs and recalculates totals.
• Do not mix both concerns in one request.

---

5) B2B/B2C summary behavior

• channel = "b2b"
  • category is locked to itinerary tripType (admin cannot override category in summary calculation)
  • selectedCategory input is ignored for b2b summary computation
  • summary shows markupAmount, gstAmount, tcsAmount, discountAmount separately.
• channel = "b2c"
  • customer category selection is honored
  • in hotel_transfer, selected category also drives transfer slab selection from that category bundle when available
  • changing selectedCategory can change summary totals based on selected bundle prices
  • base includes markup internally.
  • markup fields are omitted from summary
  • still returns gstAmount, tcsAmount, discountAmount separately.

---

6) Other related pricing endpoints

A) GET /v1/itinerary/price-details/:leadId/:tripId

Public lead pricing endpoint.

B) GET /v1/itinerary/:id/customer-price-details

Customer-token variant of itinerary price-details endpoint.

C) PUT /v1/itinerary/:id/travelers

Legacy compatibility endpoint. New UI should use POST /bookings with pricingSelection.

---

7) Rules for frontend consumers

• tripType is the canonical category source.
• Category swap applies only to hotel pricing.
• Transfer pricing is category-agnostic and uses primary transfer by default.
• Markup is now pulled from tenant markup inventory per itinerary:
  • Priority: specific-trip markup > all-trips markup > no markup
  • Supports both percentage and flat types
• Capacity slab auto-selection uses adults + children count (infants and extraMattressCount excluded from slab banding).
  • <= 3 selects 1-3 slab
  • > 3 selects 4-6 slab (or matching higher slab)
• Default display order:
  • hotel + transfer: selected/default category hotel bundle + primary transfer pricing.
  • transfer-only: primary transfer pricing.
  • activities-only: adultPrice default.

---

8) Publish validation matrix

• hotel + transfer (+activities):
  • category required
  • hotel pricing for selected/default category required
  • primary transfer required
  • transfer pricing required
• hotel-only:
  • category required
  • hotel pricing for selected/default category required
• transfer-only:
  • primary transfer required
  • transfer pricing required
• activities-only:
  • adultPrice is mandatory