Property/getPropertySettings

PMS v1 facade method. Read Quendoo's whole property snapshot in one call — property meta, rooms, rates, extras, meals, beds, payment methods, booking modules, OTA codes. The primary setup- time read: a PMS builds its mapping UI from this response.

Cutover status: legacy answers, port pending.

Request

GET https://api.quendoo.com/api/pms/v1/property/getPropertySettings
  ?api_key=…
  &names=rooms,rates      # optional — restrict to a subset. Omit for everything.

Query params

Param Type Required Notes
names comma-separated string no Whitelist of top-level keys to include (see the full list below). Omit or leave empty to return every key.

Every value in names is matched case-sensitively against the top-level key names below. Unknown names are silently ignored.

Keys

Name Contents
property {id, name} for the property itself.
rooms Same shape as getRoomsDetails.
rates Rate plans on the property.
services Extras / add-ons the property sells.
payment_methods Instances (Card X, Bank Y) available on this property.
payment_methods_types Category catalogue (card, bank, cash, …).
meal_plans BB, HB, FB, all-inclusive.
bed_types Bed catalogue used by the room-layout picker. Read-only from the QC API. Custom per-room bed layouts remain a dashboard-only concern; per_person / per_occupancy rate plans no longer need a dashboard step — set sell_type on POST /rate_plans and the vocabulary auto-derives from each room's existing bed capacity (details).
booking_modules Every booking module (booking_buttons) on the property, with id, name, url_key. The url_key is the bm_code in getBookingOffers.
booking_ota_codes OTA reference codes attached to bookings — for a PMS that wants to display "came from Booking.com".

Response

{
  "data": {
    "property": { "id": 4211, "name": "Hotel Panorama" },
    "rooms":    [ /* …see getRoomsDetails… */ ],
    "rates":    [ { "id": 985, "name": "Standard B&B" } ],
    "services": [ { "id": 12, "name": "Breakfast" } ],
    "meal_plans":     [ { "id": "BB", "name": "Bed & breakfast" } ],
    "bed_types":      [ { "id": "queen", "name": "Queen bed" } ],
    "payment_methods":       [ /* … */ ],
    "payment_methods_types": [ /* … */ ],
    "booking_modules": [
      { "id": 3204, "name": "Main website", "url_key": "hotelname" }
    ],
    "booking_ota_codes": [
      { "code": "BDC", "name": "Booking.com" }
    ]
  }
}

Only the keys named in names (or every key when names is omitted) appear at the top level. data is always an object, never an array, even for a single-key selection.

Errors

No errors are declared for this endpoint. If the property is not loadable at all the caller's api_key would already have failed authentication upstream.

Semantics

Notes