Pricing APIs

Frontend integration contract for itinerary pricing flows.

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

• selectedCategory (number enum value)
• selectedVehicleName (string)
• selectedCapacityMin (number)
• selectedCapacityMax (number)
• includeDinnerSupplement (true/false)
• channel (b2b or b2c)

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": {
        "vehicleName": "Innova / Xylo / Similar",
        "capacityMin": 1,
        "capacityMax": 3
      },
      "travelerDetails": {
        "adults": 2,
        "children": 1,
        "infants": 0,
        "childrenWithBed": 0,
        "childrenWithoutBed": 1
      },
      "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": {
    "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": [
      {
        "vehicleName": "Wagon R / Similar",
        "capacityMin": 1,
        "capacityMax": 3,
        "pricePerPerson": 15100
      },
      {
        "vehicleName": "Innova / Xylo / Similar",
        "capacityMin": 1,
        "capacityMax": 3,
        "pricePerPerson": 18400
      },
      {
        "vehicleName": "Innova / Xylo / Similar",
        "capacityMin": 4,
        "capacityMax": 6,
        "pricePerPerson": 12350
      }
    ]
  }
}

D) hotel_transfer

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

---

3) PUT pricing-selection endpoints

Two write endpoints exist with different auth and persistence targets:

• Admin: PUT /v1/itinerary/:id/pricing-selection (JWT + TRIP permission)
  • saves pricing selection on itinerary (itinerary.travelerDetails)
• Customer: PUT /v1/itinerary/:id/customer-pricing-selection (booking-jwt)
  • saves computed pricing snapshot on booking (booking.priceDetails)

Request

{
  "channel": "b2b",
  "selectedCategory": 5,
  "selectedVehicleSlab": {
    "vehicleName": "Innova / Xylo / Similar",
    "capacityMin": 1,
    "capacityMax": 3
  },
  "travelerDetails": {
    "adults": 2,
    "children": 1,
    "infants": 0,
    "childrenWithBed": 0,
    "childrenWithoutBed": 1
  },
  "includeDinnerSupplement": true,
  "displayMode": 1,
  "activitiesOnly": {
    "adultPrice": 5000,
    "childPrice": 2000
  }
}

Response

Returns same pricing structure as GET /price-details with recalculated summary.

Customer endpoint also returns bookingId in data.

Notes:

• selectedCategory is meaningful for hotel-involved flows.
• selectedVehicleSlab is meaningful for transfer-involved flows.
• In activities_only, activitiesOnly.adultPrice is mandatory for publish readiness.
• Do not send pricingTable.rows (or any rows) in PUT payload; save endpoints accept selection inputs only.

---

4) B2B/B2C summary behavior

• channel = "b2b"
  • summary shows markupAmount, gstAmount, tcsAmount, discountAmount separately.
• channel = "b2c"
  • base includes markup internally.
  • still returns gstAmount, tcsAmount, discountAmount separately.

---

5) 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/customer-pricing-selection

Customer write endpoint for pricing selection (booking persistence).

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

Legacy compatibility endpoint. New UI should use PUT /pricing-selection.

---

6) 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 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.

---

7) 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