repull 0.2.26 → 0.2.27

data/lib/repull/api/reservations_api.rb

@@ -90,9 +90,11 @@ module Repull
     end
 
     # Cancel a reservation
-    # Cancels a reservation where it lives.  - **Mews or Cloudbeds** (hotel-model PMS): cancelled in the PMS, then read back, so Repull and the PMS agree. No cancellation fee is charged. - **Direct, website or owner bookings**: cancelled in Repull — the nights are released and `reservation.cancelled` fires. - **A channel booking** (Airbnb, Booking.com, VRBO) or a booking owned by another PMS: `409 reservation_owned_by_channel`. Cancel it there; the cancellation reaches Repull with the next sync.  Cancelling an already-cancelled reservation is not an error: the response carries `alreadyCancelled: true`.  Returns `403 listing_inactive` when the listing is inactive.
+    # Cancels a reservation where it lives.  - **A booking managed in a connected PMS** (Mews, Cloudbeds, Hostaway, Guesty, Beds24, BookingSync, Lodgify, Smoobu, Hospitable, iGMS): cancelled in the PMS, then read back, so Repull and the PMS agree. No cancellation fee is charged. Lodgify *declines* the booking rather than deleting it. **OwnerRez's API cannot cancel** — `422 pms_write_unsupported`; cancel it in OwnerRez. `GET /v1/listings/{id}` → `capabilities.reservations.cancel` says which applies. - **Direct, website or owner bookings**: cancelled in Repull — the nights are released and `reservation.cancelled` fires. - **A channel booking** (Airbnb, Booking.com, VRBO), including one that came in through a PMS: `409 reservation_owned_by_channel`. Cancel it on the channel; the cancellation reaches Repull with the next sync.  Cancelling an already-cancelled reservation is not an error: the response carries `alreadyCancelled: true`.  PMS integrations other than Mews and Cloudbeds are verified against the vendor's API documentation only.  `X-Account-Id` restricts the reservation to one connected account. Returns `403 listing_inactive` when the listing is inactive.
     # @param id [Integer] Reservation id.
     # @param [Hash] opts the optional parameters
+    # @option opts [String] :idempotency_key Makes a retry of this request safe. Send a unique string (a UUID generated at the point you build the request) and the response is stored for 24 hours: a repeat with the SAME key replays that stored response — tagged `Idempotency-Status: cached` — without running the operation again, so no duplicate reservation, guest or guest message is created.  - Same key while the first request is still in flight → `409 idempotency_key_in_use`. - Same key with a DIFFERENT payload → `422 idempotency_key_reused`. Generate a new key per distinct request; reuse one only when retrying that exact request. - Retryable outcomes are deliberately not stored, so a retry with the same key runs for real: any status >= 500, `408`, `425` and `429`, and the refusals that happen before anything is done and tell you to fix something outside the request first — `connection_reauth_required`, `listing_inactive`, and the rate/daily limits. Every other answer, including a final refusal such as `422 airbnb_rejected`, is stored and replayed.
+    # @option opts [String] :x_account_id Restrict the request to one connected account (a Repull connection id, `GET /v1/connect` → `id`). A listing or reservation outside that account answers `404 not_found`. Omit it to act workspace-wide.
     # @option opts [CancelReservationRequest] :cancel_reservation_request 
     # @return [CancelReservation200Response]
     def cancel_reservation(id, opts = {})
@@ -101,9 +103,11 @@ module Repull
     end
 
     # Cancel a reservation
-    # Cancels a reservation where it lives.  - **Mews or Cloudbeds** (hotel-model PMS): cancelled in the PMS, then read back, so Repull and the PMS agree. No cancellation fee is charged. - **Direct, website or owner bookings**: cancelled in Repull — the nights are released and `reservation.cancelled` fires. - **A channel booking** (Airbnb, Booking.com, VRBO) or a booking owned by another PMS: `409 reservation_owned_by_channel`. Cancel it there; the cancellation reaches Repull with the next sync.  Cancelling an already-cancelled reservation is not an error: the response carries `alreadyCancelled: true`.  Returns `403 listing_inactive` when the listing is inactive.
+    # Cancels a reservation where it lives.  - **A booking managed in a connected PMS** (Mews, Cloudbeds, Hostaway, Guesty, Beds24, BookingSync, Lodgify, Smoobu, Hospitable, iGMS): cancelled in the PMS, then read back, so Repull and the PMS agree. No cancellation fee is charged. Lodgify *declines* the booking rather than deleting it. **OwnerRez's API cannot cancel** — `422 pms_write_unsupported`; cancel it in OwnerRez. `GET /v1/listings/{id}` → `capabilities.reservations.cancel` says which applies. - **Direct, website or owner bookings**: cancelled in Repull — the nights are released and `reservation.cancelled` fires. - **A channel booking** (Airbnb, Booking.com, VRBO), including one that came in through a PMS: `409 reservation_owned_by_channel`. Cancel it on the channel; the cancellation reaches Repull with the next sync.  Cancelling an already-cancelled reservation is not an error: the response carries `alreadyCancelled: true`.  PMS integrations other than Mews and Cloudbeds are verified against the vendor's API documentation only.  `X-Account-Id` restricts the reservation to one connected account. Returns `403 listing_inactive` when the listing is inactive.
     # @param id [Integer] Reservation id.
     # @param [Hash] opts the optional parameters
+    # @option opts [String] :idempotency_key Makes a retry of this request safe. Send a unique string (a UUID generated at the point you build the request) and the response is stored for 24 hours: a repeat with the SAME key replays that stored response — tagged `Idempotency-Status: cached` — without running the operation again, so no duplicate reservation, guest or guest message is created.  - Same key while the first request is still in flight → `409 idempotency_key_in_use`. - Same key with a DIFFERENT payload → `422 idempotency_key_reused`. Generate a new key per distinct request; reuse one only when retrying that exact request. - Retryable outcomes are deliberately not stored, so a retry with the same key runs for real: any status >= 500, `408`, `425` and `429`, and the refusals that happen before anything is done and tell you to fix something outside the request first — `connection_reauth_required`, `listing_inactive`, and the rate/daily limits. Every other answer, including a final refusal such as `422 airbnb_rejected`, is stored and replayed.
+    # @option opts [String] :x_account_id Restrict the request to one connected account (a Repull connection id, `GET /v1/connect` → `id`). A listing or reservation outside that account answers `404 not_found`. Omit it to act workspace-wide.
     # @option opts [CancelReservationRequest] :cancel_reservation_request 
     # @return [Array<(CancelReservation200Response, Integer, Hash)>] CancelReservation200Response data, response status code and response headers
     def cancel_reservation_with_http_info(id, opts = {})
@@ -114,6 +118,10 @@ module Repull
       if @api_client.config.client_side_validation && id.nil?
         fail ArgumentError, "Missing the required parameter 'id' when calling ReservationsApi.cancel_reservation"
       end
+      if @api_client.config.client_side_validation && !opts[:'idempotency_key'].nil? && opts[:'idempotency_key'].to_s.length > 255
+        fail ArgumentError, 'invalid value for "opts[:"idempotency_key"]" when calling ReservationsApi.cancel_reservation, the character length must be smaller than or equal to 255.'
+      end
+
       # resource path
       local_var_path = '/v1/reservations/{id}/cancel'.sub('{id}', CGI.escape(id.to_s))
 
@@ -129,6 +137,8 @@ module Repull
       if !content_type.nil?
           header_params['Content-Type'] = content_type
       end
+      header_params[:'Idempotency-Key'] = opts[:'idempotency_key'] if !opts[:'idempotency_key'].nil?
+      header_params[:'X-Account-Id'] = opts[:'x_account_id'] if !opts[:'x_account_id'].nil?
 
       # form parameters
       form_params = opts[:form_params] || {}
@@ -160,10 +170,11 @@ module Repull
     end
 
     # Create a reservation
-    # Creates a reservation and everything that hangs off one: the guest, the conversation thread, the dashboard item, the calendar block, and the `reservation.created` fan-out that issues the door code and starts the messaging automations.  **Platform is restricted to `direct`, `website` and `owner`.** Reservations on Airbnb, Booking.com and Vrbo are owned by the channel and arrive through sync — creating one here would mint a local booking the channel has never heard of, which then fights the next sync. Create those on the channel.  **Dates are validated** (`YYYY-MM-DD`, and `checkOut` must be after `checkIn`), and an unrecognised field is rejected by name rather than silently ignored.  **This endpoint does not set the price.** There is no `totalPrice` field: the reservation pipeline derives the price breakdown from the property's own rates and overwrites anything supplied, so accepting a total would be taking a value and discarding it. A reservation created here is priced by that engine (`0` when the property has no rates for the range). `currency` IS honoured. Quote a stay with `GET /v1/quotes` before booking if you need the figure up front.  **Availability is NOT checked.** This creates the reservation you asked for even if the dates overlap an existing booking. Call `GET /v1/availability/{propertyId}` first if that matters.  Send `Idempotency-Key` — a network timeout here is exactly the case it exists for: without it, a retry books the guest twice.  Returns `403 listing_inactive` when the listing is inactive. An inactive listing keeps syncing, but cannot be read or changed through the API until it is activated.
+    # Creates a reservation — in the listing's PMS when it has one, otherwise as a direct booking in Repull.  ### Where the booking is made  - **A listing managed in a connected PMS** (Mews, Cloudbeds, Hostaway, Guesty, Beds24, BookingSync, Lodgify, Smoobu, Hospitable, iGMS, OwnerRez): the booking is created **in the PMS first**, then recorded in Repull from the PMS's own record, so the next sync lands on the same confirmation code and nothing is duplicated. A booking is **never** created only in Repull for such a listing — the PMS would keep selling the dates. What the PMS cannot do is refused (`422 pms_write_unsupported`), never faked. The PMS checks availability: taken dates answer `409 pms_unavailable`. - **Any other listing**: a direct booking made in Repull, with everything that hangs off one — the guest, the conversation, the calendar block and the `reservation.created` fan-out that issues the door code and starts the messaging automations. Priced by the listing's own rates; **availability is NOT checked** (call `GET /v1/availability/{propertyId}` first if that matters).  `GET /v1/listings/{id}` → `capabilities.reservations` says which applies to a listing and exactly what it supports (`create`, `modify`, `cancel`, `quote`, `customPrice`, plus `notes`).  ### Fields by listing kind  | Field | PMS listing | Direct-booking listing | |---|---|---| | `listingId`, `checkIn`, `checkOut`, `guest`, `guestCount`, `adults`, `children` | ✓ | ✓ | | `status` | `confirmed` (default) or `tentative` | ✓ | | `totalPrice` | ✓ where `capabilities.reservations.customPrice`; otherwise the PMS prices the stay | `422 unsupported_field` (priced from the listing's rates) | | `notes`, `unitId`, `sendConfirmationEmail` | ✓ | `422 unsupported_field` | | `checkInTime`, `checkOutTime`, `currency`, `guestId` | `422 unsupported_field` (the PMS's own settings apply) | ✓ | | `platform` | `direct` or `website` (`owner` → `422 pms_write_unsupported`; block owner stays in the PMS) | `direct`, `website` or `owner` |  A field a listing cannot take is refused by name, never silently dropped. `platform` never accepts `airbnb` / `booking` / `vrbo`: those reservations are owned by the channel and arrive through sync.  ### Per-PMS limits  | PMS | create | change | cancel | quote | `totalPrice` | Limits | |---|---|---|---|---|---|---| | Mews | ✓ | ✓ | ✓ | – | ✓ | — | | Cloudbeds | ✓ | ✓ | ✓ | – | – | Books at the rate plan's price; group bookings supported. | | Hostaway | ✓ | ✓ | ✓ | ✓ | ✓ | Direct-channel bookings only; a specific unit is refused; a date change keeps the booked total. | | Guesty | ✓ | ✓ | ✓ | ✓ | ✓ | Cancels direct and Vrbo bookings; other channel bookings are cancelled on the channel. | | Beds24 | ✓ | ✓ | ✓ | ✓ | ✓ | Needs the `write:bookings` scope; a multi-room property needs `unitId`. | | BookingSync | ✓ | ✓ | ✓ | ✓ | ✓ | Needs `bookings_write`; fees and taxes are not itemized; no guest email. | | Lodgify | ✓ | ✓ | ✓ (declines) | ✓ | ✓ | Cancel declines the booking; single-room bookings. | | Smoobu | ✓ | ✓ (no dates) | ✓ | ✓ | ✓ | Dates cannot be changed through Smoobu's API — cancel and rebook, or change them in Smoobu. | | Hospitable | ✓ | ✓ | ✓ | ✓ (Direct plan) | ✓ | Manual reservations only; needs `reservation:write`; adds no fees or taxes. | | iGMS | ✓ | ✓ | ✓ | – | ✓ (required) | iGMS direct bookings only; a price is required; no tentative holds. | | OwnerRez | ✓ | ✓ | – | ✓ | – | No cancel through OwnerRez's API; priced by the property's own rates; needs the `full` scope. |  Every PMS except Cloudbeds refuses group bookings, and every vacation-rental PMS refuses to change or cancel a booking that came from a channel (Airbnb, Booking.com, Vrbo…) — that is done on the channel.  **Verification.** Mews and Cloudbeds were run end to end on their vendors' sandboxes. Every other PMS is **verified against the vendor's API documentation only** — no live account has been written to yet. `capabilities.reservations.verifiedAgainst` says which.  ### Idempotency  **Send `Idempotency-Key`.** A network timeout here is exactly the case it exists for. The key is also sent to the PMS as the booking's reference, so even a retry that reaches the PMS again finds the booking instead of making a second one (`409 pms_duplicate` with `existing`, or the existing booking returned). A completed answer is replayed with `Idempotency-Status: cached` and the PMS is not called again. `502 pms_error` (the PMS could not be reached) is NOT stored — retry with the same key. `502 reservation_created_in_pms_only` IS stored, unlike every other 5xx: the booking exists in the PMS and arrives with the next sync, so a retry replays that answer rather than booking twice.  ### Partial success  When the PMS created the booking but a follow-up step did not apply (for example the notes, or a tentative state), the response is still `201`, with `pms.partial: true` and the steps in `pms.failedSections`. The booking exists — do not create it again.  `X-Account-Id` restricts the listing to one connected account. Returns `403 listing_inactive` when the listing is inactive.
     # @param reservation_create_request [ReservationCreateRequest] 
     # @param [Hash] opts the optional parameters
     # @option opts [String] :idempotency_key Makes a retry of this request safe. Send a unique string (a UUID generated at the point you build the request) and the response is stored for 24 hours: a repeat with the SAME key replays that stored response — tagged &#x60;Idempotency-Status: cached&#x60; — without running the operation again, so no duplicate reservation, guest or guest message is created.  - Same key while the first request is still in flight → &#x60;409 idempotency_key_in_use&#x60;. - Same key with a DIFFERENT payload → &#x60;422 idempotency_key_reused&#x60;. Generate a new key per distinct request; reuse one only when retrying that exact request. - Retryable outcomes are deliberately not stored, so a retry with the same key runs for real: any status &gt;&#x3D; 500, &#x60;408&#x60;, &#x60;425&#x60; and &#x60;429&#x60;, and the refusals that happen before anything is done and tell you to fix something outside the request first — &#x60;connection_reauth_required&#x60;, &#x60;listing_inactive&#x60;, and the rate/daily limits. Every other answer, including a final refusal such as &#x60;422 airbnb_rejected&#x60;, is stored and replayed.
+    # @option opts [String] :x_account_id Restrict the request to one connected account (a Repull connection id, &#x60;GET /v1/connect&#x60; → &#x60;id&#x60;). A listing or reservation outside that account answers &#x60;404 not_found&#x60;. Omit it to act workspace-wide.
     # @return [ReservationCreateResponse]
     def create_reservation(reservation_create_request, opts = {})
       data, _status_code, _headers = create_reservation_with_http_info(reservation_create_request, opts)
@@ -171,10 +182,11 @@ module Repull
     end
 
     # Create a reservation
-    # Creates a reservation and everything that hangs off one: the guest, the conversation thread, the dashboard item, the calendar block, and the &#x60;reservation.created&#x60; fan-out that issues the door code and starts the messaging automations.  **Platform is restricted to &#x60;direct&#x60;, &#x60;website&#x60; and &#x60;owner&#x60;.** Reservations on Airbnb, Booking.com and Vrbo are owned by the channel and arrive through sync — creating one here would mint a local booking the channel has never heard of, which then fights the next sync. Create those on the channel.  **Dates are validated** (&#x60;YYYY-MM-DD&#x60;, and &#x60;checkOut&#x60; must be after &#x60;checkIn&#x60;), and an unrecognised field is rejected by name rather than silently ignored.  **This endpoint does not set the price.** There is no &#x60;totalPrice&#x60; field: the reservation pipeline derives the price breakdown from the property&#39;s own rates and overwrites anything supplied, so accepting a total would be taking a value and discarding it. A reservation created here is priced by that engine (&#x60;0&#x60; when the property has no rates for the range). &#x60;currency&#x60; IS honoured. Quote a stay with &#x60;GET /v1/quotes&#x60; before booking if you need the figure up front.  **Availability is NOT checked.** This creates the reservation you asked for even if the dates overlap an existing booking. Call &#x60;GET /v1/availability/{propertyId}&#x60; first if that matters.  Send &#x60;Idempotency-Key&#x60; — a network timeout here is exactly the case it exists for: without it, a retry books the guest twice.  Returns &#x60;403 listing_inactive&#x60; when the listing is inactive. An inactive listing keeps syncing, but cannot be read or changed through the API until it is activated.
+    # Creates a reservation — in the listing&#39;s PMS when it has one, otherwise as a direct booking in Repull.  ### Where the booking is made  - **A listing managed in a connected PMS** (Mews, Cloudbeds, Hostaway, Guesty, Beds24, BookingSync, Lodgify, Smoobu, Hospitable, iGMS, OwnerRez): the booking is created **in the PMS first**, then recorded in Repull from the PMS&#39;s own record, so the next sync lands on the same confirmation code and nothing is duplicated. A booking is **never** created only in Repull for such a listing — the PMS would keep selling the dates. What the PMS cannot do is refused (&#x60;422 pms_write_unsupported&#x60;), never faked. The PMS checks availability: taken dates answer &#x60;409 pms_unavailable&#x60;. - **Any other listing**: a direct booking made in Repull, with everything that hangs off one — the guest, the conversation, the calendar block and the &#x60;reservation.created&#x60; fan-out that issues the door code and starts the messaging automations. Priced by the listing&#39;s own rates; **availability is NOT checked** (call &#x60;GET /v1/availability/{propertyId}&#x60; first if that matters).  &#x60;GET /v1/listings/{id}&#x60; → &#x60;capabilities.reservations&#x60; says which applies to a listing and exactly what it supports (&#x60;create&#x60;, &#x60;modify&#x60;, &#x60;cancel&#x60;, &#x60;quote&#x60;, &#x60;customPrice&#x60;, plus &#x60;notes&#x60;).  ### Fields by listing kind  | Field | PMS listing | Direct-booking listing | |---|---|---| | &#x60;listingId&#x60;, &#x60;checkIn&#x60;, &#x60;checkOut&#x60;, &#x60;guest&#x60;, &#x60;guestCount&#x60;, &#x60;adults&#x60;, &#x60;children&#x60; | ✓ | ✓ | | &#x60;status&#x60; | &#x60;confirmed&#x60; (default) or &#x60;tentative&#x60; | ✓ | | &#x60;totalPrice&#x60; | ✓ where &#x60;capabilities.reservations.customPrice&#x60;; otherwise the PMS prices the stay | &#x60;422 unsupported_field&#x60; (priced from the listing&#39;s rates) | | &#x60;notes&#x60;, &#x60;unitId&#x60;, &#x60;sendConfirmationEmail&#x60; | ✓ | &#x60;422 unsupported_field&#x60; | | &#x60;checkInTime&#x60;, &#x60;checkOutTime&#x60;, &#x60;currency&#x60;, &#x60;guestId&#x60; | &#x60;422 unsupported_field&#x60; (the PMS&#39;s own settings apply) | ✓ | | &#x60;platform&#x60; | &#x60;direct&#x60; or &#x60;website&#x60; (&#x60;owner&#x60; → &#x60;422 pms_write_unsupported&#x60;; block owner stays in the PMS) | &#x60;direct&#x60;, &#x60;website&#x60; or &#x60;owner&#x60; |  A field a listing cannot take is refused by name, never silently dropped. &#x60;platform&#x60; never accepts &#x60;airbnb&#x60; / &#x60;booking&#x60; / &#x60;vrbo&#x60;: those reservations are owned by the channel and arrive through sync.  ### Per-PMS limits  | PMS | create | change | cancel | quote | &#x60;totalPrice&#x60; | Limits | |---|---|---|---|---|---|---| | Mews | ✓ | ✓ | ✓ | – | ✓ | — | | Cloudbeds | ✓ | ✓ | ✓ | – | – | Books at the rate plan&#39;s price; group bookings supported. | | Hostaway | ✓ | ✓ | ✓ | ✓ | ✓ | Direct-channel bookings only; a specific unit is refused; a date change keeps the booked total. | | Guesty | ✓ | ✓ | ✓ | ✓ | ✓ | Cancels direct and Vrbo bookings; other channel bookings are cancelled on the channel. | | Beds24 | ✓ | ✓ | ✓ | ✓ | ✓ | Needs the &#x60;write:bookings&#x60; scope; a multi-room property needs &#x60;unitId&#x60;. | | BookingSync | ✓ | ✓ | ✓ | ✓ | ✓ | Needs &#x60;bookings_write&#x60;; fees and taxes are not itemized; no guest email. | | Lodgify | ✓ | ✓ | ✓ (declines) | ✓ | ✓ | Cancel declines the booking; single-room bookings. | | Smoobu | ✓ | ✓ (no dates) | ✓ | ✓ | ✓ | Dates cannot be changed through Smoobu&#39;s API — cancel and rebook, or change them in Smoobu. | | Hospitable | ✓ | ✓ | ✓ | ✓ (Direct plan) | ✓ | Manual reservations only; needs &#x60;reservation:write&#x60;; adds no fees or taxes. | | iGMS | ✓ | ✓ | ✓ | – | ✓ (required) | iGMS direct bookings only; a price is required; no tentative holds. | | OwnerRez | ✓ | ✓ | – | ✓ | – | No cancel through OwnerRez&#39;s API; priced by the property&#39;s own rates; needs the &#x60;full&#x60; scope. |  Every PMS except Cloudbeds refuses group bookings, and every vacation-rental PMS refuses to change or cancel a booking that came from a channel (Airbnb, Booking.com, Vrbo…) — that is done on the channel.  **Verification.** Mews and Cloudbeds were run end to end on their vendors&#39; sandboxes. Every other PMS is **verified against the vendor&#39;s API documentation only** — no live account has been written to yet. &#x60;capabilities.reservations.verifiedAgainst&#x60; says which.  ### Idempotency  **Send &#x60;Idempotency-Key&#x60;.** A network timeout here is exactly the case it exists for. The key is also sent to the PMS as the booking&#39;s reference, so even a retry that reaches the PMS again finds the booking instead of making a second one (&#x60;409 pms_duplicate&#x60; with &#x60;existing&#x60;, or the existing booking returned). A completed answer is replayed with &#x60;Idempotency-Status: cached&#x60; and the PMS is not called again. &#x60;502 pms_error&#x60; (the PMS could not be reached) is NOT stored — retry with the same key. &#x60;502 reservation_created_in_pms_only&#x60; IS stored, unlike every other 5xx: the booking exists in the PMS and arrives with the next sync, so a retry replays that answer rather than booking twice.  ### Partial success  When the PMS created the booking but a follow-up step did not apply (for example the notes, or a tentative state), the response is still &#x60;201&#x60;, with &#x60;pms.partial: true&#x60; and the steps in &#x60;pms.failedSections&#x60;. The booking exists — do not create it again.  &#x60;X-Account-Id&#x60; restricts the listing to one connected account. Returns &#x60;403 listing_inactive&#x60; when the listing is inactive.
     # @param reservation_create_request [ReservationCreateRequest] 
     # @param [Hash] opts the optional parameters
     # @option opts [String] :idempotency_key Makes a retry of this request safe. Send a unique string (a UUID generated at the point you build the request) and the response is stored for 24 hours: a repeat with the SAME key replays that stored response — tagged &#x60;Idempotency-Status: cached&#x60; — without running the operation again, so no duplicate reservation, guest or guest message is created.  - Same key while the first request is still in flight → &#x60;409 idempotency_key_in_use&#x60;. - Same key with a DIFFERENT payload → &#x60;422 idempotency_key_reused&#x60;. Generate a new key per distinct request; reuse one only when retrying that exact request. - Retryable outcomes are deliberately not stored, so a retry with the same key runs for real: any status &gt;&#x3D; 500, &#x60;408&#x60;, &#x60;425&#x60; and &#x60;429&#x60;, and the refusals that happen before anything is done and tell you to fix something outside the request first — &#x60;connection_reauth_required&#x60;, &#x60;listing_inactive&#x60;, and the rate/daily limits. Every other answer, including a final refusal such as &#x60;422 airbnb_rejected&#x60;, is stored and replayed.
+    # @option opts [String] :x_account_id Restrict the request to one connected account (a Repull connection id, &#x60;GET /v1/connect&#x60; → &#x60;id&#x60;). A listing or reservation outside that account answers &#x60;404 not_found&#x60;. Omit it to act workspace-wide.
     # @return [Array<(ReservationCreateResponse, Integer, Hash)>] ReservationCreateResponse data, response status code and response headers
     def create_reservation_with_http_info(reservation_create_request, opts = {})
       if @api_client.config.debugging
@@ -204,6 +216,7 @@ module Repull
           header_params['Content-Type'] = content_type
       end
       header_params[:'Idempotency-Key'] = opts[:'idempotency_key'] if !opts[:'idempotency_key'].nil?
+      header_params[:'X-Account-Id'] = opts[:'x_account_id'] if !opts[:'x_account_id'].nil?
 
       # form parameters
       form_params = opts[:form_params] || {}
@@ -518,12 +531,84 @@ module Repull
       return data, status_code, headers
     end
 
+    # Quote a reservation in the PMS
+    # Prices a stay and checks its availability **in the PMS that manages the listing**, without booking anything. It is the same check `POST /v1/reservations` makes before booking when no `totalPrice` is sent, so `available: true` with a `total` is what that create would be priced at (dates can still be taken in between).  `available: false` is an answer, not an error: the PMS's reasons are in `restrictions` (minimum stay, closed to arrival, taken dates…).  - A listing **not managed in a PMS** answers `422 pms_not_linked`. Book it directly with `POST /v1/reservations`, or price it with `GET /v1/quotes`. - A PMS **without a quote API** (Mews, Cloudbeds, iGMS) answers `422 pms_write_unsupported`. You can still create the booking; on iGMS a `totalPrice` is required.  `GET /v1/listings/{id}` → `capabilities.reservations.quote` says whether a listing can be quoted.  ### Per-PMS limits  | PMS | create | change | cancel | quote | `totalPrice` | Limits | |---|---|---|---|---|---|---| | Mews | ✓ | ✓ | ✓ | – | ✓ | — | | Cloudbeds | ✓ | ✓ | ✓ | – | – | Books at the rate plan's price; group bookings supported. | | Hostaway | ✓ | ✓ | ✓ | ✓ | ✓ | Direct-channel bookings only; a specific unit is refused; a date change keeps the booked total. | | Guesty | ✓ | ✓ | ✓ | ✓ | ✓ | Cancels direct and Vrbo bookings; other channel bookings are cancelled on the channel. | | Beds24 | ✓ | ✓ | ✓ | ✓ | ✓ | Needs the `write:bookings` scope; a multi-room property needs `unitId`. | | BookingSync | ✓ | ✓ | ✓ | ✓ | ✓ | Needs `bookings_write`; fees and taxes are not itemized; no guest email. | | Lodgify | ✓ | ✓ | ✓ (declines) | ✓ | ✓ | Cancel declines the booking; single-room bookings. | | Smoobu | ✓ | ✓ (no dates) | ✓ | ✓ | ✓ | Dates cannot be changed through Smoobu's API — cancel and rebook, or change them in Smoobu. | | Hospitable | ✓ | ✓ | ✓ | ✓ (Direct plan) | ✓ | Manual reservations only; needs `reservation:write`; adds no fees or taxes. | | iGMS | ✓ | ✓ | ✓ | – | ✓ (required) | iGMS direct bookings only; a price is required; no tentative holds. | | OwnerRez | ✓ | ✓ | – | ✓ | – | No cancel through OwnerRez's API; priced by the property's own rates; needs the `full` scope. |  Every PMS except Cloudbeds refuses group bookings, and every vacation-rental PMS refuses to change or cancel a booking that came from a channel (Airbnb, Booking.com, Vrbo…) — that is done on the channel.  **Verification.** Mews and Cloudbeds were run end to end on their vendors' sandboxes. Every other PMS is **verified against the vendor's API documentation only** — no live account has been written to yet. `capabilities.reservations.verifiedAgainst` says which.  `X-Account-Id` restricts the listing to one connected account. Returns `403 listing_inactive` when the listing is inactive.
+    # @param reservation_quote_request [ReservationQuoteRequest] 
+    # @param [Hash] opts the optional parameters
+    # @option opts [String] :x_account_id Restrict the request to one connected account (a Repull connection id, &#x60;GET /v1/connect&#x60; → &#x60;id&#x60;). A listing or reservation outside that account answers &#x60;404 not_found&#x60;. Omit it to act workspace-wide.
+    # @return [ReservationQuoteResponse]
+    def quote_reservation(reservation_quote_request, opts = {})
+      data, _status_code, _headers = quote_reservation_with_http_info(reservation_quote_request, opts)
+      data
+    end
+
+    # Quote a reservation in the PMS
+    # Prices a stay and checks its availability **in the PMS that manages the listing**, without booking anything. It is the same check &#x60;POST /v1/reservations&#x60; makes before booking when no &#x60;totalPrice&#x60; is sent, so &#x60;available: true&#x60; with a &#x60;total&#x60; is what that create would be priced at (dates can still be taken in between).  &#x60;available: false&#x60; is an answer, not an error: the PMS&#39;s reasons are in &#x60;restrictions&#x60; (minimum stay, closed to arrival, taken dates…).  - A listing **not managed in a PMS** answers &#x60;422 pms_not_linked&#x60;. Book it directly with &#x60;POST /v1/reservations&#x60;, or price it with &#x60;GET /v1/quotes&#x60;. - A PMS **without a quote API** (Mews, Cloudbeds, iGMS) answers &#x60;422 pms_write_unsupported&#x60;. You can still create the booking; on iGMS a &#x60;totalPrice&#x60; is required.  &#x60;GET /v1/listings/{id}&#x60; → &#x60;capabilities.reservations.quote&#x60; says whether a listing can be quoted.  ### Per-PMS limits  | PMS | create | change | cancel | quote | &#x60;totalPrice&#x60; | Limits | |---|---|---|---|---|---|---| | Mews | ✓ | ✓ | ✓ | – | ✓ | — | | Cloudbeds | ✓ | ✓ | ✓ | – | – | Books at the rate plan&#39;s price; group bookings supported. | | Hostaway | ✓ | ✓ | ✓ | ✓ | ✓ | Direct-channel bookings only; a specific unit is refused; a date change keeps the booked total. | | Guesty | ✓ | ✓ | ✓ | ✓ | ✓ | Cancels direct and Vrbo bookings; other channel bookings are cancelled on the channel. | | Beds24 | ✓ | ✓ | ✓ | ✓ | ✓ | Needs the &#x60;write:bookings&#x60; scope; a multi-room property needs &#x60;unitId&#x60;. | | BookingSync | ✓ | ✓ | ✓ | ✓ | ✓ | Needs &#x60;bookings_write&#x60;; fees and taxes are not itemized; no guest email. | | Lodgify | ✓ | ✓ | ✓ (declines) | ✓ | ✓ | Cancel declines the booking; single-room bookings. | | Smoobu | ✓ | ✓ (no dates) | ✓ | ✓ | ✓ | Dates cannot be changed through Smoobu&#39;s API — cancel and rebook, or change them in Smoobu. | | Hospitable | ✓ | ✓ | ✓ | ✓ (Direct plan) | ✓ | Manual reservations only; needs &#x60;reservation:write&#x60;; adds no fees or taxes. | | iGMS | ✓ | ✓ | ✓ | – | ✓ (required) | iGMS direct bookings only; a price is required; no tentative holds. | | OwnerRez | ✓ | ✓ | – | ✓ | – | No cancel through OwnerRez&#39;s API; priced by the property&#39;s own rates; needs the &#x60;full&#x60; scope. |  Every PMS except Cloudbeds refuses group bookings, and every vacation-rental PMS refuses to change or cancel a booking that came from a channel (Airbnb, Booking.com, Vrbo…) — that is done on the channel.  **Verification.** Mews and Cloudbeds were run end to end on their vendors&#39; sandboxes. Every other PMS is **verified against the vendor&#39;s API documentation only** — no live account has been written to yet. &#x60;capabilities.reservations.verifiedAgainst&#x60; says which.  &#x60;X-Account-Id&#x60; restricts the listing to one connected account. Returns &#x60;403 listing_inactive&#x60; when the listing is inactive.
+    # @param reservation_quote_request [ReservationQuoteRequest] 
+    # @param [Hash] opts the optional parameters
+    # @option opts [String] :x_account_id Restrict the request to one connected account (a Repull connection id, &#x60;GET /v1/connect&#x60; → &#x60;id&#x60;). A listing or reservation outside that account answers &#x60;404 not_found&#x60;. Omit it to act workspace-wide.
+    # @return [Array<(ReservationQuoteResponse, Integer, Hash)>] ReservationQuoteResponse data, response status code and response headers
+    def quote_reservation_with_http_info(reservation_quote_request, opts = {})
+      if @api_client.config.debugging
+        @api_client.config.logger.debug 'Calling API: ReservationsApi.quote_reservation ...'
+      end
+      # verify the required parameter 'reservation_quote_request' is set
+      if @api_client.config.client_side_validation && reservation_quote_request.nil?
+        fail ArgumentError, "Missing the required parameter 'reservation_quote_request' when calling ReservationsApi.quote_reservation"
+      end
+      # resource path
+      local_var_path = '/v1/reservations/quote'
+
+      # query parameters
+      query_params = opts[:query_params] || {}
+
+      # header parameters
+      header_params = opts[:header_params] || {}
+      # HTTP header 'Accept' (if needed)
+      header_params['Accept'] = @api_client.select_header_accept(['application/json']) unless header_params['Accept']
+      # HTTP header 'Content-Type'
+      content_type = @api_client.select_header_content_type(['application/json'])
+      if !content_type.nil?
+          header_params['Content-Type'] = content_type
+      end
+      header_params[:'X-Account-Id'] = opts[:'x_account_id'] if !opts[:'x_account_id'].nil?
+
+      # form parameters
+      form_params = opts[:form_params] || {}
+
+      # http body (model)
+      post_body = opts[:debug_body] || @api_client.object_to_http_body(reservation_quote_request)
+
+      # return_type
+      return_type = opts[:debug_return_type] || 'ReservationQuoteResponse'
+
+      # auth_names
+      auth_names = opts[:debug_auth_names] || ['bearerAuth']
+
+      new_options = opts.merge(
+        :operation => :"ReservationsApi.quote_reservation",
+        :header_params => header_params,
+        :query_params => query_params,
+        :form_params => form_params,
+        :body => post_body,
+        :auth_names => auth_names,
+        :return_type => return_type
+      )
+
+      data, status_code, headers = @api_client.call_api(:POST, local_var_path, new_options)
+      if @api_client.config.debugging
+        @api_client.config.logger.debug "API called: ReservationsApi#quote_reservation\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}"
+      end
+      return data, status_code, headers
+    end
+
     # Update a reservation
-    # Changes the dates, the occupancy, or the unit. Drives the same command path the dashboard does, so the side effects come with it: the change audit is appended, bound task due dates re-sync, the old calendar dates unblock and the new ones block, the conversation's cached listing is invalidated, and `reservation.updated` fires — which is what revokes and re-issues the door code.  Supply at least one field; an empty body returns 422 rather than a 200 that changed nothing.  **Moving and re-dating in one call is one operation.** Send `listingId` together with `checkIn`/`checkOut` and it is applied as a single move, so the access code is re-issued once rather than twice.  ### Fields this endpoint deliberately does NOT accept  Each is rejected by name with the reason, never accepted and ignored:  | Field | Why | |---|---| | `guest` / `guestDetails` | Guest name, email and phone live on the guest record. The underlying command has no branch for them, so accepting them would return a success that changed nothing. | | `pricing` / `totalPrice` / `currency` | Repricing writes the price breakdown, the pricing row and a pricing-history entry. It belongs to its own endpoint. | | `status` | Not a field. Cancelling, confirming and checking out are separate operations with materially different side effects — cancellation issues a credit refund and revokes access codes. | | `platform` | Immutable: it records where the booking actually originated. | | `notes` | `internal_notes` is an append-only audit trail the system writes on every change. |  **Availability is NOT checked.** A date change that overlaps another booking will be written. Call `GET /v1/availability/{propertyId}` first if that matters.  Returns `403 listing_inactive` when the reservation is on an inactive listing, or when a `listingId` move targets one; nothing is changed.
+    # Changes the dates, the occupancy, or the unit.  **A stay managed in a connected PMS is changed in the PMS first**, then Repull's copy is refreshed from the PMS's record — changing only Repull's copy would be reverted by the next sync. On such a stay, `checkIn`, `checkOut` and `guestCount` are changed; moving it to another listing and changing its check-in/check-out times are done in the PMS (`422 pms_write_unsupported`), as is anything the PMS's API cannot change (for example dates on Smoobu). A channel booking that came in through the PMS (Airbnb, Booking.com, …) is changed on the channel (`409 reservation_owned_by_channel`). The PMS checks availability: taken dates answer `409 pms_unavailable`. The PMS's outcome comes back as `pms`. `GET /v1/listings/{id}` → `capabilities.reservations.modify` says whether a listing's PMS supports changes.  **Any other stay** drives the same command path the dashboard does, so the side effects come with it: the change audit is appended, bound task due dates re-sync, the old calendar dates unblock and the new ones block, the conversation's cached listing is invalidated, and `reservation.updated` fires — which is what revokes and re-issues the door code.  Supply at least one field; an empty body returns 422 rather than a 200 that changed nothing.  **Moving and re-dating in one call is one operation.** Send `listingId` together with `checkIn`/`checkOut` and it is applied as a single move, so the access code is re-issued once rather than twice.  ### Fields this endpoint deliberately does NOT accept  Each is rejected by name with the reason, never accepted and ignored:  | Field | Why | |---|---| | `guest` / `guestDetails` | Guest name, email and phone live on the guest record. The underlying command has no branch for them, so accepting them would return a success that changed nothing. | | `pricing` / `totalPrice` / `currency` | Repricing writes the price breakdown, the pricing row and a pricing-history entry. It belongs to its own endpoint. | | `status` | Not a field. Cancelling, confirming and checking out are separate operations with materially different side effects — cancellation issues a credit refund and revokes access codes. | | `platform` | Immutable: it records where the booking actually originated. | | `notes` | `internal_notes` is an append-only audit trail the system writes on every change. |  **Availability is NOT checked for stays outside a PMS.** A date change that overlaps another booking will be written. Call `GET /v1/availability/{propertyId}` first if that matters.  `X-Account-Id` restricts the reservation (and a listing it is moved to) to one connected account. Returns `403 listing_inactive` when the reservation is on an inactive listing, or when a `listingId` move targets one; nothing is changed.
     # @param id [Integer] Internal Repull reservation ID.
     # @param reservation_update_request [ReservationUpdateRequest] 
     # @param [Hash] opts the optional parameters
     # @option opts [String] :idempotency_key Makes a retry of this request safe. Send a unique string (a UUID generated at the point you build the request) and the response is stored for 24 hours: a repeat with the SAME key replays that stored response — tagged &#x60;Idempotency-Status: cached&#x60; — without running the operation again, so no duplicate reservation, guest or guest message is created.  - Same key while the first request is still in flight → &#x60;409 idempotency_key_in_use&#x60;. - Same key with a DIFFERENT payload → &#x60;422 idempotency_key_reused&#x60;. Generate a new key per distinct request; reuse one only when retrying that exact request. - Retryable outcomes are deliberately not stored, so a retry with the same key runs for real: any status &gt;&#x3D; 500, &#x60;408&#x60;, &#x60;425&#x60; and &#x60;429&#x60;, and the refusals that happen before anything is done and tell you to fix something outside the request first — &#x60;connection_reauth_required&#x60;, &#x60;listing_inactive&#x60;, and the rate/daily limits. Every other answer, including a final refusal such as &#x60;422 airbnb_rejected&#x60;, is stored and replayed.
+    # @option opts [String] :x_account_id Restrict the request to one connected account (a Repull connection id, &#x60;GET /v1/connect&#x60; → &#x60;id&#x60;). A listing or reservation outside that account answers &#x60;404 not_found&#x60;. Omit it to act workspace-wide.
     # @return [ReservationUpdateResponse]
     def update_reservation(id, reservation_update_request, opts = {})
       data, _status_code, _headers = update_reservation_with_http_info(id, reservation_update_request, opts)
@@ -531,11 +616,12 @@ module Repull
     end
 
     # Update a reservation
-    # Changes the dates, the occupancy, or the unit. Drives the same command path the dashboard does, so the side effects come with it: the change audit is appended, bound task due dates re-sync, the old calendar dates unblock and the new ones block, the conversation&#39;s cached listing is invalidated, and &#x60;reservation.updated&#x60; fires — which is what revokes and re-issues the door code.  Supply at least one field; an empty body returns 422 rather than a 200 that changed nothing.  **Moving and re-dating in one call is one operation.** Send &#x60;listingId&#x60; together with &#x60;checkIn&#x60;/&#x60;checkOut&#x60; and it is applied as a single move, so the access code is re-issued once rather than twice.  ### Fields this endpoint deliberately does NOT accept  Each is rejected by name with the reason, never accepted and ignored:  | Field | Why | |---|---| | &#x60;guest&#x60; / &#x60;guestDetails&#x60; | Guest name, email and phone live on the guest record. The underlying command has no branch for them, so accepting them would return a success that changed nothing. | | &#x60;pricing&#x60; / &#x60;totalPrice&#x60; / &#x60;currency&#x60; | Repricing writes the price breakdown, the pricing row and a pricing-history entry. It belongs to its own endpoint. | | &#x60;status&#x60; | Not a field. Cancelling, confirming and checking out are separate operations with materially different side effects — cancellation issues a credit refund and revokes access codes. | | &#x60;platform&#x60; | Immutable: it records where the booking actually originated. | | &#x60;notes&#x60; | &#x60;internal_notes&#x60; is an append-only audit trail the system writes on every change. |  **Availability is NOT checked.** A date change that overlaps another booking will be written. Call &#x60;GET /v1/availability/{propertyId}&#x60; first if that matters.  Returns &#x60;403 listing_inactive&#x60; when the reservation is on an inactive listing, or when a &#x60;listingId&#x60; move targets one; nothing is changed.
+    # Changes the dates, the occupancy, or the unit.  **A stay managed in a connected PMS is changed in the PMS first**, then Repull&#39;s copy is refreshed from the PMS&#39;s record — changing only Repull&#39;s copy would be reverted by the next sync. On such a stay, &#x60;checkIn&#x60;, &#x60;checkOut&#x60; and &#x60;guestCount&#x60; are changed; moving it to another listing and changing its check-in/check-out times are done in the PMS (&#x60;422 pms_write_unsupported&#x60;), as is anything the PMS&#39;s API cannot change (for example dates on Smoobu). A channel booking that came in through the PMS (Airbnb, Booking.com, …) is changed on the channel (&#x60;409 reservation_owned_by_channel&#x60;). The PMS checks availability: taken dates answer &#x60;409 pms_unavailable&#x60;. The PMS&#39;s outcome comes back as &#x60;pms&#x60;. &#x60;GET /v1/listings/{id}&#x60; → &#x60;capabilities.reservations.modify&#x60; says whether a listing&#39;s PMS supports changes.  **Any other stay** drives the same command path the dashboard does, so the side effects come with it: the change audit is appended, bound task due dates re-sync, the old calendar dates unblock and the new ones block, the conversation&#39;s cached listing is invalidated, and &#x60;reservation.updated&#x60; fires — which is what revokes and re-issues the door code.  Supply at least one field; an empty body returns 422 rather than a 200 that changed nothing.  **Moving and re-dating in one call is one operation.** Send &#x60;listingId&#x60; together with &#x60;checkIn&#x60;/&#x60;checkOut&#x60; and it is applied as a single move, so the access code is re-issued once rather than twice.  ### Fields this endpoint deliberately does NOT accept  Each is rejected by name with the reason, never accepted and ignored:  | Field | Why | |---|---| | &#x60;guest&#x60; / &#x60;guestDetails&#x60; | Guest name, email and phone live on the guest record. The underlying command has no branch for them, so accepting them would return a success that changed nothing. | | &#x60;pricing&#x60; / &#x60;totalPrice&#x60; / &#x60;currency&#x60; | Repricing writes the price breakdown, the pricing row and a pricing-history entry. It belongs to its own endpoint. | | &#x60;status&#x60; | Not a field. Cancelling, confirming and checking out are separate operations with materially different side effects — cancellation issues a credit refund and revokes access codes. | | &#x60;platform&#x60; | Immutable: it records where the booking actually originated. | | &#x60;notes&#x60; | &#x60;internal_notes&#x60; is an append-only audit trail the system writes on every change. |  **Availability is NOT checked for stays outside a PMS.** A date change that overlaps another booking will be written. Call &#x60;GET /v1/availability/{propertyId}&#x60; first if that matters.  &#x60;X-Account-Id&#x60; restricts the reservation (and a listing it is moved to) to one connected account. Returns &#x60;403 listing_inactive&#x60; when the reservation is on an inactive listing, or when a &#x60;listingId&#x60; move targets one; nothing is changed.
     # @param id [Integer] Internal Repull reservation ID.
     # @param reservation_update_request [ReservationUpdateRequest] 
     # @param [Hash] opts the optional parameters
     # @option opts [String] :idempotency_key Makes a retry of this request safe. Send a unique string (a UUID generated at the point you build the request) and the response is stored for 24 hours: a repeat with the SAME key replays that stored response — tagged &#x60;Idempotency-Status: cached&#x60; — without running the operation again, so no duplicate reservation, guest or guest message is created.  - Same key while the first request is still in flight → &#x60;409 idempotency_key_in_use&#x60;. - Same key with a DIFFERENT payload → &#x60;422 idempotency_key_reused&#x60;. Generate a new key per distinct request; reuse one only when retrying that exact request. - Retryable outcomes are deliberately not stored, so a retry with the same key runs for real: any status &gt;&#x3D; 500, &#x60;408&#x60;, &#x60;425&#x60; and &#x60;429&#x60;, and the refusals that happen before anything is done and tell you to fix something outside the request first — &#x60;connection_reauth_required&#x60;, &#x60;listing_inactive&#x60;, and the rate/daily limits. Every other answer, including a final refusal such as &#x60;422 airbnb_rejected&#x60;, is stored and replayed.
+    # @option opts [String] :x_account_id Restrict the request to one connected account (a Repull connection id, &#x60;GET /v1/connect&#x60; → &#x60;id&#x60;). A listing or reservation outside that account answers &#x60;404 not_found&#x60;. Omit it to act workspace-wide.
     # @return [Array<(ReservationUpdateResponse, Integer, Hash)>] ReservationUpdateResponse data, response status code and response headers
     def update_reservation_with_http_info(id, reservation_update_request, opts = {})
       if @api_client.config.debugging
@@ -569,6 +655,7 @@ module Repull
           header_params['Content-Type'] = content_type
       end
       header_params[:'Idempotency-Key'] = opts[:'idempotency_key'] if !opts[:'idempotency_key'].nil?
+      header_params[:'X-Account-Id'] = opts[:'x_account_id'] if !opts[:'x_account_id'].nil?
 
       # form parameters
       form_params = opts[:form_params] || {}

data/lib/repull/api/vrbo_api.rb

@@ -20,8 +20,9 @@ module Repull
       @api_client = api_client
     end
     # List VRBO listings
-    # List the Vrbo units linked to this workspace's listings, from the host's connected Vrbo account (host sign-in, beta).  Inactive listings are left out; they keep syncing and reappear once activated. Use `GET /v1/listings?status=inactive` to find them.
+    # List the Vrbo units linked to this workspace's listings, from the host's connected Vrbo account (host sign-in, beta).  Inactive listings are left out unless `?status=inactive|all` asks for them; they then come back with identity fields only (ids, `listingName`, `listingCity`, `status`, `inactiveReason`). They keep syncing and are complete again once activated.
     # @param [Hash] opts the optional parameters
+    # @option opts [String] :status `active` (default) leaves inactive listings out. `inactive` returns only them and `all` returns both. An inactive listing comes back with identity fields only (ids, `name`, `city`, `status`, `inactiveReason`, its account), which is enough to show what can be activated. Every row carries `status`. (default to 'active')
     # @return [Array<VrboListing>]
     def list_vrbo_listings(opts = {})
       data, _status_code, _headers = list_vrbo_listings_with_http_info(opts)
@@ -29,18 +30,24 @@ module Repull
     end
 
     # List VRBO listings
-    # List the Vrbo units linked to this workspace&#39;s listings, from the host&#39;s connected Vrbo account (host sign-in, beta).  Inactive listings are left out; they keep syncing and reappear once activated. Use &#x60;GET /v1/listings?status&#x3D;inactive&#x60; to find them.
+    # List the Vrbo units linked to this workspace&#39;s listings, from the host&#39;s connected Vrbo account (host sign-in, beta).  Inactive listings are left out unless &#x60;?status&#x3D;inactive|all&#x60; asks for them; they then come back with identity fields only (ids, &#x60;listingName&#x60;, &#x60;listingCity&#x60;, &#x60;status&#x60;, &#x60;inactiveReason&#x60;). They keep syncing and are complete again once activated.
     # @param [Hash] opts the optional parameters
+    # @option opts [String] :status &#x60;active&#x60; (default) leaves inactive listings out. &#x60;inactive&#x60; returns only them and &#x60;all&#x60; returns both. An inactive listing comes back with identity fields only (ids, &#x60;name&#x60;, &#x60;city&#x60;, &#x60;status&#x60;, &#x60;inactiveReason&#x60;, its account), which is enough to show what can be activated. Every row carries &#x60;status&#x60;. (default to 'active')
     # @return [Array<(Array<VrboListing>, Integer, Hash)>] Array<VrboListing> data, response status code and response headers
     def list_vrbo_listings_with_http_info(opts = {})
       if @api_client.config.debugging
         @api_client.config.logger.debug 'Calling API: VRBOApi.list_vrbo_listings ...'
       end
+      allowable_values = ["active", "inactive", "all"]
+      if @api_client.config.client_side_validation && opts[:'status'] && !allowable_values.include?(opts[:'status'])
+        fail ArgumentError, "invalid value for \"status\", must be one of #{allowable_values}"
+      end
       # resource path
       local_var_path = '/v1/channels/vrbo/listings'
 
       # query parameters
       query_params = opts[:query_params] || {}
+      query_params[:'status'] = opts[:'status'] if !opts[:'status'].nil?
 
       # header parameters
       header_params = opts[:header_params] || {}

data/lib/repull/models/airbnb_listing.rb

@@ -19,9 +19,12 @@ module Repull
     # Repull listing id
     attr_accessor :listing_id
 
-    # Listing title
+    # The host's internal nickname for the listing.
     attr_accessor :name
 
+    # The title guests see on the channel (e.g. the Airbnb listing title). `name` is the host's internal nickname for the listing; show `publicName` in anything a guest or end user reads. Present on inactive rows too.
+    attr_accessor :public_name
+
     attr_accessor :city
 
     # Cover photo URL for the listing. **Only present when the caller passes `?include=thumbnail`.** `null` when the listing has no cover photo stored — the listing is still returned.
@@ -34,6 +37,7 @@ module Repull
       {
         :'listing_id' => :'listingId',
         :'name' => :'name',
+        :'public_name' => :'publicName',
         :'city' => :'city',
         :'thumbnail_url' => :'thumbnailUrl',
         :'connections' => :'connections'
@@ -55,6 +59,7 @@ module Repull
       {
         :'listing_id' => :'String',
         :'name' => :'String',
+        :'public_name' => :'String',
         :'city' => :'String',
         :'thumbnail_url' => :'String',
         :'connections' => :'Array<AirbnbConnection>'
@@ -64,6 +69,7 @@ module Repull
     # List of attributes with nullable: true
     def self.openapi_nullable
       Set.new([
+        :'public_name',
         :'city',
         :'thumbnail_url',
       ])
@@ -93,6 +99,10 @@ module Repull
         self.name = attributes[:'name']
       end
 
+      if attributes.key?(:'public_name')
+        self.public_name = attributes[:'public_name']
+      end
+
       if attributes.key?(:'city')
         self.city = attributes[:'city']
       end
@@ -130,6 +140,7 @@ module Repull
       self.class == o.class &&
           listing_id == o.listing_id &&
           name == o.name &&
+          public_name == o.public_name &&
           city == o.city &&
           thumbnail_url == o.thumbnail_url &&
           connections == o.connections
@@ -144,7 +155,7 @@ module Repull
     # Calculates hash code according to all attributes.
     # @return [Integer] Hash code
     def hash
-      [listing_id, name, city, thumbnail_url, connections].hash
+      [listing_id, name, public_name, city, thumbnail_url, connections].hash
     end
 
     # Builds the object from hash

data/lib/repull/models/airbnb_listing_details_write_request.rb

@@ -14,7 +14,7 @@ require 'date'
 require 'time'
 
 module Repull
-  # Update what kind of property this is, when the quiet hours are, or how the guest gets in. At least one field required. These are among the attributes Airbnb locks on established listings — see `blockedFields` on the response.
+  # Update what kind of property this is, when the quiet hours are, how the guest gets in, the house manual, directions or Wi-Fi details. At least one field required. These are among the attributes Airbnb locks on established listings — see `blockedFields` on the response.
   class AirbnbListingDetailsWriteRequest < ApiModelBase
     # The coarse building family.
     attr_accessor :property_type_group
@@ -30,6 +30,18 @@ module Repull
 
     attr_accessor :check_in_option
 
+    # The house manual guests see after booking.
+    attr_accessor :house_manual
+
+    # Directions to the property, shown to booked guests.
+    attr_accessor :directions
+
+    # Wi-Fi network name.
+    attr_accessor :wifi_network
+
+    # Wi-Fi password.
+    attr_accessor :wifi_password
+
     # Attribute mapping from ruby-style variable name to JSON key.
     def self.attribute_map
       {
@@ -37,7 +49,11 @@ module Repull
         :'property_type_category' => :'property_type_category',
         :'room_type_category' => :'room_type_category',
         :'quiet_hours' => :'quiet_hours',
-        :'check_in_option' => :'check_in_option'
+        :'check_in_option' => :'check_in_option',
+        :'house_manual' => :'house_manual',
+        :'directions' => :'directions',
+        :'wifi_network' => :'wifi_network',
+        :'wifi_password' => :'wifi_password'
       }
     end
 
@@ -58,13 +74,21 @@ module Repull
         :'property_type_category' => :'String',
         :'room_type_category' => :'String',
         :'quiet_hours' => :'Array<AirbnbListingDetailsWriteRequestQuietHoursInner>',
-        :'check_in_option' => :'AirbnbListingDetailsWriteRequestCheckInOption'
+        :'check_in_option' => :'AirbnbListingDetailsWriteRequestCheckInOption',
+        :'house_manual' => :'String',
+        :'directions' => :'String',
+        :'wifi_network' => :'String',
+        :'wifi_password' => :'String'
       }
     end
 
     # List of attributes with nullable: true
     def self.openapi_nullable
       Set.new([
+        :'house_manual',
+        :'directions',
+        :'wifi_network',
+        :'wifi_password'
       ])
     end
 
@@ -105,6 +129,22 @@ module Repull
       if attributes.key?(:'check_in_option')
         self.check_in_option = attributes[:'check_in_option']
       end
+
+      if attributes.key?(:'house_manual')
+        self.house_manual = attributes[:'house_manual']
+      end
+
+      if attributes.key?(:'directions')
+        self.directions = attributes[:'directions']
+      end
+
+      if attributes.key?(:'wifi_network')
+        self.wifi_network = attributes[:'wifi_network']
+      end
+
+      if attributes.key?(:'wifi_password')
+        self.wifi_password = attributes[:'wifi_password']
+      end
     end
 
     # Show invalid properties with the reasons. Usually used together with valid?
@@ -116,6 +156,22 @@ module Repull
         invalid_properties.push('invalid value for "quiet_hours", number of items must be greater than or equal to 1.')
       end
 
+      if !@house_manual.nil? && @house_manual.to_s.length > 10000
+        invalid_properties.push('invalid value for "house_manual", the character length must be smaller than or equal to 10000.')
+      end
+
+      if !@directions.nil? && @directions.to_s.length > 5000
+        invalid_properties.push('invalid value for "directions", the character length must be smaller than or equal to 5000.')
+      end
+
+      if !@wifi_network.nil? && @wifi_network.to_s.length > 255
+        invalid_properties.push('invalid value for "wifi_network", the character length must be smaller than or equal to 255.')
+      end
+
+      if !@wifi_password.nil? && @wifi_password.to_s.length > 255
+        invalid_properties.push('invalid value for "wifi_password", the character length must be smaller than or equal to 255.')
+      end
+
       invalid_properties
     end
 
@@ -124,6 +180,10 @@ module Repull
     def valid?
       warn '[DEPRECATED] the `valid?` method is obsolete'
       return false if !@quiet_hours.nil? && @quiet_hours.length < 1
+      return false if !@house_manual.nil? && @house_manual.to_s.length > 10000
+      return false if !@directions.nil? && @directions.to_s.length > 5000
+      return false if !@wifi_network.nil? && @wifi_network.to_s.length > 255
+      return false if !@wifi_password.nil? && @wifi_password.to_s.length > 255
       true
     end
 
@@ -141,6 +201,46 @@ module Repull
       @quiet_hours = quiet_hours
     end
 
+    # Custom attribute writer method with validation
+    # @param [Object] house_manual Value to be assigned
+    def house_manual=(house_manual)
+      if !house_manual.nil? && house_manual.to_s.length > 10000
+        fail ArgumentError, 'invalid value for "house_manual", the character length must be smaller than or equal to 10000.'
+      end
+
+      @house_manual = house_manual
+    end
+
+    # Custom attribute writer method with validation
+    # @param [Object] directions Value to be assigned
+    def directions=(directions)
+      if !directions.nil? && directions.to_s.length > 5000
+        fail ArgumentError, 'invalid value for "directions", the character length must be smaller than or equal to 5000.'
+      end
+
+      @directions = directions
+    end
+
+    # Custom attribute writer method with validation
+    # @param [Object] wifi_network Value to be assigned
+    def wifi_network=(wifi_network)
+      if !wifi_network.nil? && wifi_network.to_s.length > 255
+        fail ArgumentError, 'invalid value for "wifi_network", the character length must be smaller than or equal to 255.'
+      end
+
+      @wifi_network = wifi_network
+    end
+
+    # Custom attribute writer method with validation
+    # @param [Object] wifi_password Value to be assigned
+    def wifi_password=(wifi_password)
+      if !wifi_password.nil? && wifi_password.to_s.length > 255
+        fail ArgumentError, 'invalid value for "wifi_password", the character length must be smaller than or equal to 255.'
+      end
+
+      @wifi_password = wifi_password
+    end
+
     # Checks equality by comparing each attribute.
     # @param [Object] Object to be compared
     def ==(o)
@@ -150,7 +250,11 @@ module Repull
           property_type_category == o.property_type_category &&
           room_type_category == o.room_type_category &&
           quiet_hours == o.quiet_hours &&
-          check_in_option == o.check_in_option
+          check_in_option == o.check_in_option &&
+          house_manual == o.house_manual &&
+          directions == o.directions &&
+          wifi_network == o.wifi_network &&
+          wifi_password == o.wifi_password
     end
 
     # @see the `==` method
@@ -162,7 +266,7 @@ module Repull
     # Calculates hash code according to all attributes.
     # @return [Integer] Hash code
     def hash
-      [property_type_group, property_type_category, room_type_category, quiet_hours, check_in_option].hash
+      [property_type_group, property_type_category, room_type_category, quiet_hours, check_in_option, house_manual, directions, wifi_network, wifi_password].hash
     end
 
     # Builds the object from hash

data/lib/repull/models/airbnb_listing_details_write_request_check_in_option.rb

@@ -14,7 +14,7 @@ require 'date'
 require 'time'
 
 module Repull
-  # How the guest lets themselves in — Airbnb's `check_in_option`.
+  # How the guest lets themselves in — Airbnb's `check_in_option`. `instruction` is the arrival instructions the guest sees.
   class AirbnbListingDetailsWriteRequestCheckInOption < ApiModelBase
     attr_accessor :category
 

data/lib/repull/models/airbnb_permits_write_request_permits_inner.rb

@@ -27,7 +27,7 @@ module Repull
     # The `slug` of the flow you are answering, e.g. `existing_registration` or `exemption_claim`.
     attr_accessor :flow_slug
 
-    # Keyed by each question's `answer_key`. Each value carries exactly one field, chosen by the question's `type`: TEXT → `text_value`, ATTESTATION → `attestation_value`, RADIO → `radio_value`, DATE → `date_value`, SELECT → `selected_options_value`.
+    # Keyed by each question's `answer_key`. Each value carries exactly one `<type>_value` field named after the question's `type` (lower-case): `text_value`, `attestation_value` (boolean), `radio_value`, `dropdown_value`, `email_value`, `future_date_value` (YYYY-MM-DD) and `file_upload_value` (object with the base64 file) are the ones Airbnb returns in production; other question types follow the same pattern. Airbnb validates the value against its question. Example: `{\"email\": {\"email_value\": \"host@example.com\"}, \"expiration_date\": {\"future_date_value\": \"2029-02-04\"}, \"attestation\": {\"attestation_value\": true}}`.
     attr_accessor :answers
 
     # Attribute mapping from ruby-style variable name to JSON key.
@@ -58,7 +58,7 @@ module Repull
         :'regulation_type' => :'String',
         :'regulation_context' => :'String',
         :'flow_slug' => :'String',
-        :'answers' => :'Hash<String, AirbnbPermitsWriteRequestPermitsInnerAnswersValue>'
+        :'answers' => :'Hash<String, Hash<String, Object>>'
       }
     end