repull 0.2.45 → 0.2.46

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (826) hide show
  1. checksums.yaml +4 -4
  2. data/lib/repull/api/airbnb_api.rb +1 -1
  3. data/lib/repull/api/atlas_api.rb +1 -1
  4. data/lib/repull/api/availability_api.rb +5 -5
  5. data/lib/repull/api/billing_api.rb +1 -1
  6. data/lib/repull/api/booking_com_api.rb +1 -1
  7. data/lib/repull/api/connect_api.rb +7 -7
  8. data/lib/repull/api/connections_api.rb +11 -11
  9. data/lib/repull/api/conversations_api.rb +14 -7
  10. data/lib/repull/api/guests_api.rb +1 -1
  11. data/lib/repull/api/health_api.rb +1 -1
  12. data/lib/repull/api/hotels_api.rb +1 -1
  13. data/lib/repull/api/kv_api.rb +1 -1
  14. data/lib/repull/api/listings_api.rb +1 -1
  15. data/lib/repull/api/markets_api.rb +1 -1
  16. data/lib/repull/api/migrate_api.rb +1 -1
  17. data/lib/repull/api/pricing_api.rb +1 -1
  18. data/lib/repull/api/promotions_api.rb +1 -1
  19. data/lib/repull/api/properties_api.rb +3 -3
  20. data/lib/repull/api/quotes_api.rb +1 -1
  21. data/lib/repull/api/reservations_api.rb +5 -5
  22. data/lib/repull/api/resolutions_api.rb +1 -1
  23. data/lib/repull/api/reviews_api.rb +3 -3
  24. data/lib/repull/api/schema_api.rb +1 -1
  25. data/lib/repull/api/system_api.rb +1 -1
  26. data/lib/repull/api/transactions_api.rb +1 -1
  27. data/lib/repull/api/vrbo_api.rb +1 -1
  28. data/lib/repull/api/webhooks_api.rb +1 -1
  29. data/lib/repull/api/workspaces_api.rb +127 -1
  30. data/lib/repull/api_client.rb +1 -1
  31. data/lib/repull/api_error.rb +1 -1
  32. data/lib/repull/api_model_base.rb +1 -1
  33. data/lib/repull/configuration.rb +1 -1
  34. data/lib/repull/models/accept_reservation_request200_response.rb +1 -1
  35. data/lib/repull/models/account_created_event.rb +1 -1
  36. data/lib/repull/models/account_created_payload.rb +1 -1
  37. data/lib/repull/models/account_disconnected_event.rb +1 -1
  38. data/lib/repull/models/account_disconnected_payload.rb +4 -2
  39. data/lib/repull/models/account_disconnected_payload_listings_inner.rb +1 -1
  40. data/lib/repull/models/account_import.rb +1 -1
  41. data/lib/repull/models/account_import_completed_event.rb +1 -1
  42. data/lib/repull/models/account_import_counts.rb +1 -1
  43. data/lib/repull/models/account_import_failed_event.rb +1 -1
  44. data/lib/repull/models/account_import_finished_payload.rb +1 -1
  45. data/lib/repull/models/account_import_stage.rb +1 -1
  46. data/lib/repull/models/account_import_started_event.rb +1 -1
  47. data/lib/repull/models/account_import_started_payload.rb +1 -1
  48. data/lib/repull/models/account_units_added_event.rb +282 -0
  49. data/lib/repull/models/account_units_added_payload.rb +360 -0
  50. data/lib/repull/models/account_units_added_payload_hotels_inner.rb +204 -0
  51. data/lib/repull/models/account_units_added_payload_next_steps_inner.rb +240 -0
  52. data/lib/repull/models/account_units_added_payload_units_inner.rb +271 -0
  53. data/lib/repull/models/acknowledge_booking_reservations_request.rb +1 -1
  54. data/lib/repull/models/ai_operation.rb +1 -1
  55. data/lib/repull/models/ai_operation_completed_event.rb +1 -1
  56. data/lib/repull/models/ai_operation_completed_payload.rb +1 -1
  57. data/lib/repull/models/ai_operation_failed_event.rb +1 -1
  58. data/lib/repull/models/ai_operation_failed_payload.rb +1 -1
  59. data/lib/repull/models/ai_operation_failed_payload_error.rb +1 -1
  60. data/lib/repull/models/airbnb_access.rb +1 -1
  61. data/lib/repull/models/airbnb_access_accounts_inner.rb +1 -1
  62. data/lib/repull/models/airbnb_account_freshness.rb +1 -1
  63. data/lib/repull/models/airbnb_alteration.rb +1 -1
  64. data/lib/repull/models/airbnb_alteration_create_request.rb +1 -1
  65. data/lib/repull/models/airbnb_amenity.rb +1 -1
  66. data/lib/repull/models/airbnb_availability_write_request.rb +1 -1
  67. data/lib/repull/models/airbnb_calendar_operation.rb +1 -1
  68. data/lib/repull/models/airbnb_connection.rb +1 -1
  69. data/lib/repull/models/airbnb_connection_accessibility_amenities_inner.rb +1 -1
  70. data/lib/repull/models/airbnb_connection_amenities_inner.rb +1 -1
  71. data/lib/repull/models/airbnb_connection_host.rb +1 -1
  72. data/lib/repull/models/airbnb_connection_response.rb +1 -1
  73. data/lib/repull/models/airbnb_connection_summary.rb +1 -1
  74. data/lib/repull/models/airbnb_content_write_response.rb +1 -1
  75. data/lib/repull/models/airbnb_data_freshness.rb +1 -1
  76. data/lib/repull/models/airbnb_description_write_request.rb +1 -1
  77. data/lib/repull/models/airbnb_description_write_request_description.rb +1 -1
  78. data/lib/repull/models/airbnb_host_review_submit.rb +1 -1
  79. data/lib/repull/models/airbnb_host_review_submit_category_ratings_inner.rb +1 -1
  80. data/lib/repull/models/airbnb_listing.rb +1 -1
  81. data/lib/repull/models/airbnb_listing_action200_response.rb +1 -1
  82. data/lib/repull/models/airbnb_listing_action200_response_one_of.rb +1 -1
  83. data/lib/repull/models/airbnb_listing_action200_response_one_of1.rb +1 -1
  84. data/lib/repull/models/airbnb_listing_action_request.rb +1 -1
  85. data/lib/repull/models/airbnb_listing_details_response.rb +1 -1
  86. data/lib/repull/models/airbnb_listing_details_write_request.rb +1 -1
  87. data/lib/repull/models/airbnb_listing_details_write_request_check_in_option.rb +1 -1
  88. data/lib/repull/models/airbnb_listing_details_write_request_quiet_hours_inner.rb +1 -1
  89. data/lib/repull/models/airbnb_listing_lifecycle_response.rb +1 -1
  90. data/lib/repull/models/airbnb_listing_list_response.rb +1 -1
  91. data/lib/repull/models/airbnb_permits_response.rb +1 -1
  92. data/lib/repull/models/airbnb_permits_response_cached_inner.rb +1 -1
  93. data/lib/repull/models/airbnb_permits_write_request.rb +1 -1
  94. data/lib/repull/models/airbnb_permits_write_request_permits_inner.rb +1 -1
  95. data/lib/repull/models/airbnb_photo_position.rb +1 -1
  96. data/lib/repull/models/airbnb_pricing_write_request.rb +1 -1
  97. data/lib/repull/models/airbnb_pricing_write_request_fees_inner.rb +1 -1
  98. data/lib/repull/models/airbnb_pricing_write_request_records_inner.rb +1 -1
  99. data/lib/repull/models/airbnb_publish_result.rb +1 -1
  100. data/lib/repull/models/airbnb_reservation.rb +1 -1
  101. data/lib/repull/models/airbnb_reservation_action200_response.rb +1 -1
  102. data/lib/repull/models/airbnb_reservation_action_request.rb +1 -1
  103. data/lib/repull/models/airbnb_reservation_list_response.rb +1 -1
  104. data/lib/repull/models/airbnb_review.rb +1 -1
  105. data/lib/repull/models/airbnb_review_list_response.rb +1 -1
  106. data/lib/repull/models/airbnb_safety_disclosure.rb +1 -1
  107. data/lib/repull/models/airbnb_safety_disclosures_response.rb +1 -1
  108. data/lib/repull/models/airbnb_safety_disclosures_write_request.rb +1 -1
  109. data/lib/repull/models/airbnb_thread.rb +1 -1
  110. data/lib/repull/models/airbnb_thread_list_response.rb +1 -1
  111. data/lib/repull/models/airbnb_transaction.rb +1 -1
  112. data/lib/repull/models/airbnb_transaction_fees.rb +1 -1
  113. data/lib/repull/models/airbnb_transaction_payout.rb +1 -1
  114. data/lib/repull/models/alteration_change.rb +1 -1
  115. data/lib/repull/models/alteration_webhook_object.rb +1 -1
  116. data/lib/repull/models/apply_connection_mappings200_response.rb +1 -1
  117. data/lib/repull/models/apply_connection_mappings200_response_results_inner.rb +1 -1
  118. data/lib/repull/models/apply_connection_mappings_request.rb +1 -1
  119. data/lib/repull/models/apply_connection_mappings_request_mappings_inner.rb +1 -1
  120. data/lib/repull/models/auto_map_connection_units200_response.rb +1 -1
  121. data/lib/repull/models/auto_map_connection_units_request.rb +1 -1
  122. data/lib/repull/models/availability_batch_write_request.rb +23 -2
  123. data/lib/repull/models/availability_write_request.rb +23 -2
  124. data/lib/repull/models/availability_write_result.rb +1 -1
  125. data/lib/repull/models/availability_write_result_synced.rb +17 -5
  126. data/lib/repull/models/availability_write_result_synced_channels_inner.rb +232 -0
  127. data/lib/repull/models/availability_write_settings.rb +23 -2
  128. data/lib/repull/models/billing_notice.rb +323 -0
  129. data/lib/repull/models/booking_availability_state_response.rb +1 -1
  130. data/lib/repull/models/booking_availability_update.rb +1 -1
  131. data/lib/repull/models/booking_availability_update_date_range.rb +1 -1
  132. data/lib/repull/models/booking_availability_update_request.rb +1 -1
  133. data/lib/repull/models/booking_availability_update_request_property_id.rb +1 -1
  134. data/lib/repull/models/booking_availability_update_request_updates_inner.rb +1 -1
  135. data/lib/repull/models/booking_connect_listing_option.rb +1 -1
  136. data/lib/repull/models/booking_connect_room.rb +1 -1
  137. data/lib/repull/models/booking_connect_rooms_response.rb +1 -1
  138. data/lib/repull/models/booking_conversation.rb +1 -1
  139. data/lib/repull/models/booking_derived_pricing_update.rb +1 -1
  140. data/lib/repull/models/booking_derived_pricing_write_response.rb +1 -1
  141. data/lib/repull/models/booking_derived_pricing_write_response_rates_inner.rb +1 -1
  142. data/lib/repull/models/booking_derived_pricing_write_response_verification.rb +1 -1
  143. data/lib/repull/models/booking_derived_pricing_write_response_verification_rows_inner.rb +1 -1
  144. data/lib/repull/models/booking_occupancy_rule.rb +1 -1
  145. data/lib/repull/models/booking_pricing_rate_update.rb +1 -1
  146. data/lib/repull/models/booking_pricing_rate_update_date_range.rb +1 -1
  147. data/lib/repull/models/booking_pricing_rate_update_restrictions.rb +1 -1
  148. data/lib/repull/models/booking_pricing_response.rb +1 -1
  149. data/lib/repull/models/booking_pricing_update_request.rb +1 -1
  150. data/lib/repull/models/booking_pricing_update_response.rb +1 -1
  151. data/lib/repull/models/booking_property.rb +1 -1
  152. data/lib/repull/models/booking_property_action_request.rb +1 -1
  153. data/lib/repull/models/booking_property_action_response.rb +1 -1
  154. data/lib/repull/models/booking_property_listings_inner.rb +1 -1
  155. data/lib/repull/models/booking_publish_result.rb +1 -1
  156. data/lib/repull/models/booking_publish_section_error.rb +1 -1
  157. data/lib/repull/models/booking_rate_write_occupancy.rb +1 -1
  158. data/lib/repull/models/booking_rate_write_price_half.rb +1 -1
  159. data/lib/repull/models/booking_rate_write_restriction_half.rb +1 -1
  160. data/lib/repull/models/booking_rate_write_verification.rb +1 -1
  161. data/lib/repull/models/booking_rate_write_verification_row.rb +1 -1
  162. data/lib/repull/models/booking_reservation.rb +1 -1
  163. data/lib/repull/models/booking_reservation_room.rb +1 -1
  164. data/lib/repull/models/booking_restriction_request_row.rb +1 -1
  165. data/lib/repull/models/booking_restriction_verification.rb +1 -1
  166. data/lib/repull/models/booking_restriction_verification_row.rb +1 -1
  167. data/lib/repull/models/booking_restriction_verification_row_booking_value.rb +1 -1
  168. data/lib/repull/models/booking_restriction_verification_row_expected.rb +1 -1
  169. data/lib/repull/models/booking_restriction_write_response.rb +1 -1
  170. data/lib/repull/models/booking_room_mapping.rb +1 -1
  171. data/lib/repull/models/booking_rooms_rates_response.rb +1 -1
  172. data/lib/repull/models/booking_rooms_rates_response_rooms_inner.rb +1 -1
  173. data/lib/repull/models/booking_rooms_rates_response_rooms_inner_rates_inner.rb +1 -1
  174. data/lib/repull/models/booking_setup_request.rb +1 -1
  175. data/lib/repull/models/booking_setup_request_legal_entity.rb +1 -1
  176. data/lib/repull/models/booking_unacknowledged_event.rb +1 -1
  177. data/lib/repull/models/booking_unacknowledged_payload.rb +1 -1
  178. data/lib/repull/models/booking_upstream_failure.rb +1 -1
  179. data/lib/repull/models/booking_verify_hotel_request.rb +1 -1
  180. data/lib/repull/models/booking_verify_hotel_response.rb +1 -1
  181. data/lib/repull/models/bulk_pricing_failure.rb +1 -1
  182. data/lib/repull/models/bulk_pricing_item.rb +1 -1
  183. data/lib/repull/models/bulk_pricing_request.rb +1 -1
  184. data/lib/repull/models/bulk_pricing_response.rb +1 -1
  185. data/lib/repull/models/calendar_day.rb +1 -1
  186. data/lib/repull/models/calendar_response.rb +1 -1
  187. data/lib/repull/models/cancel_reservation200_response.rb +1 -1
  188. data/lib/repull/models/cancel_reservation_request.rb +1 -1
  189. data/lib/repull/models/channel_degraded_event.rb +1 -1
  190. data/lib/repull/models/channel_degraded_payload.rb +1 -1
  191. data/lib/repull/models/channel_degraded_payload_object.rb +2 -2
  192. data/lib/repull/models/channel_market_state_item.rb +1 -1
  193. data/lib/repull/models/channel_sync_failed_event.rb +1 -1
  194. data/lib/repull/models/channel_sync_failure_payload.rb +1 -1
  195. data/lib/repull/models/channel_sync_failure_payload_failures_inner.rb +1 -1
  196. data/lib/repull/models/channel_sync_failure_payload_object.rb +1 -1
  197. data/lib/repull/models/charge_per.rb +1 -1
  198. data/lib/repull/models/check_migration_cutover200_response.rb +1 -1
  199. data/lib/repull/models/check_migration_cutover_request.rb +1 -1
  200. data/lib/repull/models/check_migration_cutover_request_reservations_inner.rb +1 -1
  201. data/lib/repull/models/clear_kv200_response.rb +1 -1
  202. data/lib/repull/models/connect_host.rb +1 -1
  203. data/lib/repull/models/connect_provider.rb +1 -1
  204. data/lib/repull/models/connect_provider_list_response.rb +1 -1
  205. data/lib/repull/models/connect_session.rb +1 -1
  206. data/lib/repull/models/connect_session_abandoned_event.rb +1 -1
  207. data/lib/repull/models/connect_session_abandoned_payload.rb +1 -1
  208. data/lib/repull/models/connect_session_completed_event.rb +1 -1
  209. data/lib/repull/models/connect_session_completed_payload.rb +3 -3
  210. data/lib/repull/models/connect_status.rb +48 -5
  211. data/lib/repull/models/connect_status_accounts_inner.rb +17 -17
  212. data/lib/repull/models/connect_status_capabilities.rb +1 -1
  213. data/lib/repull/models/connection.rb +36 -2
  214. data/lib/repull/models/connection_access_type.rb +41 -0
  215. data/lib/repull/models/connection_action.rb +1 -1
  216. data/lib/repull/models/connection_list_response.rb +11 -2
  217. data/lib/repull/models/conversation.rb +3 -1
  218. data/lib/repull/models/conversation_capabilities.rb +1 -1
  219. data/lib/repull/models/conversation_detail.rb +3 -1
  220. data/lib/repull/models/conversation_guest.rb +1 -1
  221. data/lib/repull/models/conversation_guest_contact.rb +1 -1
  222. data/lib/repull/models/conversation_host.rb +1 -1
  223. data/lib/repull/models/conversation_list_response.rb +1 -1
  224. data/lib/repull/models/conversation_message_attachment.rb +1 -1
  225. data/lib/repull/models/create_airbnb_listing_room_request.rb +1 -1
  226. data/lib/repull/models/create_airbnb_offer_request.rb +1 -1
  227. data/lib/repull/models/create_airbnb_offer_request_guest_details.rb +1 -1
  228. data/lib/repull/models/create_billing_checkout200_response.rb +1 -1
  229. data/lib/repull/models/create_billing_checkout_request.rb +1 -1
  230. data/lib/repull/models/create_booking_webhook_request.rb +1 -1
  231. data/lib/repull/models/create_connect_session_request.rb +2 -2
  232. data/lib/repull/models/create_connect_session_request_copy.rb +1 -1
  233. data/lib/repull/models/create_connect_session_request_workspace.rb +1 -1
  234. data/lib/repull/models/create_connection_request.rb +1 -1
  235. data/lib/repull/models/create_conversation_special_offer201_response.rb +1 -1
  236. data/lib/repull/models/create_conversation_special_offer201_response_fees_inner.rb +1 -1
  237. data/lib/repull/models/create_conversation_special_offer201_response_guests.rb +1 -1
  238. data/lib/repull/models/create_conversation_special_offer201_response_lines_inner.rb +1 -1
  239. data/lib/repull/models/create_conversation_special_offer_request.rb +1 -1
  240. data/lib/repull/models/create_conversation_special_offer_request_fees_inner.rb +1 -1
  241. data/lib/repull/models/create_conversation_special_offer_request_guests.rb +1 -1
  242. data/lib/repull/models/create_webhook_request.rb +1 -1
  243. data/lib/repull/models/custom_schema.rb +1 -1
  244. data/lib/repull/models/custom_schema_create.rb +1 -1
  245. data/lib/repull/models/custom_schema_create_response.rb +1 -1
  246. data/lib/repull/models/custom_schema_delete_response.rb +1 -1
  247. data/lib/repull/models/custom_schema_list_response.rb +1 -1
  248. data/lib/repull/models/custom_schema_summary.rb +1 -1
  249. data/lib/repull/models/custom_schema_update.rb +1 -1
  250. data/lib/repull/models/deactivate_workspace200_response.rb +147 -0
  251. data/lib/repull/models/deactivate_workspace200_response_data.rb +199 -0
  252. data/lib/repull/models/deactivate_workspace200_response_data_disconnected_inner.rb +156 -0
  253. data/lib/repull/models/decline_reservation_request_request.rb +1 -1
  254. data/lib/repull/models/delete_airbnb_listing_photo200_response.rb +1 -1
  255. data/lib/repull/models/delete_airbnb_listing_room200_response.rb +1 -1
  256. data/lib/repull/models/delete_connection200_response.rb +1 -1
  257. data/lib/repull/models/delete_kv200_response.rb +1 -1
  258. data/lib/repull/models/delete_migration200_response.rb +1 -1
  259. data/lib/repull/models/delete_migration200_response_data.rb +1 -1
  260. data/lib/repull/models/error.rb +1 -1
  261. data/lib/repull/models/error_error.rb +1 -1
  262. data/lib/repull/models/error_error_credits.rb +1 -1
  263. data/lib/repull/models/error_error_listings_inner.rb +1 -1
  264. data/lib/repull/models/error_error_support.rb +1 -1
  265. data/lib/repull/models/error_error_upgrade.rb +2 -2
  266. data/lib/repull/models/get_airbnb_alteration200_response.rb +1 -1
  267. data/lib/repull/models/get_airbnb_booking_settings200_response.rb +1 -1
  268. data/lib/repull/models/get_airbnb_booking_settings200_response_data.rb +1 -1
  269. data/lib/repull/models/get_airbnb_booking_settings200_response_data_advance_notice.rb +1 -1
  270. data/lib/repull/models/get_airbnb_booking_settings200_response_data_booking_window.rb +1 -1
  271. data/lib/repull/models/get_airbnb_booking_settings200_response_data_cancellation.rb +1 -1
  272. data/lib/repull/models/get_airbnb_booking_settings200_response_data_cancellation_non_refundable.rb +1 -1
  273. data/lib/repull/models/get_airbnb_booking_settings200_response_data_check_in.rb +1 -1
  274. data/lib/repull/models/get_airbnb_booking_settings200_response_data_check_in_start.rb +1 -1
  275. data/lib/repull/models/get_airbnb_booking_settings200_response_data_check_out.rb +1 -1
  276. data/lib/repull/models/get_airbnb_booking_settings200_response_data_instant_book.rb +1 -1
  277. data/lib/repull/models/get_airbnb_booking_settings200_response_data_preparation_time.rb +1 -1
  278. data/lib/repull/models/get_airbnb_checkin_guide200_response.rb +1 -1
  279. data/lib/repull/models/get_airbnb_listing_details200_response.rb +1 -1
  280. data/lib/repull/models/get_airbnb_listing_quality200_response.rb +1 -1
  281. data/lib/repull/models/get_airbnb_listing_settings200_response.rb +1 -1
  282. data/lib/repull/models/get_airbnb_offer200_response.rb +1 -1
  283. data/lib/repull/models/get_airbnb_thread200_response.rb +1 -1
  284. data/lib/repull/models/get_billing200_response.rb +1 -1
  285. data/lib/repull/models/get_billing200_response_limits.rb +1 -1
  286. data/lib/repull/models/get_billing200_response_used.rb +1 -1
  287. data/lib/repull/models/get_booking_extranet_login_config200_response.rb +1 -1
  288. data/lib/repull/models/get_booking_extranet_login_status200_response.rb +1 -1
  289. data/lib/repull/models/get_channel_health200_response.rb +1 -1
  290. data/lib/repull/models/get_channel_health200_response_vrbo.rb +1 -1
  291. data/lib/repull/models/get_connect_write_policy200_response.rb +1 -1
  292. data/lib/repull/models/get_health200_response.rb +1 -1
  293. data/lib/repull/models/get_hotel200_response.rb +1 -1
  294. data/lib/repull/models/get_hotel200_response_room_types_inner.rb +1 -1
  295. data/lib/repull/models/get_listing_calendar_sync200_response.rb +1 -1
  296. data/lib/repull/models/get_listing_calendar_sync200_response_channels_inner.rb +1 -1
  297. data/lib/repull/models/get_listing_calendar_sync200_response_channels_inner_problems_inner.rb +1 -1
  298. data/lib/repull/models/get_listing_calendar_sync200_response_channels_inner_queue.rb +1 -1
  299. data/lib/repull/models/get_listing_calendar_sync200_response_channels_inner_queue_last_push.rb +1 -1
  300. data/lib/repull/models/get_listing_markups200_response.rb +1 -1
  301. data/lib/repull/models/get_listing_markups200_response_airbnb_inner.rb +1 -1
  302. data/lib/repull/models/get_listing_markups200_response_booking_inner.rb +1 -1
  303. data/lib/repull/models/get_listing_markups200_response_vrbo_inner.rb +3 -2
  304. data/lib/repull/models/get_migration200_response.rb +1 -1
  305. data/lib/repull/models/get_migration_channel_map200_response.rb +1 -1
  306. data/lib/repull/models/get_migration_report200_response.rb +1 -1
  307. data/lib/repull/models/get_reservation_summary200_response.rb +1 -1
  308. data/lib/repull/models/get_reservation_summary200_response_totals_inner.rb +1 -1
  309. data/lib/repull/models/get_usage_logs200_response.rb +1 -1
  310. data/lib/repull/models/get_usage_logs200_response_data_inner.rb +1 -1
  311. data/lib/repull/models/get_usage_logs200_response_pagination.rb +1 -1
  312. data/lib/repull/models/get_usage_summary200_response.rb +14 -5
  313. data/lib/repull/models/get_usage_summary200_response_breakdown_inner.rb +1 -1
  314. data/lib/repull/models/get_usage_summary200_response_credits.rb +1 -1
  315. data/lib/repull/models/get_usage_summary200_response_limits.rb +1 -1
  316. data/lib/repull/models/get_usage_summary200_response_remaining.rb +1 -1
  317. data/lib/repull/models/get_usage_summary200_response_status_distribution.rb +1 -1
  318. data/lib/repull/models/get_usage_summary200_response_timeline_inner.rb +1 -1
  319. data/lib/repull/models/get_usage_summary200_response_totals.rb +1 -1
  320. data/lib/repull/models/get_usage_summary200_response_used.rb +1 -1
  321. data/lib/repull/models/get_usage_tier200_response.rb +1 -1
  322. data/lib/repull/models/get_usage_tier200_response_limits.rb +1 -1
  323. data/lib/repull/models/get_usage_tier200_response_remaining.rb +1 -1
  324. data/lib/repull/models/get_usage_tier200_response_used.rb +1 -1
  325. data/lib/repull/models/get_vrbo_publish_job200_response.rb +1 -1
  326. data/lib/repull/models/get_vrbo_publish_job200_response_job.rb +4 -3
  327. data/lib/repull/models/get_vrbo_publish_job200_response_job_rejected_photos_inner.rb +1 -1
  328. data/lib/repull/models/guest.rb +1 -1
  329. data/lib/repull/models/guest_contact.rb +1 -1
  330. data/lib/repull/models/guest_create_request.rb +1 -1
  331. data/lib/repull/models/guest_create_response.rb +1 -1
  332. data/lib/repull/models/guest_create_response_pms.rb +1 -1
  333. data/lib/repull/models/guest_flag.rb +1 -1
  334. data/lib/repull/models/guest_list_response.rb +1 -1
  335. data/lib/repull/models/guest_note.rb +1 -1
  336. data/lib/repull/models/guest_profile.rb +1 -1
  337. data/lib/repull/models/guest_reservations_summary.rb +1 -1
  338. data/lib/repull/models/guest_update_request.rb +1 -1
  339. data/lib/repull/models/guest_update_response.rb +1 -1
  340. data/lib/repull/models/guest_update_response_contacts_inner.rb +1 -1
  341. data/lib/repull/models/guest_update_response_pms_inner.rb +1 -1
  342. data/lib/repull/models/import_from_channex200_response.rb +1 -1
  343. data/lib/repull/models/import_from_channex200_response_data.rb +1 -1
  344. data/lib/repull/models/import_from_channex200_response_data_channels_inner.rb +1 -1
  345. data/lib/repull/models/import_from_channex200_response_data_properties_inner.rb +1 -1
  346. data/lib/repull/models/import_from_channex200_response_data_summary.rb +1 -1
  347. data/lib/repull/models/import_from_channex200_response_data_summary_bookings.rb +1 -1
  348. data/lib/repull/models/import_from_channex200_response_data_summary_properties.rb +1 -1
  349. data/lib/repull/models/import_from_channex_request.rb +1 -1
  350. data/lib/repull/models/inquiry_created_event.rb +1 -1
  351. data/lib/repull/models/inquiry_created_payload.rb +1 -1
  352. data/lib/repull/models/inquiry_updated_event.rb +1 -1
  353. data/lib/repull/models/inquiry_updated_payload.rb +1 -1
  354. data/lib/repull/models/inquiry_webhook_object.rb +1 -1
  355. data/lib/repull/models/inquiry_webhook_object_expected_payout.rb +1 -1
  356. data/lib/repull/models/inquiry_webhook_object_guest.rb +1 -1
  357. data/lib/repull/models/inquiry_webhook_object_guests.rb +1 -1
  358. data/lib/repull/models/invite_booking_extranet_user200_response.rb +1 -1
  359. data/lib/repull/models/invite_booking_extranet_user_request.rb +1 -1
  360. data/lib/repull/models/list_airbnb_alterations200_response.rb +1 -1
  361. data/lib/repull/models/list_airbnb_listing_amenities200_response.rb +1 -1
  362. data/lib/repull/models/list_airbnb_listing_amenities200_response_data.rb +1 -1
  363. data/lib/repull/models/list_airbnb_listing_permits200_response.rb +1 -1
  364. data/lib/repull/models/list_airbnb_listing_safety_disclosures200_response.rb +1 -1
  365. data/lib/repull/models/list_airbnb_resolutions200_response.rb +1 -1
  366. data/lib/repull/models/list_airbnb_thread_messages200_response.rb +1 -1
  367. data/lib/repull/models/list_airbnb_thread_messages200_response_data_inner.rb +1 -1
  368. data/lib/repull/models/list_airbnb_thread_messages200_response_pagination.rb +1 -1
  369. data/lib/repull/models/list_airbnb_transactions200_response.rb +1 -1
  370. data/lib/repull/models/list_booking_reservations200_response.rb +1 -1
  371. data/lib/repull/models/list_booking_transactions200_response.rb +1 -1
  372. data/lib/repull/models/list_connection_imports200_response.rb +1 -1
  373. data/lib/repull/models/list_connection_units200_response.rb +1 -1
  374. data/lib/repull/models/list_connection_units200_response_listing_options_inner.rb +1 -1
  375. data/lib/repull/models/list_connection_units200_response_units_inner.rb +1 -1
  376. data/lib/repull/models/list_hotels200_response.rb +1 -1
  377. data/lib/repull/models/list_hotels200_response_data_inner.rb +1 -1
  378. data/lib/repull/models/list_inquiries200_response.rb +1 -1
  379. data/lib/repull/models/list_inquiries200_response_data_inner.rb +1 -1
  380. data/lib/repull/models/list_inquiries200_response_data_inner_expected_payout.rb +1 -1
  381. data/lib/repull/models/list_inquiries200_response_data_inner_guest.rb +1 -1
  382. data/lib/repull/models/list_inquiries200_response_data_inner_guests.rb +1 -1
  383. data/lib/repull/models/list_kv200_response.rb +1 -1
  384. data/lib/repull/models/list_kv200_response_data_inner.rb +1 -1
  385. data/lib/repull/models/list_kv200_response_pagination.rb +1 -1
  386. data/lib/repull/models/list_listing_units200_response.rb +1 -1
  387. data/lib/repull/models/list_listing_units200_response_data_inner.rb +1 -1
  388. data/lib/repull/models/list_migrations200_response.rb +1 -1
  389. data/lib/repull/models/list_workspaces200_response.rb +1 -1
  390. data/lib/repull/models/listing.rb +1 -1
  391. data/lib/repull/models/listing_active_request.rb +1 -1
  392. data/lib/repull/models/listing_active_response.rb +1 -1
  393. data/lib/repull/models/listing_address.rb +1 -1
  394. data/lib/repull/models/listing_address_readiness.rb +1 -1
  395. data/lib/repull/models/listing_amenity.rb +1 -1
  396. data/lib/repull/models/listing_capabilities.rb +1 -1
  397. data/lib/repull/models/listing_channel.rb +1 -1
  398. data/lib/repull/models/listing_comp.rb +1 -1
  399. data/lib/repull/models/listing_comp_nightly.rb +1 -1
  400. data/lib/repull/models/listing_comp_ratings.rb +1 -1
  401. data/lib/repull/models/listing_comps_response.rb +1 -1
  402. data/lib/repull/models/listing_content.rb +1 -1
  403. data/lib/repull/models/listing_content_photo.rb +1 -1
  404. data/lib/repull/models/listing_content_update_request.rb +1 -1
  405. data/lib/repull/models/listing_content_update_request_address.rb +1 -1
  406. data/lib/repull/models/listing_content_update_request_amenities.rb +1 -1
  407. data/lib/repull/models/listing_content_update_request_amenities_one_of_inner.rb +1 -1
  408. data/lib/repull/models/listing_content_update_request_checkout_tasks_inner.rb +1 -1
  409. data/lib/repull/models/listing_content_update_request_details.rb +1 -1
  410. data/lib/repull/models/listing_content_update_request_occupancy.rb +1 -1
  411. data/lib/repull/models/listing_content_update_request_photos_inner.rb +1 -1
  412. data/lib/repull/models/listing_content_update_request_photos_inner_one_of.rb +1 -1
  413. data/lib/repull/models/listing_content_update_request_policies.rb +1 -1
  414. data/lib/repull/models/listing_content_update_request_pricing.rb +1 -1
  415. data/lib/repull/models/listing_content_update_request_rooms_inner.rb +1 -1
  416. data/lib/repull/models/listing_content_update_request_rooms_inner_beds_inner.rb +1 -1
  417. data/lib/repull/models/listing_content_update_response.rb +1 -1
  418. data/lib/repull/models/listing_content_update_response_pms.rb +1 -1
  419. data/lib/repull/models/listing_content_update_response_pms_errors_inner.rb +1 -1
  420. data/lib/repull/models/listing_create_request.rb +1 -1
  421. data/lib/repull/models/listing_create_response.rb +1 -1
  422. data/lib/repull/models/listing_created_event.rb +1 -1
  423. data/lib/repull/models/listing_created_payload.rb +1 -1
  424. data/lib/repull/models/listing_created_payload_address.rb +1 -1
  425. data/lib/repull/models/listing_deleted_event.rb +1 -1
  426. data/lib/repull/models/listing_deleted_payload.rb +1 -1
  427. data/lib/repull/models/listing_details.rb +1 -1
  428. data/lib/repull/models/listing_fee.rb +1 -1
  429. data/lib/repull/models/listing_generate_content_request.rb +1 -1
  430. data/lib/repull/models/listing_generate_content_response.rb +1 -1
  431. data/lib/repull/models/listing_hotel.rb +1 -1
  432. data/lib/repull/models/listing_list_response.rb +11 -2
  433. data/lib/repull/models/listing_market_state_request.rb +1 -1
  434. data/lib/repull/models/listing_market_state_response.rb +1 -1
  435. data/lib/repull/models/listing_parent.rb +1 -1
  436. data/lib/repull/models/listing_photo.rb +1 -1
  437. data/lib/repull/models/listing_photo_delete_request.rb +1 -1
  438. data/lib/repull/models/listing_photo_delete_response.rb +1 -1
  439. data/lib/repull/models/listing_photo_upload_url_request.rb +1 -1
  440. data/lib/repull/models/listing_photo_upload_url_response.rb +1 -1
  441. data/lib/repull/models/listing_photos_response.rb +1 -1
  442. data/lib/repull/models/listing_policies.rb +1 -1
  443. data/lib/repull/models/listing_policies_check_in.rb +1 -1
  444. data/lib/repull/models/listing_policies_check_out.rb +1 -1
  445. data/lib/repull/models/listing_policies_quiet_hours.rb +1 -1
  446. data/lib/repull/models/listing_pricing_apply_request.rb +1 -1
  447. data/lib/repull/models/listing_pricing_apply_response.rb +1 -1
  448. data/lib/repull/models/listing_pricing_history_entry.rb +1 -1
  449. data/lib/repull/models/listing_pricing_history_response.rb +1 -1
  450. data/lib/repull/models/listing_pricing_recommendation.rb +1 -1
  451. data/lib/repull/models/listing_pricing_response.rb +1 -1
  452. data/lib/repull/models/listing_pricing_response_comp_summary.rb +1 -1
  453. data/lib/repull/models/listing_pricing_response_date_range.rb +1 -1
  454. data/lib/repull/models/listing_pricing_response_listing.rb +1 -1
  455. data/lib/repull/models/listing_pricing_settings.rb +1 -1
  456. data/lib/repull/models/listing_pricing_strategy.rb +1 -1
  457. data/lib/repull/models/listing_pricing_strategy_input.rb +1 -1
  458. data/lib/repull/models/listing_publish_airbnb_request.rb +1 -1
  459. data/lib/repull/models/listing_publish_airbnb_response.rb +1 -1
  460. data/lib/repull/models/listing_publish_booking_request.rb +1 -1
  461. data/lib/repull/models/listing_publish_booking_response.rb +1 -1
  462. data/lib/repull/models/listing_publish_status_channel.rb +1 -1
  463. data/lib/repull/models/listing_publish_status_connection.rb +1 -1
  464. data/lib/repull/models/listing_publish_status_response.rb +1 -1
  465. data/lib/repull/models/listing_pull_airbnb_request.rb +1 -1
  466. data/lib/repull/models/listing_pull_response.rb +1 -1
  467. data/lib/repull/models/listing_quality_tier.rb +1 -1
  468. data/lib/repull/models/listing_reactivated_event.rb +1 -1
  469. data/lib/repull/models/listing_room.rb +1 -1
  470. data/lib/repull/models/listing_room_beds_inner.rb +1 -1
  471. data/lib/repull/models/listing_rules.rb +1 -1
  472. data/lib/repull/models/listing_segment.rb +1 -1
  473. data/lib/repull/models/listing_segment_recommendation.rb +1 -1
  474. data/lib/repull/models/listing_segments_response.rb +1 -1
  475. data/lib/repull/models/listing_segments_response_scope.rb +1 -1
  476. data/lib/repull/models/listing_status_batch_request.rb +1 -1
  477. data/lib/repull/models/listing_status_batch_response.rb +1 -1
  478. data/lib/repull/models/listing_suspended_event.rb +1 -1
  479. data/lib/repull/models/listing_suspension_payload.rb +1 -1
  480. data/lib/repull/models/listing_tax.rb +1 -1
  481. data/lib/repull/models/listing_units_inner.rb +1 -1
  482. data/lib/repull/models/listing_updated_event.rb +1 -1
  483. data/lib/repull/models/listing_updated_payload.rb +1 -1
  484. data/lib/repull/models/listing_webhook_object.rb +1 -1
  485. data/lib/repull/models/listing_webhook_object_address.rb +1 -1
  486. data/lib/repull/models/listing_webhook_object_channels_inner.rb +1 -1
  487. data/lib/repull/models/map_airbnb_listing_request.rb +1 -1
  488. data/lib/repull/models/map_airbnb_listing_response.rb +1 -1
  489. data/lib/repull/models/map_booking_room_request.rb +1 -1
  490. data/lib/repull/models/map_booking_room_response.rb +1 -1
  491. data/lib/repull/models/map_connect_booking_rooms_request.rb +1 -1
  492. data/lib/repull/models/map_connect_booking_rooms_response.rb +25 -5
  493. data/lib/repull/models/map_connect_booking_rooms_response_property_status.rb +226 -0
  494. data/lib/repull/models/market_browse_category.rb +1 -1
  495. data/lib/repull/models/market_browse_entry.rb +1 -1
  496. data/lib/repull/models/market_browse_featured.rb +1 -1
  497. data/lib/repull/models/market_browse_response.rb +1 -1
  498. data/lib/repull/models/market_calendar_day.rb +1 -1
  499. data/lib/repull/models/market_calendar_day_events_inner.rb +1 -1
  500. data/lib/repull/models/market_calendar_response.rb +1 -1
  501. data/lib/repull/models/market_detail_response.rb +1 -1
  502. data/lib/repull/models/market_detail_response_price_distribution_inner.rb +1 -1
  503. data/lib/repull/models/market_detail_response_property_type_mix_inner.rb +1 -1
  504. data/lib/repull/models/market_detail_response_supply_trend_inner.rb +1 -1
  505. data/lib/repull/models/market_detail_response_top_comps.rb +1 -1
  506. data/lib/repull/models/market_event.rb +1 -1
  507. data/lib/repull/models/market_my_listing.rb +1 -1
  508. data/lib/repull/models/market_summary.rb +1 -1
  509. data/lib/repull/models/market_top_comp.rb +1 -1
  510. data/lib/repull/models/markets_overview_response.rb +1 -1
  511. data/lib/repull/models/markets_overview_response_browse.rb +1 -1
  512. data/lib/repull/models/markets_overview_response_subscriptions.rb +1 -1
  513. data/lib/repull/models/markets_overview_response_totals.rb +1 -1
  514. data/lib/repull/models/message.rb +1 -1
  515. data/lib/repull/models/message_actor.rb +1 -1
  516. data/lib/repull/models/message_list_response.rb +1 -1
  517. data/lib/repull/models/message_reaction.rb +1 -1
  518. data/lib/repull/models/migration.rb +1 -1
  519. data/lib/repull/models/migration_channel_map.rb +1 -1
  520. data/lib/repull/models/migration_channel_map_listings_inner.rb +1 -1
  521. data/lib/repull/models/migration_channel_map_listings_inner_airbnb.rb +1 -1
  522. data/lib/repull/models/migration_channel_map_listings_inner_booking.rb +1 -1
  523. data/lib/repull/models/migration_channel_map_sources_inner.rb +1 -1
  524. data/lib/repull/models/migration_completed_event.rb +1 -1
  525. data/lib/repull/models/migration_connections_inner.rb +1 -1
  526. data/lib/repull/models/migration_counts.rb +1 -1
  527. data/lib/repull/models/migration_cutover_check.rb +1 -1
  528. data/lib/repull/models/migration_cutover_check_mismatched_inner.rb +1 -1
  529. data/lib/repull/models/migration_failed_event.rb +1 -1
  530. data/lib/repull/models/migration_import_payload.rb +1 -1
  531. data/lib/repull/models/migration_import_payload_results_inner.rb +1 -1
  532. data/lib/repull/models/migration_import_run.rb +1 -1
  533. data/lib/repull/models/migration_import_run_results_inner.rb +1 -1
  534. data/lib/repull/models/migration_report.rb +1 -1
  535. data/lib/repull/models/migration_report_issues_inner.rb +1 -1
  536. data/lib/repull/models/migration_reservation_ref.rb +1 -1
  537. data/lib/repull/models/pagination.rb +1 -1
  538. data/lib/repull/models/payment_completed_event.rb +1 -1
  539. data/lib/repull/models/payment_completed_payload.rb +1 -1
  540. data/lib/repull/models/payment_refunded_event.rb +1 -1
  541. data/lib/repull/models/payment_refunded_payload.rb +1 -1
  542. data/lib/repull/models/payment_webhook_object.rb +1 -1
  543. data/lib/repull/models/payout_completed_event.rb +1 -1
  544. data/lib/repull/models/payout_completed_payload.rb +1 -1
  545. data/lib/repull/models/plan_notice.rb +3 -3
  546. data/lib/repull/models/pms_capabilities.rb +1 -1
  547. data/lib/repull/models/pms_capabilities_calendar.rb +1 -1
  548. data/lib/repull/models/pms_capabilities_conversations.rb +1 -1
  549. data/lib/repull/models/pms_capabilities_guests.rb +1 -1
  550. data/lib/repull/models/pms_capabilities_listings.rb +1 -1
  551. data/lib/repull/models/pms_capabilities_payments.rb +1 -1
  552. data/lib/repull/models/pms_capabilities_reservations.rb +1 -1
  553. data/lib/repull/models/pms_capabilities_reviews.rb +1 -1
  554. data/lib/repull/models/pms_capabilities_tasks.rb +1 -1
  555. data/lib/repull/models/pms_write_policy.rb +1 -1
  556. data/lib/repull/models/pms_write_policy_calendar.rb +1 -1
  557. data/lib/repull/models/pms_write_policy_reservations.rb +1 -1
  558. data/lib/repull/models/postal_address.rb +1 -1
  559. data/lib/repull/models/preapprove_conversation201_response.rb +1 -1
  560. data/lib/repull/models/preapprove_conversation_request.rb +1 -1
  561. data/lib/repull/models/preview_conversation_special_offer_request.rb +1 -1
  562. data/lib/repull/models/preview_conversation_special_offer_request_fees_inner.rb +1 -1
  563. data/lib/repull/models/preview_conversation_special_offer_request_guests.rb +1 -1
  564. data/lib/repull/models/promotion.rb +1 -1
  565. data/lib/repull/models/promotion_applies_to.rb +1 -1
  566. data/lib/repull/models/promotion_bulk_request.rb +1 -1
  567. data/lib/repull/models/promotion_bulk_response.rb +1 -1
  568. data/lib/repull/models/promotion_bulk_response_data_inner.rb +1 -1
  569. data/lib/repull/models/promotion_bulk_response_data_inner_error.rb +1 -1
  570. data/lib/repull/models/promotion_bulk_response_summary.rb +1 -1
  571. data/lib/repull/models/promotion_catalog.rb +1 -1
  572. data/lib/repull/models/promotion_catalog_channels_inner.rb +1 -1
  573. data/lib/repull/models/promotion_catalog_entry.rb +1 -1
  574. data/lib/repull/models/promotion_catalog_field.rb +1 -1
  575. data/lib/repull/models/promotion_catalog_field_options_inner.rb +1 -1
  576. data/lib/repull/models/promotion_catalog_response.rb +1 -1
  577. data/lib/repull/models/promotion_create_request.rb +1 -1
  578. data/lib/repull/models/promotion_delete_response.rb +1 -1
  579. data/lib/repull/models/promotion_delete_response_data.rb +1 -1
  580. data/lib/repull/models/promotion_discount.rb +1 -1
  581. data/lib/repull/models/promotion_input.rb +1 -1
  582. data/lib/repull/models/promotion_list_response.rb +1 -1
  583. data/lib/repull/models/promotion_refresh_response.rb +1 -1
  584. data/lib/repull/models/promotion_response.rb +1 -1
  585. data/lib/repull/models/promotion_rules.rb +1 -1
  586. data/lib/repull/models/promotion_rules_blackout_dates_quota.rb +1 -1
  587. data/lib/repull/models/promotion_rules_booking_window.rb +1 -1
  588. data/lib/repull/models/promotion_rules_last_minute.rb +1 -1
  589. data/lib/repull/models/promotion_rules_stay_window.rb +1 -1
  590. data/lib/repull/models/promotion_type.rb +1 -1
  591. data/lib/repull/models/promotion_update_request.rb +1 -1
  592. data/lib/repull/models/promotion_usage.rb +1 -1
  593. data/lib/repull/models/promotion_usage_revenue.rb +1 -1
  594. data/lib/repull/models/property.rb +1 -1
  595. data/lib/repull/models/property_availability.rb +1 -1
  596. data/lib/repull/models/property_availability_coverage.rb +1 -1
  597. data/lib/repull/models/property_availability_day.rb +1 -1
  598. data/lib/repull/models/property_availability_unit.rb +1 -1
  599. data/lib/repull/models/property_list_response.rb +11 -2
  600. data/lib/repull/models/publish_listing_to_vrbo_request.rb +2 -2
  601. data/lib/repull/models/publish_section_error.rb +1 -1
  602. data/lib/repull/models/quote.rb +1 -1
  603. data/lib/repull/models/quote_pricing.rb +1 -1
  604. data/lib/repull/models/reactivate_workspace200_response.rb +147 -0
  605. data/lib/repull/models/reactivate_workspace200_response_data.rb +209 -0
  606. data/lib/repull/models/recheck_booking_extranet_login200_response.rb +1 -1
  607. data/lib/repull/models/recheck_booking_extranet_login_request.rb +1 -1
  608. data/lib/repull/models/record_account.rb +6 -5
  609. data/lib/repull/models/refresh_airbnb_resolutions200_response.rb +1 -1
  610. data/lib/repull/models/refresh_airbnb_resolutions200_response_accounts_inner.rb +1 -1
  611. data/lib/repull/models/refresh_airbnb_resolutions200_response_accounts_inner_error.rb +1 -1
  612. data/lib/repull/models/refresh_airbnb_resolutions_request.rb +1 -1
  613. data/lib/repull/models/reorder_airbnb_listing_photos200_response.rb +1 -1
  614. data/lib/repull/models/reorder_airbnb_listing_photos200_response_data.rb +1 -1
  615. data/lib/repull/models/reorder_airbnb_listing_photos_request.rb +1 -1
  616. data/lib/repull/models/replay_webhook_delivery_request.rb +1 -1
  617. data/lib/repull/models/reply_booking_review200_response.rb +1 -1
  618. data/lib/repull/models/reply_booking_review_request.rb +1 -1
  619. data/lib/repull/models/reply_to_review201_response.rb +1 -1
  620. data/lib/repull/models/reply_to_review_request.rb +1 -1
  621. data/lib/repull/models/repull_ping_event.rb +1 -1
  622. data/lib/repull/models/repull_ping_payload.rb +1 -1
  623. data/lib/repull/models/reservation.rb +1 -1
  624. data/lib/repull/models/reservation_access_code.rb +1 -1
  625. data/lib/repull/models/reservation_access_code_locks_inner.rb +1 -1
  626. data/lib/repull/models/reservation_alteration_created_event.rb +1 -1
  627. data/lib/repull/models/reservation_alteration_created_payload.rb +1 -1
  628. data/lib/repull/models/reservation_alteration_responded_event.rb +1 -1
  629. data/lib/repull/models/reservation_alteration_responded_payload.rb +1 -1
  630. data/lib/repull/models/reservation_cancelled_event.rb +1 -1
  631. data/lib/repull/models/reservation_cancelled_payload.rb +1 -1
  632. data/lib/repull/models/reservation_capabilities.rb +1 -1
  633. data/lib/repull/models/reservation_create_request.rb +1 -1
  634. data/lib/repull/models/reservation_create_response.rb +1 -1
  635. data/lib/repull/models/reservation_create_response_unit.rb +1 -1
  636. data/lib/repull/models/reservation_created_event.rb +1 -1
  637. data/lib/repull/models/reservation_created_payload.rb +1 -1
  638. data/lib/repull/models/reservation_financials.rb +1 -1
  639. data/lib/repull/models/reservation_guest_financials.rb +1 -1
  640. data/lib/repull/models/reservation_guest_input.rb +1 -1
  641. data/lib/repull/models/reservation_host_financials.rb +1 -1
  642. data/lib/repull/models/reservation_list_response.rb +1 -1
  643. data/lib/repull/models/reservation_message_reaction_event.rb +1 -1
  644. data/lib/repull/models/reservation_message_reaction_payload.rb +1 -1
  645. data/lib/repull/models/reservation_message_reaction_payload_reaction.rb +1 -1
  646. data/lib/repull/models/reservation_message_read_event.rb +1 -1
  647. data/lib/repull/models/reservation_message_read_payload.rb +1 -1
  648. data/lib/repull/models/reservation_message_received_event.rb +1 -1
  649. data/lib/repull/models/reservation_message_received_payload.rb +1 -1
  650. data/lib/repull/models/reservation_message_received_payload_from.rb +1 -1
  651. data/lib/repull/models/reservation_message_sent_event.rb +1 -1
  652. data/lib/repull/models/reservation_message_sent_payload.rb +1 -1
  653. data/lib/repull/models/reservation_message_sent_payload_from.rb +1 -1
  654. data/lib/repull/models/reservation_message_updated_event.rb +1 -1
  655. data/lib/repull/models/reservation_message_updated_payload.rb +1 -1
  656. data/lib/repull/models/reservation_message_updated_payload_from.rb +1 -1
  657. data/lib/repull/models/reservation_money_line.rb +1 -1
  658. data/lib/repull/models/reservation_occupancy.rb +1 -1
  659. data/lib/repull/models/reservation_pms_outcome.rb +1 -1
  660. data/lib/repull/models/reservation_pms_outcome_quote.rb +1 -1
  661. data/lib/repull/models/reservation_pms_section_error.rb +1 -1
  662. data/lib/repull/models/reservation_primary_guest.rb +1 -1
  663. data/lib/repull/models/reservation_quote_request.rb +1 -1
  664. data/lib/repull/models/reservation_quote_response.rb +1 -1
  665. data/lib/repull/models/reservation_quote_response_breakdown.rb +1 -1
  666. data/lib/repull/models/reservation_request_created_event.rb +1 -1
  667. data/lib/repull/models/reservation_request_created_payload.rb +1 -1
  668. data/lib/repull/models/reservation_request_updated_event.rb +1 -1
  669. data/lib/repull/models/reservation_request_updated_payload.rb +1 -1
  670. data/lib/repull/models/reservation_thread_assigned_event.rb +1 -1
  671. data/lib/repull/models/reservation_thread_assigned_payload.rb +1 -1
  672. data/lib/repull/models/reservation_thread_assigned_payload_object.rb +1 -1
  673. data/lib/repull/models/reservation_unit.rb +1 -1
  674. data/lib/repull/models/reservation_update_request.rb +1 -1
  675. data/lib/repull/models/reservation_update_response.rb +1 -1
  676. data/lib/repull/models/reservation_updated_event.rb +1 -1
  677. data/lib/repull/models/reservation_updated_payload.rb +1 -1
  678. data/lib/repull/models/reservation_webhook_object.rb +1 -1
  679. data/lib/repull/models/resolution.rb +1 -1
  680. data/lib/repull/models/respond_airbnb_review_request.rb +1 -1
  681. data/lib/repull/models/resume_connect400_response.rb +1 -1
  682. data/lib/repull/models/resume_connect500_response.rb +1 -1
  683. data/lib/repull/models/review.rb +1 -1
  684. data/lib/repull/models/review_category.rb +1 -1
  685. data/lib/repull/models/review_created_event.rb +1 -1
  686. data/lib/repull/models/review_created_payload.rb +1 -1
  687. data/lib/repull/models/review_list_response.rb +1 -1
  688. data/lib/repull/models/review_responded_event.rb +1 -1
  689. data/lib/repull/models/review_responded_payload.rb +1 -1
  690. data/lib/repull/models/review_response.rb +1 -1
  691. data/lib/repull/models/review_webhook_object.rb +1 -1
  692. data/lib/repull/models/rotate_webhook_secret200_response.rb +1 -1
  693. data/lib/repull/models/run_migration_import202_response.rb +1 -1
  694. data/lib/repull/models/run_migration_import202_response_data.rb +1 -1
  695. data/lib/repull/models/run_migration_import202_response_data_queued_inner.rb +1 -1
  696. data/lib/repull/models/run_migration_import_request.rb +1 -1
  697. data/lib/repull/models/search_connect_session_listing_options200_response.rb +1 -1
  698. data/lib/repull/models/search_connect_session_listing_options200_response_data_inner.rb +1 -1
  699. data/lib/repull/models/search_connection_listing_options200_response.rb +1 -1
  700. data/lib/repull/models/select_connect_provider_request.rb +1 -1
  701. data/lib/repull/models/select_provider_response.rb +1 -1
  702. data/lib/repull/models/send_airbnb_message201_response.rb +1 -1
  703. data/lib/repull/models/send_airbnb_message_request.rb +1 -1
  704. data/lib/repull/models/send_booking_message_request.rb +1 -1
  705. data/lib/repull/models/send_message_attachment.rb +1 -1
  706. data/lib/repull/models/send_message_part.rb +1 -1
  707. data/lib/repull/models/send_message_request.rb +1 -1
  708. data/lib/repull/models/send_message_response.rb +1 -1
  709. data/lib/repull/models/sent_attachment.rb +1 -1
  710. data/lib/repull/models/set_airbnb_listing_cover_photo200_response.rb +1 -1
  711. data/lib/repull/models/set_airbnb_listing_cover_photo200_response_data.rb +1 -1
  712. data/lib/repull/models/set_airbnb_listing_cover_photo_request.rb +1 -1
  713. data/lib/repull/models/set_kv_request.rb +1 -1
  714. data/lib/repull/models/set_listing_markup_request.rb +2 -2
  715. data/lib/repull/models/start_booking_extranet_login200_response.rb +1 -1
  716. data/lib/repull/models/start_booking_extranet_login_request.rb +1 -1
  717. data/lib/repull/models/submit_beds24_credentials200_response.rb +1 -1
  718. data/lib/repull/models/submit_beds24_credentials_request.rb +1 -1
  719. data/lib/repull/models/submit_bookingsync_credentials_request.rb +1 -1
  720. data/lib/repull/models/submit_ciirus_credentials200_response.rb +1 -1
  721. data/lib/repull/models/submit_ciirus_credentials200_response_account_info.rb +1 -1
  722. data/lib/repull/models/submit_ciirus_credentials_request.rb +1 -1
  723. data/lib/repull/models/submit_ciirus_credentials_request_credentials.rb +1 -1
  724. data/lib/repull/models/submit_cloudbeds_credentials200_response.rb +1 -1
  725. data/lib/repull/models/submit_cloudbeds_credentials200_response_account_info.rb +1 -1
  726. data/lib/repull/models/submit_cloudbeds_credentials200_response_webhooks.rb +1 -1
  727. data/lib/repull/models/submit_cloudbeds_credentials_request.rb +1 -1
  728. data/lib/repull/models/submit_cloudbeds_credentials_request_credentials.rb +1 -1
  729. data/lib/repull/models/submit_guest_review200_response.rb +1 -1
  730. data/lib/repull/models/submit_guesty_credentials_request.rb +1 -1
  731. data/lib/repull/models/submit_hospitable_credentials_request.rb +1 -1
  732. data/lib/repull/models/submit_hostaway_credentials_request.rb +1 -1
  733. data/lib/repull/models/submit_igms_credentials_request.rb +1 -1
  734. data/lib/repull/models/submit_lodgify_credentials_request.rb +1 -1
  735. data/lib/repull/models/submit_mews_credentials200_response.rb +1 -1
  736. data/lib/repull/models/submit_mews_credentials200_response_account_info.rb +1 -1
  737. data/lib/repull/models/submit_mews_credentials_request.rb +1 -1
  738. data/lib/repull/models/submit_mews_credentials_request_credentials.rb +1 -1
  739. data/lib/repull/models/submit_ownerrez_credentials_request.rb +1 -1
  740. data/lib/repull/models/submit_smoobu_credentials_request.rb +1 -1
  741. data/lib/repull/models/submit_smoobu_credentials_request_credentials.rb +1 -1
  742. data/lib/repull/models/submit_track_credentials200_response.rb +1 -1
  743. data/lib/repull/models/submit_track_credentials200_response_account_info.rb +1 -1
  744. data/lib/repull/models/submit_track_credentials200_response_first_sync.rb +1 -1
  745. data/lib/repull/models/submit_track_credentials_request.rb +1 -1
  746. data/lib/repull/models/submit_track_credentials_request_credentials.rb +1 -1
  747. data/lib/repull/models/submit_vrbo_credentials_request.rb +1 -1
  748. data/lib/repull/models/sync_airbnb_transactions200_response.rb +1 -1
  749. data/lib/repull/models/sync_airbnb_transactions200_response_accounts_inner.rb +1 -1
  750. data/lib/repull/models/sync_airbnb_transactions200_response_accounts_inner_error.rb +1 -1
  751. data/lib/repull/models/sync_airbnb_transactions_request.rb +1 -1
  752. data/lib/repull/models/test_webhook_request.rb +1 -1
  753. data/lib/repull/models/transaction.rb +1 -1
  754. data/lib/repull/models/transaction_fees.rb +1 -1
  755. data/lib/repull/models/transaction_payout.rb +1 -1
  756. data/lib/repull/models/update_airbnb_booking_settings200_response.rb +1 -1
  757. data/lib/repull/models/update_airbnb_booking_settings200_response_data.rb +1 -1
  758. data/lib/repull/models/update_airbnb_booking_settings_request.rb +1 -1
  759. data/lib/repull/models/update_airbnb_booking_settings_request_advance_notice.rb +1 -1
  760. data/lib/repull/models/update_airbnb_booking_settings_request_booking_window.rb +1 -1
  761. data/lib/repull/models/update_airbnb_booking_settings_request_cancellation.rb +1 -1
  762. data/lib/repull/models/update_airbnb_booking_settings_request_cancellation_non_refundable.rb +1 -1
  763. data/lib/repull/models/update_airbnb_booking_settings_request_check_in.rb +1 -1
  764. data/lib/repull/models/update_airbnb_booking_settings_request_check_out.rb +1 -1
  765. data/lib/repull/models/update_airbnb_booking_settings_request_instant_book.rb +1 -1
  766. data/lib/repull/models/update_airbnb_booking_settings_request_preparation_time.rb +1 -1
  767. data/lib/repull/models/update_airbnb_checkin_guide200_response.rb +1 -1
  768. data/lib/repull/models/update_airbnb_checkin_guide200_response_data.rb +1 -1
  769. data/lib/repull/models/update_airbnb_checkin_guide200_response_data_steps_inner.rb +1 -1
  770. data/lib/repull/models/update_airbnb_checkin_guide_request.rb +1 -1
  771. data/lib/repull/models/update_airbnb_checkin_guide_request_steps_inner.rb +1 -1
  772. data/lib/repull/models/update_airbnb_listing_amenities200_response.rb +1 -1
  773. data/lib/repull/models/update_airbnb_listing_amenities200_response_data.rb +1 -1
  774. data/lib/repull/models/update_airbnb_listing_amenities_request.rb +1 -1
  775. data/lib/repull/models/update_airbnb_listing_amenities_request_accessibility_amenities_inner.rb +1 -1
  776. data/lib/repull/models/update_airbnb_listing_amenities_request_amenities_inner.rb +1 -1
  777. data/lib/repull/models/update_airbnb_listing_permits200_response.rb +1 -1
  778. data/lib/repull/models/update_airbnb_listing_photo200_response.rb +1 -1
  779. data/lib/repull/models/update_airbnb_listing_photo_request.rb +1 -1
  780. data/lib/repull/models/update_airbnb_listing_room200_response.rb +1 -1
  781. data/lib/repull/models/update_airbnb_listing_room_request.rb +1 -1
  782. data/lib/repull/models/update_airbnb_listing_room_request_beds_inner.rb +1 -1
  783. data/lib/repull/models/update_airbnb_listing_room_request_room_amenities_inner.rb +1 -1
  784. data/lib/repull/models/update_airbnb_listing_room_request_room_amenities_inner_value.rb +1 -1
  785. data/lib/repull/models/update_airbnb_listing_safety_disclosures200_response.rb +1 -1
  786. data/lib/repull/models/update_airbnb_message_request.rb +1 -1
  787. data/lib/repull/models/update_booking_availability200_response.rb +1 -1
  788. data/lib/repull/models/update_booking_charges_request.rb +1 -1
  789. data/lib/repull/models/update_booking_content_request.rb +1 -1
  790. data/lib/repull/models/update_booking_content_request_content_data_inner.rb +1 -1
  791. data/lib/repull/models/update_booking_content_request_photos_inner.rb +1 -1
  792. data/lib/repull/models/update_connect_write_policy_request.rb +1 -1
  793. data/lib/repull/models/update_connect_write_policy_request_calendar.rb +1 -1
  794. data/lib/repull/models/update_connect_write_policy_request_reservations.rb +1 -1
  795. data/lib/repull/models/update_listing_pricing_strategy200_response.rb +1 -1
  796. data/lib/repull/models/update_webhook_request.rb +1 -1
  797. data/lib/repull/models/upload_airbnb_listing_photos_request.rb +1 -1
  798. data/lib/repull/models/upload_airbnb_listing_photos_request_photos_inner.rb +1 -1
  799. data/lib/repull/models/upload_airbnb_listing_photos_request_photos_inner_listing_id.rb +1 -1
  800. data/lib/repull/models/usage_quota_warning_event.rb +1 -1
  801. data/lib/repull/models/usage_quota_warning_payload.rb +1 -1
  802. data/lib/repull/models/usage_quota_warning_payload_top_operation.rb +1 -1
  803. data/lib/repull/models/vrbo_import_status.rb +1 -1
  804. data/lib/repull/models/vrbo_listing.rb +1 -1
  805. data/lib/repull/models/vrbo_login200_response.rb +1 -1
  806. data/lib/repull/models/vrbo_login_request.rb +1 -1
  807. data/lib/repull/models/vrbo_reservation.rb +1 -1
  808. data/lib/repull/models/vrbo_reservation_list_response.rb +1 -1
  809. data/lib/repull/models/webhook_delivery.rb +1 -1
  810. data/lib/repull/models/webhook_delivery_detail.rb +1 -1
  811. data/lib/repull/models/webhook_delivery_list_response.rb +1 -1
  812. data/lib/repull/models/webhook_event.rb +3 -1
  813. data/lib/repull/models/webhook_event_account.rb +3 -3
  814. data/lib/repull/models/webhook_event_catalog.rb +1 -1
  815. data/lib/repull/models/webhook_event_catalog_domains_inner.rb +1 -1
  816. data/lib/repull/models/webhook_event_catalog_entry.rb +1 -1
  817. data/lib/repull/models/webhook_event_type.rb +3 -2
  818. data/lib/repull/models/webhook_list_response.rb +1 -1
  819. data/lib/repull/models/webhook_subscription.rb +1 -1
  820. data/lib/repull/models/withdraw_conversation_preapproval200_response.rb +1 -1
  821. data/lib/repull/models/withdraw_conversation_special_offer200_response.rb +1 -1
  822. data/lib/repull/models/workspace.rb +14 -2
  823. data/lib/repull/version.rb +2 -2
  824. data/lib/repull.rb +15 -1
  825. data/openapi/v1.json +666 -56
  826. metadata +15 -1
@@ -1,7 +1,7 @@
1
1
  =begin
2
2
  #Repull API
3
3
 
4
- #The unified API for vacation rental tech. Connect Airbnb, Booking.com, Vrbo and more channels, plus 14 PMS platforms, through one REST API. ## Designed for AI agents Every error response on this API includes machine-parseable fields so an LLM (Claude in MCP, Cursor, Cline, GPT, etc.) can self-recover without escalating to a human: - `error.code` — stable string identifier (e.g. `invalid_params`, `rate_limit_exceeded`) - `error.message` — human-readable cause - `error.fix` — exact recovery steps (e.g. \"Pass `check_in_after` as ISO 8601: `?check_in_after=2026-01-15`\") - `error.docs_url` — link to the canonical write-up at `https://repull.dev/docs/errors/{code}` - `error.request_id` — id to correlate with server-side logs - `error.field` / `error.value_received` / `error.valid_values` / `error.did_you_mean` — when the error is parameter-specific - `error.retry_after` — seconds to wait before retrying (rate-limit + transient upstream) `Access-Control-Expose-Headers` lists `x-request-id` and the `X-RateLimit-*` family so browsers can read them on cross-origin responses. ## Quick Start 1. Get an API key at https://repull.dev/dashboard 2. Connect a PMS: `POST /v1/connect/{provider}` 3. List properties: `GET /v1/properties` 4. Get reservations: `GET /v1/reservations` ## Authentication All requests require a Bearer token: ``` Authorization: Bearer sk_live_YOUR_API_KEY ``` ## Request Correlation (X-Request-ID) Every response carries an `X-Request-ID` header, e.g. `X-Request-ID: req_01HXY...`. Include this id in support tickets and bug reports — we can trace the full request lifecycle (auth, rate limit, handler, downstream calls, log row) from a single id. You may set the header on the inbound request to forward your own trace id; we will echo it back instead of generating a new one. Accepted format: `^[\\\\w.-]{1,128}$`. The id is also embedded in error envelopes as `request_id` so server-side log diffs work even when the response headers are stripped by an intermediate proxy. ## Rate Limits The public API enforces a per-API-key sliding-window rate limit on top of the per-tier monthly + daily-AI quotas. **Default policy:** 600 requests per 60 seconds, per API key. Sliding window — there is no fixed-minute boundary you can burst across. Every response includes: | Header | Meaning | |---|---| | `X-RateLimit-Limit` | Requests permitted in the current window. | | `X-RateLimit-Remaining` | Requests left in the current window after this call. | | `X-RateLimit-Reset` | Unix epoch (seconds) when the next slot opens. | | `X-RateLimit-Policy` | Machine-readable policy descriptor, e.g. `600;w=60`. | | `Retry-After` | Seconds to wait before retrying. **Only present on 429 responses.** | **On 429 (rate_limit_exceeded):** the response body matches the standard error envelope with `code: \"rate_limit_exceeded\"`, plus `limit`, `window_seconds`, `retry_after`, and `request_id` fields. SDKs MUST honor `Retry-After` and use exponential backoff with jitter on subsequent retries — never a tight loop. Recommended backoff: ``` sleep_ms = (Retry-After * 1000) + random(0..250) ``` Monthly + daily-AI tier quotas (`free`, `starter`, `custom`) are enforced separately and also surface as 429s; they include `tier`, `scope`, `limit`, `used` and `resets_at` fields. **The way past a request quota.** The monthly quota refusal (`429 rate_limit_exceeded` with `scope: \"monthly\"`), `402 credits_exhausted` and `429 daily_limit_exceeded` also carry `upgrade` (the cheapest plan that covers your usage: its exact monthly price for your listings, its request quotas and a `checkout_url` that opens checkout for that price; `plan: \"custom\"` with a `contact_email` when no self-serve plan covers it), `credits` (pay-as-you-go: `usd_per_1000_requests`, `top_up_url`, your `balance_usd`), `resets_at` and `projected_monthly_requests`. The per-minute 429 (`scope: \"per_api_key\"`) carries none of these: wait `Retry-After`. ## Plan listing limits Each plan includes a number of **active listings**: | Tier | Active listings | |---|---| | `free` | 3 | | `starter` | no cap: 10 included, then billed per listing | | `custom` | no cap | Going over the plan never blocks your API calls. Listings beyond the plan are **held back**: they stay connected and keep syncing, but they are not served. A held-back listing answers `403 listing_inactive` with `reason: \"plan_limit\"`, and collection routes leave it out. Every JSON response then carries a `planNotice` and the `X-Repull-Listings-Held-Back` header, so you know there is more to see. Choose which listings are active with `POST /v1/listings/status`, or upgrade at `https://repull.dev/dashboard/billing` to activate them all. Only a call that would itself take you over the plan is refused, with **`402 listings_limit_exceeded`**: activating listings (`PATCH /v1/listings/{id}` with `{ \"active\": true }`, `POST /v1/listings/status`) or creating one (`POST /v1/listings`). Nothing else changes. The envelope carries the tier, the limit, the active count and an upgrade link next to the standard `code` / `message` / `fix` / `docs_url` / `request_id`. If an account has more active listings than its plan (for example after a downgrade), calls are still served and `planNotice` says so (code \"listings_over_plan\").
4
+ #The unified API for vacation rental tech. Connect Airbnb, Booking.com, Vrbo and more channels, plus 14 PMS platforms, through one REST API. ## Designed for AI agents Every error response on this API includes machine-parseable fields so an LLM (Claude in MCP, Cursor, Cline, GPT, etc.) can self-recover without escalating to a human: - `error.code` — stable string identifier (e.g. `invalid_params`, `rate_limit_exceeded`) - `error.message` — human-readable cause - `error.fix` — exact recovery steps (e.g. \"Pass `check_in_after` as ISO 8601: `?check_in_after=2026-01-15`\") - `error.docs_url` — link to the canonical write-up at `https://repull.dev/docs/errors/{code}` - `error.request_id` — id to correlate with server-side logs - `error.field` / `error.value_received` / `error.valid_values` / `error.did_you_mean` — when the error is parameter-specific - `error.retry_after` — seconds to wait before retrying (rate-limit + transient upstream) `Access-Control-Expose-Headers` lists `x-request-id` and the `X-RateLimit-*` family so browsers can read them on cross-origin responses. ## Quick Start 1. Get an API key at https://repull.dev/dashboard 2. Connect a PMS: `POST /v1/connect/{provider}` 3. List properties: `GET /v1/properties` 4. Get reservations: `GET /v1/reservations` ## Authentication All requests require a Bearer token: ``` Authorization: Bearer sk_live_YOUR_API_KEY ``` ## Request Correlation (X-Request-ID) Every response carries an `X-Request-ID` header, e.g. `X-Request-ID: req_01HXY...`. Include this id in support tickets and bug reports — we can trace the full request lifecycle (auth, rate limit, handler, downstream calls, log row) from a single id. You may set the header on the inbound request to forward your own trace id; we will echo it back instead of generating a new one. Accepted format: `^[\\\\w.-]{1,128}$`. The id is also embedded in error envelopes as `request_id` so server-side log diffs work even when the response headers are stripped by an intermediate proxy. ## Rate Limits The public API enforces a per-API-key sliding-window rate limit on top of the per-tier monthly + daily-AI quotas. **Default policy:** 600 requests per 60 seconds, per API key. Sliding window — there is no fixed-minute boundary you can burst across. Every response includes: | Header | Meaning | |---|---| | `X-RateLimit-Limit` | Requests permitted in the current window. | | `X-RateLimit-Remaining` | Requests left in the current window after this call. | | `X-RateLimit-Reset` | Unix epoch (seconds) when the next slot opens. | | `X-RateLimit-Policy` | Machine-readable policy descriptor, e.g. `600;w=60`. | | `Retry-After` | Seconds to wait before retrying. **Only present on 429 responses.** | **On 429 (rate_limit_exceeded):** the response body matches the standard error envelope with `code: \"rate_limit_exceeded\"`, plus `limit`, `window_seconds`, `retry_after`, and `request_id` fields. SDKs MUST honor `Retry-After` and use exponential backoff with jitter on subsequent retries — never a tight loop. Recommended backoff: ``` sleep_ms = (Retry-After * 1000) + random(0..250) ``` Monthly + daily-AI tier quotas (`free`, `starter`, `custom`) are enforced separately and also surface as 429s; they include `tier`, `scope`, `limit`, `used` and `resets_at` fields. **The way past a request quota.** The monthly quota refusal (`429 rate_limit_exceeded` with `scope: \"monthly\"`), `402 credits_exhausted` and `429 daily_limit_exceeded` also carry `upgrade` (the cheapest plan that covers your usage: its exact monthly price for your listings, its request quotas and a `checkout_url` that opens checkout for that price; `plan: \"custom\"` with a `contact_email` when no self-serve plan covers it), `credits` (pay-as-you-go: `usd_per_1000_requests`, `top_up_url`, your `balance_usd`), `resets_at` and `projected_monthly_requests`. The per-minute 429 (`scope: \"per_api_key\"`) carries none of these: wait `Retry-After`. ## Plan listing limits Each plan includes a number of **active listings**: | Tier | Active listings | |---|---| | `free` | 3 | | `starter` | no cap: 10 included, then billed per listing | | `custom` | no cap | Going over the plan never blocks your API calls. Listings beyond the plan are **held back**: they stay connected and keep syncing, but they are not served. A held-back listing answers `403 listing_inactive` with `reason: \"plan_limit\"`, and collection routes leave it out. Every JSON response then carries a `planNotice` and the `X-Repull-Listings-Held-Back` header, so you know there is more to see. Choose which listings are active with `POST /v1/listings/status`. Upgrading at `https://repull.dev/dashboard/billing` lifts the cap but does not switch held-back listings on: you choose which to activate afterwards, with the same call or from the dashboard, and each one you switch on is billed from then. Only a call that would itself take you over the plan is refused, with **`402 listings_limit_exceeded`**: activating listings (`PATCH /v1/listings/{id}` with `{ \"active\": true }`, `POST /v1/listings/status`) or creating one (`POST /v1/listings`). Nothing else changes. The envelope carries the tier, the limit, the active count and an upgrade link next to the standard `code` / `message` / `fix` / `docs_url` / `request_id`. If an account has more active listings than its plan (for example after a downgrade), calls are still served and `planNotice` says so (code \"listings_over_plan\"). ## Failed payments If your plan's renewal payment fails, nothing is blocked: your API calls keep working while Stripe retries the card. Every successful JSON response then carries a `billingNotice` (code `payment_failed`) with the amount, when it failed, the next automatic retry (`nextRetryAt`) and `payUrl`, the invoice to pay. It disappears once the invoice is paid.
5
5
 
6
6
  The version of the OpenAPI document: 1.0.0
7
7
 
@@ -23,8 +23,15 @@ module Repull
23
23
 
24
24
  attr_accessor :min_nights
25
25
 
26
+ # Maximum stay for an arrival on these dates. Sent to Airbnb and Booking.com. Vrbo has no per-date maximum stay, so it is not sent there.
26
27
  attr_accessor :max_nights
27
28
 
29
+ # No check-in on these dates (`true`), or check-in allowed again (`false`). Sent to Airbnb, Booking.com and Vrbo. Leaving it out keeps the current value.
30
+ attr_accessor :closed_to_arrival
31
+
32
+ # No check-out on these dates (`true`), or check-out allowed again (`false`). Sent to Airbnb, Booking.com and Vrbo. Leaving it out keeps the current value.
33
+ attr_accessor :closed_to_departure
34
+
28
35
  # Rooms to sell on these dates, for a listing that sells several identical rooms (`unitCount` > 1, e.g. a Booking.com room type). Up to the listing's `unitCount`. Refused with `409 managed_by_pms` on a hotel PMS room type (Cloudbeds, Mews) — its PMS owns the room count.
29
36
  attr_accessor :available_units
30
37
 
@@ -38,6 +45,8 @@ module Repull
38
45
  :'price' => :'price',
39
46
  :'min_nights' => :'minNights',
40
47
  :'max_nights' => :'maxNights',
48
+ :'closed_to_arrival' => :'closedToArrival',
49
+ :'closed_to_departure' => :'closedToDeparture',
41
50
  :'available_units' => :'availableUnits',
42
51
  :'dates' => :'dates'
43
52
  }
@@ -60,6 +69,8 @@ module Repull
60
69
  :'price' => :'Float',
61
70
  :'min_nights' => :'Integer',
62
71
  :'max_nights' => :'Integer',
72
+ :'closed_to_arrival' => :'Boolean',
73
+ :'closed_to_departure' => :'Boolean',
63
74
  :'available_units' => :'Integer',
64
75
  :'dates' => :'Array<Date>'
65
76
  }
@@ -110,6 +121,14 @@ module Repull
110
121
  self.max_nights = attributes[:'max_nights']
111
122
  end
112
123
 
124
+ if attributes.key?(:'closed_to_arrival')
125
+ self.closed_to_arrival = attributes[:'closed_to_arrival']
126
+ end
127
+
128
+ if attributes.key?(:'closed_to_departure')
129
+ self.closed_to_departure = attributes[:'closed_to_departure']
130
+ end
131
+
113
132
  if attributes.key?(:'available_units')
114
133
  self.available_units = attributes[:'available_units']
115
134
  end
@@ -228,6 +247,8 @@ module Repull
228
247
  price == o.price &&
229
248
  min_nights == o.min_nights &&
230
249
  max_nights == o.max_nights &&
250
+ closed_to_arrival == o.closed_to_arrival &&
251
+ closed_to_departure == o.closed_to_departure &&
231
252
  available_units == o.available_units &&
232
253
  dates == o.dates
233
254
  end
@@ -241,7 +262,7 @@ module Repull
241
262
  # Calculates hash code according to all attributes.
242
263
  # @return [Integer] Hash code
243
264
  def hash
244
- [available, price, min_nights, max_nights, available_units, dates].hash
265
+ [available, price, min_nights, max_nights, closed_to_arrival, closed_to_departure, available_units, dates].hash
245
266
  end
246
267
 
247
268
  # Builds the object from hash
@@ -1,7 +1,7 @@
1
1
  =begin
2
2
  #Repull API
3
3
 
4
- #The unified API for vacation rental tech. Connect Airbnb, Booking.com, Vrbo and more channels, plus 14 PMS platforms, through one REST API. ## Designed for AI agents Every error response on this API includes machine-parseable fields so an LLM (Claude in MCP, Cursor, Cline, GPT, etc.) can self-recover without escalating to a human: - `error.code` — stable string identifier (e.g. `invalid_params`, `rate_limit_exceeded`) - `error.message` — human-readable cause - `error.fix` — exact recovery steps (e.g. \"Pass `check_in_after` as ISO 8601: `?check_in_after=2026-01-15`\") - `error.docs_url` — link to the canonical write-up at `https://repull.dev/docs/errors/{code}` - `error.request_id` — id to correlate with server-side logs - `error.field` / `error.value_received` / `error.valid_values` / `error.did_you_mean` — when the error is parameter-specific - `error.retry_after` — seconds to wait before retrying (rate-limit + transient upstream) `Access-Control-Expose-Headers` lists `x-request-id` and the `X-RateLimit-*` family so browsers can read them on cross-origin responses. ## Quick Start 1. Get an API key at https://repull.dev/dashboard 2. Connect a PMS: `POST /v1/connect/{provider}` 3. List properties: `GET /v1/properties` 4. Get reservations: `GET /v1/reservations` ## Authentication All requests require a Bearer token: ``` Authorization: Bearer sk_live_YOUR_API_KEY ``` ## Request Correlation (X-Request-ID) Every response carries an `X-Request-ID` header, e.g. `X-Request-ID: req_01HXY...`. Include this id in support tickets and bug reports — we can trace the full request lifecycle (auth, rate limit, handler, downstream calls, log row) from a single id. You may set the header on the inbound request to forward your own trace id; we will echo it back instead of generating a new one. Accepted format: `^[\\\\w.-]{1,128}$`. The id is also embedded in error envelopes as `request_id` so server-side log diffs work even when the response headers are stripped by an intermediate proxy. ## Rate Limits The public API enforces a per-API-key sliding-window rate limit on top of the per-tier monthly + daily-AI quotas. **Default policy:** 600 requests per 60 seconds, per API key. Sliding window — there is no fixed-minute boundary you can burst across. Every response includes: | Header | Meaning | |---|---| | `X-RateLimit-Limit` | Requests permitted in the current window. | | `X-RateLimit-Remaining` | Requests left in the current window after this call. | | `X-RateLimit-Reset` | Unix epoch (seconds) when the next slot opens. | | `X-RateLimit-Policy` | Machine-readable policy descriptor, e.g. `600;w=60`. | | `Retry-After` | Seconds to wait before retrying. **Only present on 429 responses.** | **On 429 (rate_limit_exceeded):** the response body matches the standard error envelope with `code: \"rate_limit_exceeded\"`, plus `limit`, `window_seconds`, `retry_after`, and `request_id` fields. SDKs MUST honor `Retry-After` and use exponential backoff with jitter on subsequent retries — never a tight loop. Recommended backoff: ``` sleep_ms = (Retry-After * 1000) + random(0..250) ``` Monthly + daily-AI tier quotas (`free`, `starter`, `custom`) are enforced separately and also surface as 429s; they include `tier`, `scope`, `limit`, `used` and `resets_at` fields. **The way past a request quota.** The monthly quota refusal (`429 rate_limit_exceeded` with `scope: \"monthly\"`), `402 credits_exhausted` and `429 daily_limit_exceeded` also carry `upgrade` (the cheapest plan that covers your usage: its exact monthly price for your listings, its request quotas and a `checkout_url` that opens checkout for that price; `plan: \"custom\"` with a `contact_email` when no self-serve plan covers it), `credits` (pay-as-you-go: `usd_per_1000_requests`, `top_up_url`, your `balance_usd`), `resets_at` and `projected_monthly_requests`. The per-minute 429 (`scope: \"per_api_key\"`) carries none of these: wait `Retry-After`. ## Plan listing limits Each plan includes a number of **active listings**: | Tier | Active listings | |---|---| | `free` | 3 | | `starter` | no cap: 10 included, then billed per listing | | `custom` | no cap | Going over the plan never blocks your API calls. Listings beyond the plan are **held back**: they stay connected and keep syncing, but they are not served. A held-back listing answers `403 listing_inactive` with `reason: \"plan_limit\"`, and collection routes leave it out. Every JSON response then carries a `planNotice` and the `X-Repull-Listings-Held-Back` header, so you know there is more to see. Choose which listings are active with `POST /v1/listings/status`, or upgrade at `https://repull.dev/dashboard/billing` to activate them all. Only a call that would itself take you over the plan is refused, with **`402 listings_limit_exceeded`**: activating listings (`PATCH /v1/listings/{id}` with `{ \"active\": true }`, `POST /v1/listings/status`) or creating one (`POST /v1/listings`). Nothing else changes. The envelope carries the tier, the limit, the active count and an upgrade link next to the standard `code` / `message` / `fix` / `docs_url` / `request_id`. If an account has more active listings than its plan (for example after a downgrade), calls are still served and `planNotice` says so (code \"listings_over_plan\").
4
+ #The unified API for vacation rental tech. Connect Airbnb, Booking.com, Vrbo and more channels, plus 14 PMS platforms, through one REST API. ## Designed for AI agents Every error response on this API includes machine-parseable fields so an LLM (Claude in MCP, Cursor, Cline, GPT, etc.) can self-recover without escalating to a human: - `error.code` — stable string identifier (e.g. `invalid_params`, `rate_limit_exceeded`) - `error.message` — human-readable cause - `error.fix` — exact recovery steps (e.g. \"Pass `check_in_after` as ISO 8601: `?check_in_after=2026-01-15`\") - `error.docs_url` — link to the canonical write-up at `https://repull.dev/docs/errors/{code}` - `error.request_id` — id to correlate with server-side logs - `error.field` / `error.value_received` / `error.valid_values` / `error.did_you_mean` — when the error is parameter-specific - `error.retry_after` — seconds to wait before retrying (rate-limit + transient upstream) `Access-Control-Expose-Headers` lists `x-request-id` and the `X-RateLimit-*` family so browsers can read them on cross-origin responses. ## Quick Start 1. Get an API key at https://repull.dev/dashboard 2. Connect a PMS: `POST /v1/connect/{provider}` 3. List properties: `GET /v1/properties` 4. Get reservations: `GET /v1/reservations` ## Authentication All requests require a Bearer token: ``` Authorization: Bearer sk_live_YOUR_API_KEY ``` ## Request Correlation (X-Request-ID) Every response carries an `X-Request-ID` header, e.g. `X-Request-ID: req_01HXY...`. Include this id in support tickets and bug reports — we can trace the full request lifecycle (auth, rate limit, handler, downstream calls, log row) from a single id. You may set the header on the inbound request to forward your own trace id; we will echo it back instead of generating a new one. Accepted format: `^[\\\\w.-]{1,128}$`. The id is also embedded in error envelopes as `request_id` so server-side log diffs work even when the response headers are stripped by an intermediate proxy. ## Rate Limits The public API enforces a per-API-key sliding-window rate limit on top of the per-tier monthly + daily-AI quotas. **Default policy:** 600 requests per 60 seconds, per API key. Sliding window — there is no fixed-minute boundary you can burst across. Every response includes: | Header | Meaning | |---|---| | `X-RateLimit-Limit` | Requests permitted in the current window. | | `X-RateLimit-Remaining` | Requests left in the current window after this call. | | `X-RateLimit-Reset` | Unix epoch (seconds) when the next slot opens. | | `X-RateLimit-Policy` | Machine-readable policy descriptor, e.g. `600;w=60`. | | `Retry-After` | Seconds to wait before retrying. **Only present on 429 responses.** | **On 429 (rate_limit_exceeded):** the response body matches the standard error envelope with `code: \"rate_limit_exceeded\"`, plus `limit`, `window_seconds`, `retry_after`, and `request_id` fields. SDKs MUST honor `Retry-After` and use exponential backoff with jitter on subsequent retries — never a tight loop. Recommended backoff: ``` sleep_ms = (Retry-After * 1000) + random(0..250) ``` Monthly + daily-AI tier quotas (`free`, `starter`, `custom`) are enforced separately and also surface as 429s; they include `tier`, `scope`, `limit`, `used` and `resets_at` fields. **The way past a request quota.** The monthly quota refusal (`429 rate_limit_exceeded` with `scope: \"monthly\"`), `402 credits_exhausted` and `429 daily_limit_exceeded` also carry `upgrade` (the cheapest plan that covers your usage: its exact monthly price for your listings, its request quotas and a `checkout_url` that opens checkout for that price; `plan: \"custom\"` with a `contact_email` when no self-serve plan covers it), `credits` (pay-as-you-go: `usd_per_1000_requests`, `top_up_url`, your `balance_usd`), `resets_at` and `projected_monthly_requests`. The per-minute 429 (`scope: \"per_api_key\"`) carries none of these: wait `Retry-After`. ## Plan listing limits Each plan includes a number of **active listings**: | Tier | Active listings | |---|---| | `free` | 3 | | `starter` | no cap: 10 included, then billed per listing | | `custom` | no cap | Going over the plan never blocks your API calls. Listings beyond the plan are **held back**: they stay connected and keep syncing, but they are not served. A held-back listing answers `403 listing_inactive` with `reason: \"plan_limit\"`, and collection routes leave it out. Every JSON response then carries a `planNotice` and the `X-Repull-Listings-Held-Back` header, so you know there is more to see. Choose which listings are active with `POST /v1/listings/status`. Upgrading at `https://repull.dev/dashboard/billing` lifts the cap but does not switch held-back listings on: you choose which to activate afterwards, with the same call or from the dashboard, and each one you switch on is billed from then. Only a call that would itself take you over the plan is refused, with **`402 listings_limit_exceeded`**: activating listings (`PATCH /v1/listings/{id}` with `{ \"active\": true }`, `POST /v1/listings/status`) or creating one (`POST /v1/listings`). Nothing else changes. The envelope carries the tier, the limit, the active count and an upgrade link next to the standard `code` / `message` / `fix` / `docs_url` / `request_id`. If an account has more active listings than its plan (for example after a downgrade), calls are still served and `planNotice` says so (code \"listings_over_plan\"). ## Failed payments If your plan's renewal payment fails, nothing is blocked: your API calls keep working while Stripe retries the card. Every successful JSON response then carries a `billingNotice` (code `payment_failed`) with the amount, when it failed, the next automatic retry (`nextRetryAt`) and `payUrl`, the invoice to pay. It disappears once the invoice is paid.
5
5
 
6
6
  The version of the OpenAPI document: 1.0.0
7
7
 
@@ -1,7 +1,7 @@
1
1
  =begin
2
2
  #Repull API
3
3
 
4
- #The unified API for vacation rental tech. Connect Airbnb, Booking.com, Vrbo and more channels, plus 14 PMS platforms, through one REST API. ## Designed for AI agents Every error response on this API includes machine-parseable fields so an LLM (Claude in MCP, Cursor, Cline, GPT, etc.) can self-recover without escalating to a human: - `error.code` — stable string identifier (e.g. `invalid_params`, `rate_limit_exceeded`) - `error.message` — human-readable cause - `error.fix` — exact recovery steps (e.g. \"Pass `check_in_after` as ISO 8601: `?check_in_after=2026-01-15`\") - `error.docs_url` — link to the canonical write-up at `https://repull.dev/docs/errors/{code}` - `error.request_id` — id to correlate with server-side logs - `error.field` / `error.value_received` / `error.valid_values` / `error.did_you_mean` — when the error is parameter-specific - `error.retry_after` — seconds to wait before retrying (rate-limit + transient upstream) `Access-Control-Expose-Headers` lists `x-request-id` and the `X-RateLimit-*` family so browsers can read them on cross-origin responses. ## Quick Start 1. Get an API key at https://repull.dev/dashboard 2. Connect a PMS: `POST /v1/connect/{provider}` 3. List properties: `GET /v1/properties` 4. Get reservations: `GET /v1/reservations` ## Authentication All requests require a Bearer token: ``` Authorization: Bearer sk_live_YOUR_API_KEY ``` ## Request Correlation (X-Request-ID) Every response carries an `X-Request-ID` header, e.g. `X-Request-ID: req_01HXY...`. Include this id in support tickets and bug reports — we can trace the full request lifecycle (auth, rate limit, handler, downstream calls, log row) from a single id. You may set the header on the inbound request to forward your own trace id; we will echo it back instead of generating a new one. Accepted format: `^[\\\\w.-]{1,128}$`. The id is also embedded in error envelopes as `request_id` so server-side log diffs work even when the response headers are stripped by an intermediate proxy. ## Rate Limits The public API enforces a per-API-key sliding-window rate limit on top of the per-tier monthly + daily-AI quotas. **Default policy:** 600 requests per 60 seconds, per API key. Sliding window — there is no fixed-minute boundary you can burst across. Every response includes: | Header | Meaning | |---|---| | `X-RateLimit-Limit` | Requests permitted in the current window. | | `X-RateLimit-Remaining` | Requests left in the current window after this call. | | `X-RateLimit-Reset` | Unix epoch (seconds) when the next slot opens. | | `X-RateLimit-Policy` | Machine-readable policy descriptor, e.g. `600;w=60`. | | `Retry-After` | Seconds to wait before retrying. **Only present on 429 responses.** | **On 429 (rate_limit_exceeded):** the response body matches the standard error envelope with `code: \"rate_limit_exceeded\"`, plus `limit`, `window_seconds`, `retry_after`, and `request_id` fields. SDKs MUST honor `Retry-After` and use exponential backoff with jitter on subsequent retries — never a tight loop. Recommended backoff: ``` sleep_ms = (Retry-After * 1000) + random(0..250) ``` Monthly + daily-AI tier quotas (`free`, `starter`, `custom`) are enforced separately and also surface as 429s; they include `tier`, `scope`, `limit`, `used` and `resets_at` fields. **The way past a request quota.** The monthly quota refusal (`429 rate_limit_exceeded` with `scope: \"monthly\"`), `402 credits_exhausted` and `429 daily_limit_exceeded` also carry `upgrade` (the cheapest plan that covers your usage: its exact monthly price for your listings, its request quotas and a `checkout_url` that opens checkout for that price; `plan: \"custom\"` with a `contact_email` when no self-serve plan covers it), `credits` (pay-as-you-go: `usd_per_1000_requests`, `top_up_url`, your `balance_usd`), `resets_at` and `projected_monthly_requests`. The per-minute 429 (`scope: \"per_api_key\"`) carries none of these: wait `Retry-After`. ## Plan listing limits Each plan includes a number of **active listings**: | Tier | Active listings | |---|---| | `free` | 3 | | `starter` | no cap: 10 included, then billed per listing | | `custom` | no cap | Going over the plan never blocks your API calls. Listings beyond the plan are **held back**: they stay connected and keep syncing, but they are not served. A held-back listing answers `403 listing_inactive` with `reason: \"plan_limit\"`, and collection routes leave it out. Every JSON response then carries a `planNotice` and the `X-Repull-Listings-Held-Back` header, so you know there is more to see. Choose which listings are active with `POST /v1/listings/status`, or upgrade at `https://repull.dev/dashboard/billing` to activate them all. Only a call that would itself take you over the plan is refused, with **`402 listings_limit_exceeded`**: activating listings (`PATCH /v1/listings/{id}` with `{ \"active\": true }`, `POST /v1/listings/status`) or creating one (`POST /v1/listings`). Nothing else changes. The envelope carries the tier, the limit, the active count and an upgrade link next to the standard `code` / `message` / `fix` / `docs_url` / `request_id`. If an account has more active listings than its plan (for example after a downgrade), calls are still served and `planNotice` says so (code \"listings_over_plan\").
4
+ #The unified API for vacation rental tech. Connect Airbnb, Booking.com, Vrbo and more channels, plus 14 PMS platforms, through one REST API. ## Designed for AI agents Every error response on this API includes machine-parseable fields so an LLM (Claude in MCP, Cursor, Cline, GPT, etc.) can self-recover without escalating to a human: - `error.code` — stable string identifier (e.g. `invalid_params`, `rate_limit_exceeded`) - `error.message` — human-readable cause - `error.fix` — exact recovery steps (e.g. \"Pass `check_in_after` as ISO 8601: `?check_in_after=2026-01-15`\") - `error.docs_url` — link to the canonical write-up at `https://repull.dev/docs/errors/{code}` - `error.request_id` — id to correlate with server-side logs - `error.field` / `error.value_received` / `error.valid_values` / `error.did_you_mean` — when the error is parameter-specific - `error.retry_after` — seconds to wait before retrying (rate-limit + transient upstream) `Access-Control-Expose-Headers` lists `x-request-id` and the `X-RateLimit-*` family so browsers can read them on cross-origin responses. ## Quick Start 1. Get an API key at https://repull.dev/dashboard 2. Connect a PMS: `POST /v1/connect/{provider}` 3. List properties: `GET /v1/properties` 4. Get reservations: `GET /v1/reservations` ## Authentication All requests require a Bearer token: ``` Authorization: Bearer sk_live_YOUR_API_KEY ``` ## Request Correlation (X-Request-ID) Every response carries an `X-Request-ID` header, e.g. `X-Request-ID: req_01HXY...`. Include this id in support tickets and bug reports — we can trace the full request lifecycle (auth, rate limit, handler, downstream calls, log row) from a single id. You may set the header on the inbound request to forward your own trace id; we will echo it back instead of generating a new one. Accepted format: `^[\\\\w.-]{1,128}$`. The id is also embedded in error envelopes as `request_id` so server-side log diffs work even when the response headers are stripped by an intermediate proxy. ## Rate Limits The public API enforces a per-API-key sliding-window rate limit on top of the per-tier monthly + daily-AI quotas. **Default policy:** 600 requests per 60 seconds, per API key. Sliding window — there is no fixed-minute boundary you can burst across. Every response includes: | Header | Meaning | |---|---| | `X-RateLimit-Limit` | Requests permitted in the current window. | | `X-RateLimit-Remaining` | Requests left in the current window after this call. | | `X-RateLimit-Reset` | Unix epoch (seconds) when the next slot opens. | | `X-RateLimit-Policy` | Machine-readable policy descriptor, e.g. `600;w=60`. | | `Retry-After` | Seconds to wait before retrying. **Only present on 429 responses.** | **On 429 (rate_limit_exceeded):** the response body matches the standard error envelope with `code: \"rate_limit_exceeded\"`, plus `limit`, `window_seconds`, `retry_after`, and `request_id` fields. SDKs MUST honor `Retry-After` and use exponential backoff with jitter on subsequent retries — never a tight loop. Recommended backoff: ``` sleep_ms = (Retry-After * 1000) + random(0..250) ``` Monthly + daily-AI tier quotas (`free`, `starter`, `custom`) are enforced separately and also surface as 429s; they include `tier`, `scope`, `limit`, `used` and `resets_at` fields. **The way past a request quota.** The monthly quota refusal (`429 rate_limit_exceeded` with `scope: \"monthly\"`), `402 credits_exhausted` and `429 daily_limit_exceeded` also carry `upgrade` (the cheapest plan that covers your usage: its exact monthly price for your listings, its request quotas and a `checkout_url` that opens checkout for that price; `plan: \"custom\"` with a `contact_email` when no self-serve plan covers it), `credits` (pay-as-you-go: `usd_per_1000_requests`, `top_up_url`, your `balance_usd`), `resets_at` and `projected_monthly_requests`. The per-minute 429 (`scope: \"per_api_key\"`) carries none of these: wait `Retry-After`. ## Plan listing limits Each plan includes a number of **active listings**: | Tier | Active listings | |---|---| | `free` | 3 | | `starter` | no cap: 10 included, then billed per listing | | `custom` | no cap | Going over the plan never blocks your API calls. Listings beyond the plan are **held back**: they stay connected and keep syncing, but they are not served. A held-back listing answers `403 listing_inactive` with `reason: \"plan_limit\"`, and collection routes leave it out. Every JSON response then carries a `planNotice` and the `X-Repull-Listings-Held-Back` header, so you know there is more to see. Choose which listings are active with `POST /v1/listings/status`. Upgrading at `https://repull.dev/dashboard/billing` lifts the cap but does not switch held-back listings on: you choose which to activate afterwards, with the same call or from the dashboard, and each one you switch on is billed from then. Only a call that would itself take you over the plan is refused, with **`402 listings_limit_exceeded`**: activating listings (`PATCH /v1/listings/{id}` with `{ \"active\": true }`, `POST /v1/listings/status`) or creating one (`POST /v1/listings`). Nothing else changes. The envelope carries the tier, the limit, the active count and an upgrade link next to the standard `code` / `message` / `fix` / `docs_url` / `request_id`. If an account has more active listings than its plan (for example after a downgrade), calls are still served and `planNotice` says so (code \"listings_over_plan\"). ## Failed payments If your plan's renewal payment fails, nothing is blocked: your API calls keep working while Stripe retries the card. Every successful JSON response then carries a `billingNotice` (code `payment_failed`) with the amount, when it failed, the next automatic retry (`nextRetryAt`) and `payUrl`, the invoice to pay. It disappears once the invoice is paid.
5
5
 
6
6
  The version of the OpenAPI document: 1.0.0
7
7
 
@@ -25,13 +25,17 @@ module Repull
25
25
  # Channels whose token has expired — these need reconnecting, not retrying.
26
26
  attr_accessor :auth_errors
27
27
 
28
+ # One entry per listing per connected channel: which channel took the write and which refused it.
29
+ attr_accessor :channels
30
+
28
31
  # Attribute mapping from ruby-style variable name to JSON key.
29
32
  def self.attribute_map
30
33
  {
31
34
  :'attempted' => :'attempted',
32
35
  :'succeeded' => :'succeeded',
33
36
  :'failed' => :'failed',
34
- :'auth_errors' => :'authErrors'
37
+ :'auth_errors' => :'authErrors',
38
+ :'channels' => :'channels'
35
39
  }
36
40
  end
37
41
 
@@ -51,7 +55,8 @@ module Repull
51
55
  :'attempted' => :'Integer',
52
56
  :'succeeded' => :'Integer',
53
57
  :'failed' => :'Integer',
54
- :'auth_errors' => :'Integer'
58
+ :'auth_errors' => :'Integer',
59
+ :'channels' => :'Array<AvailabilityWriteResultSyncedChannelsInner>'
55
60
  }
56
61
  end
57
62
 
@@ -92,6 +97,12 @@ module Repull
92
97
  if attributes.key?(:'auth_errors')
93
98
  self.auth_errors = attributes[:'auth_errors']
94
99
  end
100
+
101
+ if attributes.key?(:'channels')
102
+ if (value = attributes[:'channels']).is_a?(Array)
103
+ self.channels = value
104
+ end
105
+ end
95
106
  end
96
107
 
97
108
  # Show invalid properties with the reasons. Usually used together with valid?
@@ -117,7 +128,8 @@ module Repull
117
128
  attempted == o.attempted &&
118
129
  succeeded == o.succeeded &&
119
130
  failed == o.failed &&
120
- auth_errors == o.auth_errors
131
+ auth_errors == o.auth_errors &&
132
+ channels == o.channels
121
133
  end
122
134
 
123
135
  # @see the `==` method
@@ -129,7 +141,7 @@ module Repull
129
141
  # Calculates hash code according to all attributes.
130
142
  # @return [Integer] Hash code
131
143
  def hash
132
- [attempted, succeeded, failed, auth_errors].hash
144
+ [attempted, succeeded, failed, auth_errors, channels].hash
133
145
  end
134
146
 
135
147
  # Builds the object from hash
@@ -0,0 +1,232 @@
1
+ =begin
2
+ #Repull API
3
+
4
+ #The unified API for vacation rental tech. Connect Airbnb, Booking.com, Vrbo and more channels, plus 14 PMS platforms, through one REST API. ## Designed for AI agents Every error response on this API includes machine-parseable fields so an LLM (Claude in MCP, Cursor, Cline, GPT, etc.) can self-recover without escalating to a human: - `error.code` — stable string identifier (e.g. `invalid_params`, `rate_limit_exceeded`) - `error.message` — human-readable cause - `error.fix` — exact recovery steps (e.g. \"Pass `check_in_after` as ISO 8601: `?check_in_after=2026-01-15`\") - `error.docs_url` — link to the canonical write-up at `https://repull.dev/docs/errors/{code}` - `error.request_id` — id to correlate with server-side logs - `error.field` / `error.value_received` / `error.valid_values` / `error.did_you_mean` — when the error is parameter-specific - `error.retry_after` — seconds to wait before retrying (rate-limit + transient upstream) `Access-Control-Expose-Headers` lists `x-request-id` and the `X-RateLimit-*` family so browsers can read them on cross-origin responses. ## Quick Start 1. Get an API key at https://repull.dev/dashboard 2. Connect a PMS: `POST /v1/connect/{provider}` 3. List properties: `GET /v1/properties` 4. Get reservations: `GET /v1/reservations` ## Authentication All requests require a Bearer token: ``` Authorization: Bearer sk_live_YOUR_API_KEY ``` ## Request Correlation (X-Request-ID) Every response carries an `X-Request-ID` header, e.g. `X-Request-ID: req_01HXY...`. Include this id in support tickets and bug reports — we can trace the full request lifecycle (auth, rate limit, handler, downstream calls, log row) from a single id. You may set the header on the inbound request to forward your own trace id; we will echo it back instead of generating a new one. Accepted format: `^[\\\\w.-]{1,128}$`. The id is also embedded in error envelopes as `request_id` so server-side log diffs work even when the response headers are stripped by an intermediate proxy. ## Rate Limits The public API enforces a per-API-key sliding-window rate limit on top of the per-tier monthly + daily-AI quotas. **Default policy:** 600 requests per 60 seconds, per API key. Sliding window — there is no fixed-minute boundary you can burst across. Every response includes: | Header | Meaning | |---|---| | `X-RateLimit-Limit` | Requests permitted in the current window. | | `X-RateLimit-Remaining` | Requests left in the current window after this call. | | `X-RateLimit-Reset` | Unix epoch (seconds) when the next slot opens. | | `X-RateLimit-Policy` | Machine-readable policy descriptor, e.g. `600;w=60`. | | `Retry-After` | Seconds to wait before retrying. **Only present on 429 responses.** | **On 429 (rate_limit_exceeded):** the response body matches the standard error envelope with `code: \"rate_limit_exceeded\"`, plus `limit`, `window_seconds`, `retry_after`, and `request_id` fields. SDKs MUST honor `Retry-After` and use exponential backoff with jitter on subsequent retries — never a tight loop. Recommended backoff: ``` sleep_ms = (Retry-After * 1000) + random(0..250) ``` Monthly + daily-AI tier quotas (`free`, `starter`, `custom`) are enforced separately and also surface as 429s; they include `tier`, `scope`, `limit`, `used` and `resets_at` fields. **The way past a request quota.** The monthly quota refusal (`429 rate_limit_exceeded` with `scope: \"monthly\"`), `402 credits_exhausted` and `429 daily_limit_exceeded` also carry `upgrade` (the cheapest plan that covers your usage: its exact monthly price for your listings, its request quotas and a `checkout_url` that opens checkout for that price; `plan: \"custom\"` with a `contact_email` when no self-serve plan covers it), `credits` (pay-as-you-go: `usd_per_1000_requests`, `top_up_url`, your `balance_usd`), `resets_at` and `projected_monthly_requests`. The per-minute 429 (`scope: \"per_api_key\"`) carries none of these: wait `Retry-After`. ## Plan listing limits Each plan includes a number of **active listings**: | Tier | Active listings | |---|---| | `free` | 3 | | `starter` | no cap: 10 included, then billed per listing | | `custom` | no cap | Going over the plan never blocks your API calls. Listings beyond the plan are **held back**: they stay connected and keep syncing, but they are not served. A held-back listing answers `403 listing_inactive` with `reason: \"plan_limit\"`, and collection routes leave it out. Every JSON response then carries a `planNotice` and the `X-Repull-Listings-Held-Back` header, so you know there is more to see. Choose which listings are active with `POST /v1/listings/status`. Upgrading at `https://repull.dev/dashboard/billing` lifts the cap but does not switch held-back listings on: you choose which to activate afterwards, with the same call or from the dashboard, and each one you switch on is billed from then. Only a call that would itself take you over the plan is refused, with **`402 listings_limit_exceeded`**: activating listings (`PATCH /v1/listings/{id}` with `{ \"active\": true }`, `POST /v1/listings/status`) or creating one (`POST /v1/listings`). Nothing else changes. The envelope carries the tier, the limit, the active count and an upgrade link next to the standard `code` / `message` / `fix` / `docs_url` / `request_id`. If an account has more active listings than its plan (for example after a downgrade), calls are still served and `planNotice` says so (code \"listings_over_plan\"). ## Failed payments If your plan's renewal payment fails, nothing is blocked: your API calls keep working while Stripe retries the card. Every successful JSON response then carries a `billingNotice` (code `payment_failed`) with the amount, when it failed, the next automatic retry (`nextRetryAt`) and `payUrl`, the invoice to pay. It disappears once the invoice is paid.
5
+
6
+ The version of the OpenAPI document: 1.0.0
7
+
8
+ Generated by: https://openapi-generator.tech
9
+ Generator version: 7.22.0
10
+
11
+ =end
12
+
13
+ require 'date'
14
+ require 'time'
15
+
16
+ module Repull
17
+ class AvailabilityWriteResultSyncedChannelsInner < ApiModelBase
18
+ attr_accessor :listing_id
19
+
20
+ # `airbnb`, `booking`, `vrbo`, or another connected channel.
21
+ attr_accessor :channel
22
+
23
+ # The channel's own id for the listing or room.
24
+ attr_accessor :channel_listing_id
25
+
26
+ # `accepted`: the channel took the write in this request. `queued` (Vrbo): sent within minutes and read back; `GET /v1/listings/{id}/calendar-sync` shows the outcome. `failed`: the channel refused it; see `error`.
27
+ attr_accessor :status
28
+
29
+ attr_accessor :error
30
+
31
+ # True when the channel's authorization has expired: reconnect, don't retry.
32
+ attr_accessor :auth_error
33
+
34
+ class EnumAttributeValidator
35
+ attr_reader :datatype
36
+ attr_reader :allowable_values
37
+
38
+ def initialize(datatype, allowable_values)
39
+ @allowable_values = allowable_values.map do |value|
40
+ case datatype.to_s
41
+ when /Integer/i
42
+ value.to_i
43
+ when /Float/i
44
+ value.to_f
45
+ else
46
+ value
47
+ end
48
+ end
49
+ end
50
+
51
+ def valid?(value)
52
+ !value || allowable_values.include?(value)
53
+ end
54
+ end
55
+
56
+ # Attribute mapping from ruby-style variable name to JSON key.
57
+ def self.attribute_map
58
+ {
59
+ :'listing_id' => :'listingId',
60
+ :'channel' => :'channel',
61
+ :'channel_listing_id' => :'channelListingId',
62
+ :'status' => :'status',
63
+ :'error' => :'error',
64
+ :'auth_error' => :'authError'
65
+ }
66
+ end
67
+
68
+ # Returns attribute mapping this model knows about
69
+ def self.acceptable_attribute_map
70
+ attribute_map
71
+ end
72
+
73
+ # Returns all the JSON keys this model knows about
74
+ def self.acceptable_attributes
75
+ acceptable_attribute_map.values
76
+ end
77
+
78
+ # Attribute type mapping.
79
+ def self.openapi_types
80
+ {
81
+ :'listing_id' => :'String',
82
+ :'channel' => :'String',
83
+ :'channel_listing_id' => :'String',
84
+ :'status' => :'String',
85
+ :'error' => :'String',
86
+ :'auth_error' => :'Boolean'
87
+ }
88
+ end
89
+
90
+ # List of attributes with nullable: true
91
+ def self.openapi_nullable
92
+ Set.new([
93
+ :'channel_listing_id',
94
+ :'error',
95
+ ])
96
+ end
97
+
98
+ # Initializes the object
99
+ # @param [Hash] attributes Model attributes in the form of hash
100
+ def initialize(attributes = {})
101
+ if (!attributes.is_a?(Hash))
102
+ fail ArgumentError, "The input argument (attributes) must be a hash in `Repull::AvailabilityWriteResultSyncedChannelsInner` initialize method"
103
+ end
104
+
105
+ # check to see if the attribute exists and convert string to symbol for hash key
106
+ acceptable_attribute_map = self.class.acceptable_attribute_map
107
+ attributes = attributes.each_with_object({}) { |(k, v), h|
108
+ if (!acceptable_attribute_map.key?(k.to_sym))
109
+ fail ArgumentError, "`#{k}` is not a valid attribute in `Repull::AvailabilityWriteResultSyncedChannelsInner`. Please check the name to make sure it's valid. List of attributes: " + acceptable_attribute_map.keys.inspect
110
+ end
111
+ h[k.to_sym] = v
112
+ }
113
+
114
+ if attributes.key?(:'listing_id')
115
+ self.listing_id = attributes[:'listing_id']
116
+ end
117
+
118
+ if attributes.key?(:'channel')
119
+ self.channel = attributes[:'channel']
120
+ end
121
+
122
+ if attributes.key?(:'channel_listing_id')
123
+ self.channel_listing_id = attributes[:'channel_listing_id']
124
+ end
125
+
126
+ if attributes.key?(:'status')
127
+ self.status = attributes[:'status']
128
+ end
129
+
130
+ if attributes.key?(:'error')
131
+ self.error = attributes[:'error']
132
+ end
133
+
134
+ if attributes.key?(:'auth_error')
135
+ self.auth_error = attributes[:'auth_error']
136
+ end
137
+ end
138
+
139
+ # Show invalid properties with the reasons. Usually used together with valid?
140
+ # @return Array for valid properties with the reasons
141
+ def list_invalid_properties
142
+ warn '[DEPRECATED] the `list_invalid_properties` method is obsolete'
143
+ invalid_properties = Array.new
144
+ invalid_properties
145
+ end
146
+
147
+ # Check to see if the all the properties in the model are valid
148
+ # @return true if the model is valid
149
+ def valid?
150
+ warn '[DEPRECATED] the `valid?` method is obsolete'
151
+ status_validator = EnumAttributeValidator.new('String', ["accepted", "queued", "failed"])
152
+ return false unless status_validator.valid?(@status)
153
+ true
154
+ end
155
+
156
+ # Custom attribute writer method checking allowed values (enum).
157
+ # @param [Object] status Object to be assigned
158
+ def status=(status)
159
+ validator = EnumAttributeValidator.new('String', ["accepted", "queued", "failed"])
160
+ unless validator.valid?(status)
161
+ fail ArgumentError, "invalid value for \"status\", must be one of #{validator.allowable_values}."
162
+ end
163
+ @status = status
164
+ end
165
+
166
+ # Checks equality by comparing each attribute.
167
+ # @param [Object] Object to be compared
168
+ def ==(o)
169
+ return true if self.equal?(o)
170
+ self.class == o.class &&
171
+ listing_id == o.listing_id &&
172
+ channel == o.channel &&
173
+ channel_listing_id == o.channel_listing_id &&
174
+ status == o.status &&
175
+ error == o.error &&
176
+ auth_error == o.auth_error
177
+ end
178
+
179
+ # @see the `==` method
180
+ # @param [Object] Object to be compared
181
+ def eql?(o)
182
+ self == o
183
+ end
184
+
185
+ # Calculates hash code according to all attributes.
186
+ # @return [Integer] Hash code
187
+ def hash
188
+ [listing_id, channel, channel_listing_id, status, error, auth_error].hash
189
+ end
190
+
191
+ # Builds the object from hash
192
+ # @param [Hash] attributes Model attributes in the form of hash
193
+ # @return [Object] Returns the model itself
194
+ def self.build_from_hash(attributes)
195
+ return nil unless attributes.is_a?(Hash)
196
+ attributes = attributes.transform_keys(&:to_sym)
197
+ transformed_hash = {}
198
+ openapi_types.each_pair do |key, type|
199
+ if attributes.key?(attribute_map[key]) && attributes[attribute_map[key]].nil?
200
+ transformed_hash["#{key}"] = nil
201
+ elsif type =~ /\AArray<(.*)>/i
202
+ # check to ensure the input is an array given that the attribute
203
+ # is documented as an array but the input is not
204
+ if attributes[attribute_map[key]].is_a?(Array)
205
+ transformed_hash["#{key}"] = attributes[attribute_map[key]].map { |v| _deserialize($1, v) }
206
+ end
207
+ elsif !attributes[attribute_map[key]].nil?
208
+ transformed_hash["#{key}"] = _deserialize(type, attributes[attribute_map[key]])
209
+ end
210
+ end
211
+ new(transformed_hash)
212
+ end
213
+
214
+ # Returns the object in the form of hash
215
+ # @return [Hash] Returns the object in the form of hash
216
+ def to_hash
217
+ hash = {}
218
+ self.class.attribute_map.each_pair do |attr, param|
219
+ value = self.send(attr)
220
+ if value.nil?
221
+ is_nullable = self.class.openapi_nullable.include?(attr)
222
+ next if !is_nullable || (is_nullable && !instance_variable_defined?(:"@#{attr}"))
223
+ end
224
+
225
+ hash[param] = _to_hash(value)
226
+ end
227
+ hash
228
+ end
229
+
230
+ end
231
+
232
+ end
@@ -1,7 +1,7 @@
1
1
  =begin
2
2
  #Repull API
3
3
 
4
- #The unified API for vacation rental tech. Connect Airbnb, Booking.com, Vrbo and more channels, plus 14 PMS platforms, through one REST API. ## Designed for AI agents Every error response on this API includes machine-parseable fields so an LLM (Claude in MCP, Cursor, Cline, GPT, etc.) can self-recover without escalating to a human: - `error.code` — stable string identifier (e.g. `invalid_params`, `rate_limit_exceeded`) - `error.message` — human-readable cause - `error.fix` — exact recovery steps (e.g. \"Pass `check_in_after` as ISO 8601: `?check_in_after=2026-01-15`\") - `error.docs_url` — link to the canonical write-up at `https://repull.dev/docs/errors/{code}` - `error.request_id` — id to correlate with server-side logs - `error.field` / `error.value_received` / `error.valid_values` / `error.did_you_mean` — when the error is parameter-specific - `error.retry_after` — seconds to wait before retrying (rate-limit + transient upstream) `Access-Control-Expose-Headers` lists `x-request-id` and the `X-RateLimit-*` family so browsers can read them on cross-origin responses. ## Quick Start 1. Get an API key at https://repull.dev/dashboard 2. Connect a PMS: `POST /v1/connect/{provider}` 3. List properties: `GET /v1/properties` 4. Get reservations: `GET /v1/reservations` ## Authentication All requests require a Bearer token: ``` Authorization: Bearer sk_live_YOUR_API_KEY ``` ## Request Correlation (X-Request-ID) Every response carries an `X-Request-ID` header, e.g. `X-Request-ID: req_01HXY...`. Include this id in support tickets and bug reports — we can trace the full request lifecycle (auth, rate limit, handler, downstream calls, log row) from a single id. You may set the header on the inbound request to forward your own trace id; we will echo it back instead of generating a new one. Accepted format: `^[\\\\w.-]{1,128}$`. The id is also embedded in error envelopes as `request_id` so server-side log diffs work even when the response headers are stripped by an intermediate proxy. ## Rate Limits The public API enforces a per-API-key sliding-window rate limit on top of the per-tier monthly + daily-AI quotas. **Default policy:** 600 requests per 60 seconds, per API key. Sliding window — there is no fixed-minute boundary you can burst across. Every response includes: | Header | Meaning | |---|---| | `X-RateLimit-Limit` | Requests permitted in the current window. | | `X-RateLimit-Remaining` | Requests left in the current window after this call. | | `X-RateLimit-Reset` | Unix epoch (seconds) when the next slot opens. | | `X-RateLimit-Policy` | Machine-readable policy descriptor, e.g. `600;w=60`. | | `Retry-After` | Seconds to wait before retrying. **Only present on 429 responses.** | **On 429 (rate_limit_exceeded):** the response body matches the standard error envelope with `code: \"rate_limit_exceeded\"`, plus `limit`, `window_seconds`, `retry_after`, and `request_id` fields. SDKs MUST honor `Retry-After` and use exponential backoff with jitter on subsequent retries — never a tight loop. Recommended backoff: ``` sleep_ms = (Retry-After * 1000) + random(0..250) ``` Monthly + daily-AI tier quotas (`free`, `starter`, `custom`) are enforced separately and also surface as 429s; they include `tier`, `scope`, `limit`, `used` and `resets_at` fields. **The way past a request quota.** The monthly quota refusal (`429 rate_limit_exceeded` with `scope: \"monthly\"`), `402 credits_exhausted` and `429 daily_limit_exceeded` also carry `upgrade` (the cheapest plan that covers your usage: its exact monthly price for your listings, its request quotas and a `checkout_url` that opens checkout for that price; `plan: \"custom\"` with a `contact_email` when no self-serve plan covers it), `credits` (pay-as-you-go: `usd_per_1000_requests`, `top_up_url`, your `balance_usd`), `resets_at` and `projected_monthly_requests`. The per-minute 429 (`scope: \"per_api_key\"`) carries none of these: wait `Retry-After`. ## Plan listing limits Each plan includes a number of **active listings**: | Tier | Active listings | |---|---| | `free` | 3 | | `starter` | no cap: 10 included, then billed per listing | | `custom` | no cap | Going over the plan never blocks your API calls. Listings beyond the plan are **held back**: they stay connected and keep syncing, but they are not served. A held-back listing answers `403 listing_inactive` with `reason: \"plan_limit\"`, and collection routes leave it out. Every JSON response then carries a `planNotice` and the `X-Repull-Listings-Held-Back` header, so you know there is more to see. Choose which listings are active with `POST /v1/listings/status`, or upgrade at `https://repull.dev/dashboard/billing` to activate them all. Only a call that would itself take you over the plan is refused, with **`402 listings_limit_exceeded`**: activating listings (`PATCH /v1/listings/{id}` with `{ \"active\": true }`, `POST /v1/listings/status`) or creating one (`POST /v1/listings`). Nothing else changes. The envelope carries the tier, the limit, the active count and an upgrade link next to the standard `code` / `message` / `fix` / `docs_url` / `request_id`. If an account has more active listings than its plan (for example after a downgrade), calls are still served and `planNotice` says so (code \"listings_over_plan\").
4
+ #The unified API for vacation rental tech. Connect Airbnb, Booking.com, Vrbo and more channels, plus 14 PMS platforms, through one REST API. ## Designed for AI agents Every error response on this API includes machine-parseable fields so an LLM (Claude in MCP, Cursor, Cline, GPT, etc.) can self-recover without escalating to a human: - `error.code` — stable string identifier (e.g. `invalid_params`, `rate_limit_exceeded`) - `error.message` — human-readable cause - `error.fix` — exact recovery steps (e.g. \"Pass `check_in_after` as ISO 8601: `?check_in_after=2026-01-15`\") - `error.docs_url` — link to the canonical write-up at `https://repull.dev/docs/errors/{code}` - `error.request_id` — id to correlate with server-side logs - `error.field` / `error.value_received` / `error.valid_values` / `error.did_you_mean` — when the error is parameter-specific - `error.retry_after` — seconds to wait before retrying (rate-limit + transient upstream) `Access-Control-Expose-Headers` lists `x-request-id` and the `X-RateLimit-*` family so browsers can read them on cross-origin responses. ## Quick Start 1. Get an API key at https://repull.dev/dashboard 2. Connect a PMS: `POST /v1/connect/{provider}` 3. List properties: `GET /v1/properties` 4. Get reservations: `GET /v1/reservations` ## Authentication All requests require a Bearer token: ``` Authorization: Bearer sk_live_YOUR_API_KEY ``` ## Request Correlation (X-Request-ID) Every response carries an `X-Request-ID` header, e.g. `X-Request-ID: req_01HXY...`. Include this id in support tickets and bug reports — we can trace the full request lifecycle (auth, rate limit, handler, downstream calls, log row) from a single id. You may set the header on the inbound request to forward your own trace id; we will echo it back instead of generating a new one. Accepted format: `^[\\\\w.-]{1,128}$`. The id is also embedded in error envelopes as `request_id` so server-side log diffs work even when the response headers are stripped by an intermediate proxy. ## Rate Limits The public API enforces a per-API-key sliding-window rate limit on top of the per-tier monthly + daily-AI quotas. **Default policy:** 600 requests per 60 seconds, per API key. Sliding window — there is no fixed-minute boundary you can burst across. Every response includes: | Header | Meaning | |---|---| | `X-RateLimit-Limit` | Requests permitted in the current window. | | `X-RateLimit-Remaining` | Requests left in the current window after this call. | | `X-RateLimit-Reset` | Unix epoch (seconds) when the next slot opens. | | `X-RateLimit-Policy` | Machine-readable policy descriptor, e.g. `600;w=60`. | | `Retry-After` | Seconds to wait before retrying. **Only present on 429 responses.** | **On 429 (rate_limit_exceeded):** the response body matches the standard error envelope with `code: \"rate_limit_exceeded\"`, plus `limit`, `window_seconds`, `retry_after`, and `request_id` fields. SDKs MUST honor `Retry-After` and use exponential backoff with jitter on subsequent retries — never a tight loop. Recommended backoff: ``` sleep_ms = (Retry-After * 1000) + random(0..250) ``` Monthly + daily-AI tier quotas (`free`, `starter`, `custom`) are enforced separately and also surface as 429s; they include `tier`, `scope`, `limit`, `used` and `resets_at` fields. **The way past a request quota.** The monthly quota refusal (`429 rate_limit_exceeded` with `scope: \"monthly\"`), `402 credits_exhausted` and `429 daily_limit_exceeded` also carry `upgrade` (the cheapest plan that covers your usage: its exact monthly price for your listings, its request quotas and a `checkout_url` that opens checkout for that price; `plan: \"custom\"` with a `contact_email` when no self-serve plan covers it), `credits` (pay-as-you-go: `usd_per_1000_requests`, `top_up_url`, your `balance_usd`), `resets_at` and `projected_monthly_requests`. The per-minute 429 (`scope: \"per_api_key\"`) carries none of these: wait `Retry-After`. ## Plan listing limits Each plan includes a number of **active listings**: | Tier | Active listings | |---|---| | `free` | 3 | | `starter` | no cap: 10 included, then billed per listing | | `custom` | no cap | Going over the plan never blocks your API calls. Listings beyond the plan are **held back**: they stay connected and keep syncing, but they are not served. A held-back listing answers `403 listing_inactive` with `reason: \"plan_limit\"`, and collection routes leave it out. Every JSON response then carries a `planNotice` and the `X-Repull-Listings-Held-Back` header, so you know there is more to see. Choose which listings are active with `POST /v1/listings/status`. Upgrading at `https://repull.dev/dashboard/billing` lifts the cap but does not switch held-back listings on: you choose which to activate afterwards, with the same call or from the dashboard, and each one you switch on is billed from then. Only a call that would itself take you over the plan is refused, with **`402 listings_limit_exceeded`**: activating listings (`PATCH /v1/listings/{id}` with `{ \"active\": true }`, `POST /v1/listings/status`) or creating one (`POST /v1/listings`). Nothing else changes. The envelope carries the tier, the limit, the active count and an upgrade link next to the standard `code` / `message` / `fix` / `docs_url` / `request_id`. If an account has more active listings than its plan (for example after a downgrade), calls are still served and `planNotice` says so (code \"listings_over_plan\"). ## Failed payments If your plan's renewal payment fails, nothing is blocked: your API calls keep working while Stripe retries the card. Every successful JSON response then carries a `billingNotice` (code `payment_failed`) with the amount, when it failed, the next automatic retry (`nextRetryAt`) and `payUrl`, the invoice to pay. It disappears once the invoice is paid.
5
5
 
6
6
  The version of the OpenAPI document: 1.0.0
7
7
 
@@ -24,8 +24,15 @@ module Repull
24
24
 
25
25
  attr_accessor :min_nights
26
26
 
27
+ # Maximum stay for an arrival on these dates. Sent to Airbnb and Booking.com. Vrbo has no per-date maximum stay, so it is not sent there.
27
28
  attr_accessor :max_nights
28
29
 
30
+ # No check-in on these dates (`true`), or check-in allowed again (`false`). Sent to Airbnb, Booking.com and Vrbo. Leaving it out keeps the current value.
31
+ attr_accessor :closed_to_arrival
32
+
33
+ # No check-out on these dates (`true`), or check-out allowed again (`false`). Sent to Airbnb, Booking.com and Vrbo. Leaving it out keeps the current value.
34
+ attr_accessor :closed_to_departure
35
+
29
36
  # Rooms to sell on these dates, for a listing that sells several identical rooms (`unitCount` > 1, e.g. a Booking.com room type). Up to the listing's `unitCount`. Refused with `409 managed_by_pms` on a hotel PMS room type (Cloudbeds, Mews) — its PMS owns the room count.
30
37
  attr_accessor :available_units
31
38
 
@@ -36,6 +43,8 @@ module Repull
36
43
  :'price' => :'price',
37
44
  :'min_nights' => :'minNights',
38
45
  :'max_nights' => :'maxNights',
46
+ :'closed_to_arrival' => :'closedToArrival',
47
+ :'closed_to_departure' => :'closedToDeparture',
39
48
  :'available_units' => :'availableUnits'
40
49
  }
41
50
  end
@@ -57,6 +66,8 @@ module Repull
57
66
  :'price' => :'Float',
58
67
  :'min_nights' => :'Integer',
59
68
  :'max_nights' => :'Integer',
69
+ :'closed_to_arrival' => :'Boolean',
70
+ :'closed_to_departure' => :'Boolean',
60
71
  :'available_units' => :'Integer'
61
72
  }
62
73
  end
@@ -99,6 +110,14 @@ module Repull
99
110
  self.max_nights = attributes[:'max_nights']
100
111
  end
101
112
 
113
+ if attributes.key?(:'closed_to_arrival')
114
+ self.closed_to_arrival = attributes[:'closed_to_arrival']
115
+ end
116
+
117
+ if attributes.key?(:'closed_to_departure')
118
+ self.closed_to_departure = attributes[:'closed_to_departure']
119
+ end
120
+
102
121
  if attributes.key?(:'available_units')
103
122
  self.available_units = attributes[:'available_units']
104
123
  end
@@ -185,6 +204,8 @@ module Repull
185
204
  price == o.price &&
186
205
  min_nights == o.min_nights &&
187
206
  max_nights == o.max_nights &&
207
+ closed_to_arrival == o.closed_to_arrival &&
208
+ closed_to_departure == o.closed_to_departure &&
188
209
  available_units == o.available_units
189
210
  end
190
211
 
@@ -197,7 +218,7 @@ module Repull
197
218
  # Calculates hash code according to all attributes.
198
219
  # @return [Integer] Hash code
199
220
  def hash
200
- [available, price, min_nights, max_nights, available_units].hash
221
+ [available, price, min_nights, max_nights, closed_to_arrival, closed_to_departure, available_units].hash
201
222
  end
202
223
 
203
224
  # Builds the object from hash