REST Resource: accounts.priceViews

AI-generated Key Takeaways

A Price View covers the Prices functionality found in pre-v3.0 API versions.
The PriceView resource includes a name and an array of per-itinerary prices.
HotelPricePerItinerary details the price for a specific itinerary, including check-in date, length of stay, price, taxes, fees, currency code, and update time.
The get method is available to return the requested price view in full detail.

A price view. Covers the Prices functionality in pre-v3.0 API versions.

JSON representation
{ "name" : string , "perItineraryPrices" : [ { object ( `HotelPricePerItinerary` ) } ] }

Fields

Fields
`name`	`string` Resource name in the format `accounts/{account_id}/priceViews/{partnerHotelId}` .
`perItineraryPrices[]`	`object ( HotelPricePerItinerary )` Price for each itinerary.

name

string

Resource name in the format accounts/{account_id}/priceViews/{partnerHotelId} .

perItineraryPrices[]

Price for each itinerary.

Hotel price for a given itinerary.

JSON representation
{ "checkinDate" : { object ( `Date` ) } , "lengthOfStayDays" : integer , "price" : number , "taxes" : number , "fees" : number , "currencyCode" : string , "updateTime" : string }

Fields
`checkinDate`	`object ( Date )` Check-in date.
`lengthOfStayDays`	`integer` Number of nights for the itinerary.
`price`	`number` Hotel price for this itinerary.
`taxes`	`number` Taxes for this itinerary.
`fees`	`number` Fees for this itinerary.
`currencyCode`	`string` Currency for `price` , `taxes` , and `fees` .
`updateTime`	`string ( Timestamp format)` Update timestamp for this hotel price. Uses RFC 3339, where generated output will always be Z-normalized and uses 0, 3, 6 or 9 fractional digits. Offsets other than "Z" are also accepted. Examples: `"2014-10-02T15:01:23Z"` , `"2014-10-02T15:01:23.045123456Z"` or `"2014-10-02T15:01:23+05:30"` .

Methods
`get`	Returns the requested price view in full detail.