repull 0.2.43 → 0.2.44

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 (811) hide show
  1. checksums.yaml +4 -4
  2. data/README.md +8 -37
  3. data/lib/repull/api/airbnb_api.rb +1 -1
  4. data/lib/repull/api/atlas_api.rb +1 -1
  5. data/lib/repull/api/availability_api.rb +1 -1
  6. data/lib/repull/api/billing_api.rb +1 -1
  7. data/lib/repull/api/booking_com_api.rb +1 -1
  8. data/lib/repull/api/connect_api.rb +1 -1
  9. data/lib/repull/api/connections_api.rb +1 -1
  10. data/lib/repull/api/conversations_api.rb +1 -1
  11. data/lib/repull/api/guests_api.rb +1 -1
  12. data/lib/repull/api/health_api.rb +1 -1
  13. data/lib/repull/api/hotels_api.rb +1 -1
  14. data/lib/repull/api/kv_api.rb +1 -1
  15. data/lib/repull/api/listings_api.rb +1 -1
  16. data/lib/repull/api/markets_api.rb +1 -1
  17. data/lib/repull/api/migrate_api.rb +1 -1
  18. data/lib/repull/api/pricing_api.rb +1 -1
  19. data/lib/repull/api/promotions_api.rb +1 -1
  20. data/lib/repull/api/properties_api.rb +1 -1
  21. data/lib/repull/api/quotes_api.rb +1 -1
  22. data/lib/repull/api/reservations_api.rb +1 -1
  23. data/lib/repull/api/resolutions_api.rb +1 -1
  24. data/lib/repull/api/reviews_api.rb +1 -1
  25. data/lib/repull/api/schema_api.rb +1 -1
  26. data/lib/repull/api/system_api.rb +1 -1
  27. data/lib/repull/api/transactions_api.rb +1 -1
  28. data/lib/repull/api/vrbo_api.rb +1 -1
  29. data/lib/repull/api/webhooks_api.rb +1 -1
  30. data/lib/repull/api/workspaces_api.rb +1 -1
  31. data/lib/repull/api_client.rb +1 -1
  32. data/lib/repull/api_error.rb +1 -1
  33. data/lib/repull/api_model_base.rb +1 -1
  34. data/lib/repull/configuration.rb +1 -1
  35. data/lib/repull/models/accept_reservation_request200_response.rb +1 -1
  36. data/lib/repull/models/account_created_event.rb +1 -1
  37. data/lib/repull/models/account_created_payload.rb +1 -1
  38. data/lib/repull/models/account_disconnected_event.rb +1 -1
  39. data/lib/repull/models/account_disconnected_payload.rb +1 -1
  40. data/lib/repull/models/account_disconnected_payload_listings_inner.rb +1 -1
  41. data/lib/repull/models/account_import.rb +1 -1
  42. data/lib/repull/models/account_import_completed_event.rb +1 -1
  43. data/lib/repull/models/account_import_counts.rb +1 -1
  44. data/lib/repull/models/account_import_failed_event.rb +1 -1
  45. data/lib/repull/models/account_import_finished_payload.rb +1 -1
  46. data/lib/repull/models/account_import_stage.rb +1 -1
  47. data/lib/repull/models/account_import_started_event.rb +1 -1
  48. data/lib/repull/models/account_import_started_payload.rb +1 -1
  49. data/lib/repull/models/acknowledge_booking_reservations_request.rb +1 -1
  50. data/lib/repull/models/ai_operation.rb +1 -1
  51. data/lib/repull/models/ai_operation_completed_event.rb +1 -1
  52. data/lib/repull/models/ai_operation_completed_payload.rb +1 -1
  53. data/lib/repull/models/ai_operation_failed_event.rb +1 -1
  54. data/lib/repull/models/ai_operation_failed_payload.rb +1 -1
  55. data/lib/repull/models/ai_operation_failed_payload_error.rb +1 -1
  56. data/lib/repull/models/airbnb_access.rb +1 -1
  57. data/lib/repull/models/airbnb_access_accounts_inner.rb +1 -1
  58. data/lib/repull/models/airbnb_account_freshness.rb +1 -1
  59. data/lib/repull/models/airbnb_alteration.rb +1 -1
  60. data/lib/repull/models/airbnb_alteration_create_request.rb +1 -1
  61. data/lib/repull/models/airbnb_amenity.rb +1 -1
  62. data/lib/repull/models/airbnb_availability_write_request.rb +1 -1
  63. data/lib/repull/models/airbnb_calendar_operation.rb +1 -1
  64. data/lib/repull/models/airbnb_connection.rb +1 -1
  65. data/lib/repull/models/airbnb_connection_accessibility_amenities_inner.rb +1 -1
  66. data/lib/repull/models/airbnb_connection_amenities_inner.rb +1 -1
  67. data/lib/repull/models/airbnb_connection_host.rb +1 -1
  68. data/lib/repull/models/airbnb_connection_response.rb +1 -1
  69. data/lib/repull/models/airbnb_connection_summary.rb +1 -1
  70. data/lib/repull/models/airbnb_content_write_response.rb +1 -1
  71. data/lib/repull/models/airbnb_data_freshness.rb +1 -1
  72. data/lib/repull/models/airbnb_description_write_request.rb +1 -1
  73. data/lib/repull/models/airbnb_description_write_request_description.rb +1 -1
  74. data/lib/repull/models/airbnb_host_review_submit.rb +1 -1
  75. data/lib/repull/models/airbnb_host_review_submit_category_ratings_inner.rb +1 -1
  76. data/lib/repull/models/airbnb_listing.rb +1 -1
  77. data/lib/repull/models/airbnb_listing_action200_response.rb +1 -1
  78. data/lib/repull/models/airbnb_listing_action200_response_one_of.rb +1 -1
  79. data/lib/repull/models/airbnb_listing_action200_response_one_of1.rb +1 -1
  80. data/lib/repull/models/airbnb_listing_action_request.rb +1 -1
  81. data/lib/repull/models/airbnb_listing_details_response.rb +1 -1
  82. data/lib/repull/models/airbnb_listing_details_write_request.rb +1 -1
  83. data/lib/repull/models/airbnb_listing_details_write_request_check_in_option.rb +1 -1
  84. data/lib/repull/models/airbnb_listing_details_write_request_quiet_hours_inner.rb +1 -1
  85. data/lib/repull/models/airbnb_listing_lifecycle_response.rb +1 -1
  86. data/lib/repull/models/airbnb_listing_list_response.rb +1 -1
  87. data/lib/repull/models/airbnb_permits_response.rb +1 -1
  88. data/lib/repull/models/airbnb_permits_response_cached_inner.rb +1 -1
  89. data/lib/repull/models/airbnb_permits_write_request.rb +1 -1
  90. data/lib/repull/models/airbnb_permits_write_request_permits_inner.rb +1 -1
  91. data/lib/repull/models/airbnb_photo_position.rb +1 -1
  92. data/lib/repull/models/airbnb_pricing_write_request.rb +1 -1
  93. data/lib/repull/models/airbnb_pricing_write_request_fees_inner.rb +1 -1
  94. data/lib/repull/models/airbnb_pricing_write_request_records_inner.rb +1 -1
  95. data/lib/repull/models/airbnb_publish_result.rb +1 -1
  96. data/lib/repull/models/airbnb_reservation.rb +1 -1
  97. data/lib/repull/models/airbnb_reservation_action200_response.rb +1 -1
  98. data/lib/repull/models/airbnb_reservation_action_request.rb +1 -1
  99. data/lib/repull/models/airbnb_reservation_list_response.rb +1 -1
  100. data/lib/repull/models/airbnb_review.rb +1 -1
  101. data/lib/repull/models/airbnb_review_list_response.rb +1 -1
  102. data/lib/repull/models/airbnb_safety_disclosure.rb +1 -1
  103. data/lib/repull/models/airbnb_safety_disclosures_response.rb +1 -1
  104. data/lib/repull/models/airbnb_safety_disclosures_write_request.rb +1 -1
  105. data/lib/repull/models/airbnb_thread.rb +1 -1
  106. data/lib/repull/models/airbnb_thread_list_response.rb +1 -1
  107. data/lib/repull/models/airbnb_transaction.rb +1 -1
  108. data/lib/repull/models/airbnb_transaction_fees.rb +1 -1
  109. data/lib/repull/models/airbnb_transaction_payout.rb +1 -1
  110. data/lib/repull/models/alteration_change.rb +1 -1
  111. data/lib/repull/models/alteration_webhook_object.rb +1 -1
  112. data/lib/repull/models/apply_connection_mappings200_response.rb +1 -1
  113. data/lib/repull/models/apply_connection_mappings200_response_results_inner.rb +1 -1
  114. data/lib/repull/models/apply_connection_mappings_request.rb +1 -1
  115. data/lib/repull/models/apply_connection_mappings_request_mappings_inner.rb +1 -1
  116. data/lib/repull/models/auto_map_connection_units200_response.rb +1 -1
  117. data/lib/repull/models/auto_map_connection_units_request.rb +1 -1
  118. data/lib/repull/models/availability_batch_write_request.rb +1 -1
  119. data/lib/repull/models/availability_write_request.rb +1 -1
  120. data/lib/repull/models/availability_write_result.rb +1 -1
  121. data/lib/repull/models/availability_write_result_synced.rb +1 -1
  122. data/lib/repull/models/availability_write_settings.rb +1 -1
  123. data/lib/repull/models/booking_availability_state_response.rb +1 -1
  124. data/lib/repull/models/booking_availability_update.rb +1 -1
  125. data/lib/repull/models/booking_availability_update_date_range.rb +1 -1
  126. data/lib/repull/models/booking_availability_update_request.rb +1 -1
  127. data/lib/repull/models/booking_availability_update_request_property_id.rb +1 -1
  128. data/lib/repull/models/booking_availability_update_request_updates_inner.rb +1 -1
  129. data/lib/repull/models/booking_connect_listing_option.rb +1 -1
  130. data/lib/repull/models/booking_connect_room.rb +1 -1
  131. data/lib/repull/models/booking_connect_rooms_response.rb +1 -1
  132. data/lib/repull/models/booking_conversation.rb +1 -1
  133. data/lib/repull/models/booking_derived_pricing_update.rb +1 -1
  134. data/lib/repull/models/booking_derived_pricing_write_response.rb +1 -1
  135. data/lib/repull/models/booking_derived_pricing_write_response_rates_inner.rb +1 -1
  136. data/lib/repull/models/booking_derived_pricing_write_response_verification.rb +1 -1
  137. data/lib/repull/models/booking_derived_pricing_write_response_verification_rows_inner.rb +1 -1
  138. data/lib/repull/models/booking_occupancy_rule.rb +1 -1
  139. data/lib/repull/models/booking_pricing_rate_update.rb +1 -1
  140. data/lib/repull/models/booking_pricing_rate_update_date_range.rb +1 -1
  141. data/lib/repull/models/booking_pricing_rate_update_restrictions.rb +1 -1
  142. data/lib/repull/models/booking_pricing_response.rb +1 -1
  143. data/lib/repull/models/booking_pricing_update_request.rb +1 -1
  144. data/lib/repull/models/booking_pricing_update_response.rb +1 -1
  145. data/lib/repull/models/booking_property.rb +1 -1
  146. data/lib/repull/models/booking_property_action_request.rb +1 -1
  147. data/lib/repull/models/booking_property_action_response.rb +1 -1
  148. data/lib/repull/models/booking_property_listings_inner.rb +1 -1
  149. data/lib/repull/models/booking_publish_result.rb +1 -1
  150. data/lib/repull/models/booking_publish_section_error.rb +1 -1
  151. data/lib/repull/models/booking_rate_write_occupancy.rb +1 -1
  152. data/lib/repull/models/booking_rate_write_price_half.rb +1 -1
  153. data/lib/repull/models/booking_rate_write_restriction_half.rb +1 -1
  154. data/lib/repull/models/booking_rate_write_verification.rb +1 -1
  155. data/lib/repull/models/booking_rate_write_verification_row.rb +1 -1
  156. data/lib/repull/models/booking_reservation.rb +1 -1
  157. data/lib/repull/models/booking_reservation_room.rb +1 -1
  158. data/lib/repull/models/booking_restriction_request_row.rb +1 -1
  159. data/lib/repull/models/booking_restriction_verification.rb +1 -1
  160. data/lib/repull/models/booking_restriction_verification_row.rb +1 -1
  161. data/lib/repull/models/booking_restriction_verification_row_booking_value.rb +1 -1
  162. data/lib/repull/models/booking_restriction_verification_row_expected.rb +1 -1
  163. data/lib/repull/models/booking_restriction_write_response.rb +1 -1
  164. data/lib/repull/models/booking_room_mapping.rb +1 -1
  165. data/lib/repull/models/booking_rooms_rates_response.rb +1 -1
  166. data/lib/repull/models/booking_rooms_rates_response_rooms_inner.rb +1 -1
  167. data/lib/repull/models/booking_rooms_rates_response_rooms_inner_rates_inner.rb +1 -1
  168. data/lib/repull/models/booking_setup_request.rb +1 -1
  169. data/lib/repull/models/booking_setup_request_legal_entity.rb +1 -1
  170. data/lib/repull/models/booking_unacknowledged_event.rb +1 -1
  171. data/lib/repull/models/booking_unacknowledged_payload.rb +1 -1
  172. data/lib/repull/models/booking_upstream_failure.rb +1 -1
  173. data/lib/repull/models/booking_verify_hotel_request.rb +1 -1
  174. data/lib/repull/models/booking_verify_hotel_response.rb +1 -1
  175. data/lib/repull/models/bulk_pricing_failure.rb +1 -1
  176. data/lib/repull/models/bulk_pricing_item.rb +1 -1
  177. data/lib/repull/models/bulk_pricing_request.rb +1 -1
  178. data/lib/repull/models/bulk_pricing_response.rb +1 -1
  179. data/lib/repull/models/calendar_day.rb +1 -1
  180. data/lib/repull/models/calendar_response.rb +1 -1
  181. data/lib/repull/models/cancel_reservation200_response.rb +1 -1
  182. data/lib/repull/models/cancel_reservation_request.rb +1 -1
  183. data/lib/repull/models/channel_degraded_event.rb +1 -1
  184. data/lib/repull/models/channel_degraded_payload.rb +1 -1
  185. data/lib/repull/models/channel_degraded_payload_object.rb +1 -1
  186. data/lib/repull/models/channel_market_state_item.rb +1 -1
  187. data/lib/repull/models/channel_sync_failed_event.rb +1 -1
  188. data/lib/repull/models/channel_sync_failure_payload.rb +1 -1
  189. data/lib/repull/models/channel_sync_failure_payload_failures_inner.rb +1 -1
  190. data/lib/repull/models/channel_sync_failure_payload_object.rb +1 -1
  191. data/lib/repull/models/charge_per.rb +1 -1
  192. data/lib/repull/models/check_migration_cutover200_response.rb +1 -1
  193. data/lib/repull/models/check_migration_cutover_request.rb +1 -1
  194. data/lib/repull/models/check_migration_cutover_request_reservations_inner.rb +1 -1
  195. data/lib/repull/models/clear_kv200_response.rb +1 -1
  196. data/lib/repull/models/connect_host.rb +1 -1
  197. data/lib/repull/models/connect_provider.rb +1 -1
  198. data/lib/repull/models/connect_provider_list_response.rb +1 -1
  199. data/lib/repull/models/connect_session.rb +1 -1
  200. data/lib/repull/models/connect_session_completed_event.rb +1 -1
  201. data/lib/repull/models/connect_session_completed_payload.rb +1 -1
  202. data/lib/repull/models/connect_status.rb +1 -1
  203. data/lib/repull/models/connect_status_accounts_inner.rb +1 -1
  204. data/lib/repull/models/connect_status_capabilities.rb +1 -1
  205. data/lib/repull/models/connection.rb +1 -1
  206. data/lib/repull/models/connection_action.rb +1 -1
  207. data/lib/repull/models/connection_list_response.rb +1 -1
  208. data/lib/repull/models/conversation.rb +1 -1
  209. data/lib/repull/models/conversation_capabilities.rb +1 -1
  210. data/lib/repull/models/conversation_detail.rb +1 -1
  211. data/lib/repull/models/conversation_guest.rb +1 -1
  212. data/lib/repull/models/conversation_guest_contact.rb +1 -1
  213. data/lib/repull/models/conversation_host.rb +1 -1
  214. data/lib/repull/models/conversation_list_response.rb +1 -1
  215. data/lib/repull/models/conversation_message_attachment.rb +1 -1
  216. data/lib/repull/models/create_airbnb_listing_room_request.rb +1 -1
  217. data/lib/repull/models/create_airbnb_offer_request.rb +1 -1
  218. data/lib/repull/models/create_airbnb_offer_request_guest_details.rb +1 -1
  219. data/lib/repull/models/create_billing_checkout200_response.rb +1 -1
  220. data/lib/repull/models/create_billing_checkout_request.rb +1 -1
  221. data/lib/repull/models/create_booking_webhook_request.rb +1 -1
  222. data/lib/repull/models/create_connect_session_request.rb +1 -1
  223. data/lib/repull/models/create_connect_session_request_copy.rb +1 -1
  224. data/lib/repull/models/create_connect_session_request_workspace.rb +1 -1
  225. data/lib/repull/models/create_connection_request.rb +1 -1
  226. data/lib/repull/models/create_conversation_special_offer201_response.rb +1 -1
  227. data/lib/repull/models/create_conversation_special_offer201_response_fees_inner.rb +1 -1
  228. data/lib/repull/models/create_conversation_special_offer201_response_guests.rb +1 -1
  229. data/lib/repull/models/create_conversation_special_offer201_response_lines_inner.rb +1 -1
  230. data/lib/repull/models/create_conversation_special_offer_request.rb +1 -1
  231. data/lib/repull/models/create_conversation_special_offer_request_fees_inner.rb +1 -1
  232. data/lib/repull/models/create_conversation_special_offer_request_guests.rb +1 -1
  233. data/lib/repull/models/create_webhook_request.rb +1 -1
  234. data/lib/repull/models/custom_schema.rb +1 -1
  235. data/lib/repull/models/custom_schema_create.rb +1 -1
  236. data/lib/repull/models/custom_schema_create_response.rb +1 -1
  237. data/lib/repull/models/custom_schema_delete_response.rb +1 -1
  238. data/lib/repull/models/custom_schema_list_response.rb +1 -1
  239. data/lib/repull/models/custom_schema_summary.rb +1 -1
  240. data/lib/repull/models/custom_schema_update.rb +1 -1
  241. data/lib/repull/models/decline_reservation_request_request.rb +1 -1
  242. data/lib/repull/models/delete_airbnb_listing_photo200_response.rb +1 -1
  243. data/lib/repull/models/delete_airbnb_listing_room200_response.rb +1 -1
  244. data/lib/repull/models/delete_connection200_response.rb +1 -1
  245. data/lib/repull/models/delete_kv200_response.rb +1 -1
  246. data/lib/repull/models/delete_migration200_response.rb +1 -1
  247. data/lib/repull/models/delete_migration200_response_data.rb +1 -1
  248. data/lib/repull/models/error.rb +1 -1
  249. data/lib/repull/models/error_error.rb +1 -1
  250. data/lib/repull/models/error_error_listings_inner.rb +1 -1
  251. data/lib/repull/models/error_error_support.rb +1 -1
  252. data/lib/repull/models/get_airbnb_alteration200_response.rb +1 -1
  253. data/lib/repull/models/get_airbnb_booking_settings200_response.rb +1 -1
  254. data/lib/repull/models/get_airbnb_booking_settings200_response_data.rb +1 -1
  255. data/lib/repull/models/get_airbnb_booking_settings200_response_data_advance_notice.rb +1 -1
  256. data/lib/repull/models/get_airbnb_booking_settings200_response_data_booking_window.rb +1 -1
  257. data/lib/repull/models/get_airbnb_booking_settings200_response_data_cancellation.rb +1 -1
  258. data/lib/repull/models/get_airbnb_booking_settings200_response_data_cancellation_non_refundable.rb +1 -1
  259. data/lib/repull/models/get_airbnb_booking_settings200_response_data_check_in.rb +1 -1
  260. data/lib/repull/models/get_airbnb_booking_settings200_response_data_check_in_start.rb +1 -1
  261. data/lib/repull/models/get_airbnb_booking_settings200_response_data_check_out.rb +1 -1
  262. data/lib/repull/models/get_airbnb_booking_settings200_response_data_instant_book.rb +1 -1
  263. data/lib/repull/models/get_airbnb_booking_settings200_response_data_preparation_time.rb +1 -1
  264. data/lib/repull/models/get_airbnb_checkin_guide200_response.rb +1 -1
  265. data/lib/repull/models/get_airbnb_listing_details200_response.rb +1 -1
  266. data/lib/repull/models/get_airbnb_listing_quality200_response.rb +1 -1
  267. data/lib/repull/models/get_airbnb_listing_settings200_response.rb +1 -1
  268. data/lib/repull/models/get_airbnb_offer200_response.rb +1 -1
  269. data/lib/repull/models/get_airbnb_thread200_response.rb +1 -1
  270. data/lib/repull/models/get_billing200_response.rb +1 -1
  271. data/lib/repull/models/get_billing200_response_limits.rb +1 -1
  272. data/lib/repull/models/get_billing200_response_used.rb +1 -1
  273. data/lib/repull/models/get_booking_extranet_login_config200_response.rb +1 -1
  274. data/lib/repull/models/get_booking_extranet_login_status200_response.rb +1 -1
  275. data/lib/repull/models/get_channel_health200_response.rb +1 -1
  276. data/lib/repull/models/get_channel_health200_response_vrbo.rb +1 -1
  277. data/lib/repull/models/get_connect_write_policy200_response.rb +1 -1
  278. data/lib/repull/models/get_health200_response.rb +1 -1
  279. data/lib/repull/models/get_hotel200_response.rb +1 -1
  280. data/lib/repull/models/get_hotel200_response_room_types_inner.rb +1 -1
  281. data/lib/repull/models/get_listing_calendar_sync200_response.rb +1 -1
  282. data/lib/repull/models/get_listing_calendar_sync200_response_channels_inner.rb +1 -1
  283. data/lib/repull/models/get_listing_calendar_sync200_response_channels_inner_problems_inner.rb +1 -1
  284. data/lib/repull/models/get_listing_calendar_sync200_response_channels_inner_queue.rb +1 -1
  285. data/lib/repull/models/get_listing_calendar_sync200_response_channels_inner_queue_last_push.rb +1 -1
  286. data/lib/repull/models/get_listing_markups200_response.rb +1 -1
  287. data/lib/repull/models/get_listing_markups200_response_airbnb_inner.rb +1 -1
  288. data/lib/repull/models/get_listing_markups200_response_booking_inner.rb +1 -1
  289. data/lib/repull/models/get_listing_markups200_response_vrbo_inner.rb +1 -1
  290. data/lib/repull/models/get_migration200_response.rb +1 -1
  291. data/lib/repull/models/get_migration_channel_map200_response.rb +1 -1
  292. data/lib/repull/models/get_migration_report200_response.rb +1 -1
  293. data/lib/repull/models/get_reservation_summary200_response.rb +1 -1
  294. data/lib/repull/models/get_reservation_summary200_response_totals_inner.rb +1 -1
  295. data/lib/repull/models/get_usage_logs200_response.rb +1 -1
  296. data/lib/repull/models/get_usage_logs200_response_data_inner.rb +1 -1
  297. data/lib/repull/models/get_usage_logs200_response_pagination.rb +1 -1
  298. data/lib/repull/models/get_usage_summary200_response.rb +1 -1
  299. data/lib/repull/models/get_usage_summary200_response_breakdown_inner.rb +1 -1
  300. data/lib/repull/models/get_usage_summary200_response_credits.rb +1 -1
  301. data/lib/repull/models/get_usage_summary200_response_limits.rb +1 -1
  302. data/lib/repull/models/get_usage_summary200_response_remaining.rb +1 -1
  303. data/lib/repull/models/get_usage_summary200_response_status_distribution.rb +1 -1
  304. data/lib/repull/models/get_usage_summary200_response_timeline_inner.rb +1 -1
  305. data/lib/repull/models/get_usage_summary200_response_totals.rb +1 -1
  306. data/lib/repull/models/get_usage_summary200_response_used.rb +1 -1
  307. data/lib/repull/models/get_usage_tier200_response.rb +1 -1
  308. data/lib/repull/models/get_usage_tier200_response_limits.rb +1 -1
  309. data/lib/repull/models/get_usage_tier200_response_remaining.rb +1 -1
  310. data/lib/repull/models/get_usage_tier200_response_used.rb +1 -1
  311. data/lib/repull/models/get_vrbo_publish_job200_response.rb +1 -1
  312. data/lib/repull/models/get_vrbo_publish_job200_response_job.rb +1 -1
  313. data/lib/repull/models/get_vrbo_publish_job200_response_job_rejected_photos_inner.rb +1 -1
  314. data/lib/repull/models/guest.rb +1 -1
  315. data/lib/repull/models/guest_contact.rb +1 -1
  316. data/lib/repull/models/guest_create_request.rb +1 -1
  317. data/lib/repull/models/guest_create_response.rb +1 -1
  318. data/lib/repull/models/guest_create_response_pms.rb +1 -1
  319. data/lib/repull/models/guest_flag.rb +1 -1
  320. data/lib/repull/models/guest_list_response.rb +1 -1
  321. data/lib/repull/models/guest_note.rb +1 -1
  322. data/lib/repull/models/guest_profile.rb +1 -1
  323. data/lib/repull/models/guest_reservations_summary.rb +1 -1
  324. data/lib/repull/models/guest_update_request.rb +1 -1
  325. data/lib/repull/models/guest_update_response.rb +1 -1
  326. data/lib/repull/models/guest_update_response_contacts_inner.rb +1 -1
  327. data/lib/repull/models/guest_update_response_pms_inner.rb +1 -1
  328. data/lib/repull/models/import_from_channex200_response.rb +1 -1
  329. data/lib/repull/models/import_from_channex200_response_data.rb +1 -1
  330. data/lib/repull/models/import_from_channex200_response_data_channels_inner.rb +1 -1
  331. data/lib/repull/models/import_from_channex200_response_data_properties_inner.rb +1 -1
  332. data/lib/repull/models/import_from_channex200_response_data_summary.rb +1 -1
  333. data/lib/repull/models/import_from_channex200_response_data_summary_bookings.rb +1 -1
  334. data/lib/repull/models/import_from_channex200_response_data_summary_properties.rb +1 -1
  335. data/lib/repull/models/import_from_channex_request.rb +1 -1
  336. data/lib/repull/models/inquiry_created_event.rb +1 -1
  337. data/lib/repull/models/inquiry_created_payload.rb +1 -1
  338. data/lib/repull/models/inquiry_updated_event.rb +1 -1
  339. data/lib/repull/models/inquiry_updated_payload.rb +1 -1
  340. data/lib/repull/models/inquiry_webhook_object.rb +1 -1
  341. data/lib/repull/models/inquiry_webhook_object_expected_payout.rb +1 -1
  342. data/lib/repull/models/inquiry_webhook_object_guest.rb +1 -1
  343. data/lib/repull/models/inquiry_webhook_object_guests.rb +1 -1
  344. data/lib/repull/models/invite_booking_extranet_user200_response.rb +1 -1
  345. data/lib/repull/models/invite_booking_extranet_user_request.rb +1 -1
  346. data/lib/repull/models/list_airbnb_alterations200_response.rb +1 -1
  347. data/lib/repull/models/list_airbnb_listing_amenities200_response.rb +1 -1
  348. data/lib/repull/models/list_airbnb_listing_amenities200_response_data.rb +1 -1
  349. data/lib/repull/models/list_airbnb_listing_permits200_response.rb +1 -1
  350. data/lib/repull/models/list_airbnb_listing_safety_disclosures200_response.rb +1 -1
  351. data/lib/repull/models/list_airbnb_resolutions200_response.rb +1 -1
  352. data/lib/repull/models/list_airbnb_thread_messages200_response.rb +1 -1
  353. data/lib/repull/models/list_airbnb_thread_messages200_response_data_inner.rb +1 -1
  354. data/lib/repull/models/list_airbnb_thread_messages200_response_pagination.rb +1 -1
  355. data/lib/repull/models/list_airbnb_transactions200_response.rb +1 -1
  356. data/lib/repull/models/list_booking_reservations200_response.rb +1 -1
  357. data/lib/repull/models/list_booking_transactions200_response.rb +1 -1
  358. data/lib/repull/models/list_connection_imports200_response.rb +1 -1
  359. data/lib/repull/models/list_connection_units200_response.rb +1 -1
  360. data/lib/repull/models/list_connection_units200_response_listing_options_inner.rb +1 -1
  361. data/lib/repull/models/list_connection_units200_response_units_inner.rb +1 -1
  362. data/lib/repull/models/list_hotels200_response.rb +1 -1
  363. data/lib/repull/models/list_hotels200_response_data_inner.rb +1 -1
  364. data/lib/repull/models/list_inquiries200_response.rb +1 -1
  365. data/lib/repull/models/list_inquiries200_response_data_inner.rb +1 -1
  366. data/lib/repull/models/list_inquiries200_response_data_inner_expected_payout.rb +1 -1
  367. data/lib/repull/models/list_inquiries200_response_data_inner_guest.rb +1 -1
  368. data/lib/repull/models/list_inquiries200_response_data_inner_guests.rb +1 -1
  369. data/lib/repull/models/list_kv200_response.rb +1 -1
  370. data/lib/repull/models/list_kv200_response_data_inner.rb +1 -1
  371. data/lib/repull/models/list_kv200_response_pagination.rb +1 -1
  372. data/lib/repull/models/list_listing_units200_response.rb +1 -1
  373. data/lib/repull/models/list_listing_units200_response_data_inner.rb +1 -1
  374. data/lib/repull/models/list_migrations200_response.rb +1 -1
  375. data/lib/repull/models/list_workspaces200_response.rb +1 -1
  376. data/lib/repull/models/listing.rb +1 -1
  377. data/lib/repull/models/listing_active_request.rb +1 -1
  378. data/lib/repull/models/listing_active_response.rb +1 -1
  379. data/lib/repull/models/listing_address.rb +1 -1
  380. data/lib/repull/models/listing_address_readiness.rb +1 -1
  381. data/lib/repull/models/listing_amenity.rb +1 -1
  382. data/lib/repull/models/listing_capabilities.rb +1 -1
  383. data/lib/repull/models/listing_channel.rb +1 -1
  384. data/lib/repull/models/listing_comp.rb +1 -1
  385. data/lib/repull/models/listing_comp_nightly.rb +1 -1
  386. data/lib/repull/models/listing_comp_ratings.rb +1 -1
  387. data/lib/repull/models/listing_comps_response.rb +1 -1
  388. data/lib/repull/models/listing_content.rb +1 -1
  389. data/lib/repull/models/listing_content_photo.rb +1 -1
  390. data/lib/repull/models/listing_content_update_request.rb +1 -1
  391. data/lib/repull/models/listing_content_update_request_address.rb +1 -1
  392. data/lib/repull/models/listing_content_update_request_amenities.rb +1 -1
  393. data/lib/repull/models/listing_content_update_request_amenities_one_of_inner.rb +1 -1
  394. data/lib/repull/models/listing_content_update_request_checkout_tasks_inner.rb +1 -1
  395. data/lib/repull/models/listing_content_update_request_details.rb +1 -1
  396. data/lib/repull/models/listing_content_update_request_occupancy.rb +1 -1
  397. data/lib/repull/models/listing_content_update_request_photos_inner.rb +1 -1
  398. data/lib/repull/models/listing_content_update_request_photos_inner_one_of.rb +1 -1
  399. data/lib/repull/models/listing_content_update_request_policies.rb +1 -1
  400. data/lib/repull/models/listing_content_update_request_pricing.rb +1 -1
  401. data/lib/repull/models/listing_content_update_request_rooms_inner.rb +1 -1
  402. data/lib/repull/models/listing_content_update_request_rooms_inner_beds_inner.rb +1 -1
  403. data/lib/repull/models/listing_content_update_response.rb +1 -1
  404. data/lib/repull/models/listing_content_update_response_pms.rb +1 -1
  405. data/lib/repull/models/listing_content_update_response_pms_errors_inner.rb +1 -1
  406. data/lib/repull/models/listing_create_request.rb +1 -1
  407. data/lib/repull/models/listing_create_response.rb +1 -1
  408. data/lib/repull/models/listing_created_event.rb +1 -1
  409. data/lib/repull/models/listing_created_payload.rb +1 -1
  410. data/lib/repull/models/listing_created_payload_address.rb +1 -1
  411. data/lib/repull/models/listing_deleted_event.rb +1 -1
  412. data/lib/repull/models/listing_deleted_payload.rb +1 -1
  413. data/lib/repull/models/listing_details.rb +1 -1
  414. data/lib/repull/models/listing_fee.rb +1 -1
  415. data/lib/repull/models/listing_generate_content_request.rb +1 -1
  416. data/lib/repull/models/listing_generate_content_response.rb +1 -1
  417. data/lib/repull/models/listing_hotel.rb +1 -1
  418. data/lib/repull/models/listing_list_response.rb +1 -1
  419. data/lib/repull/models/listing_market_state_request.rb +1 -1
  420. data/lib/repull/models/listing_market_state_response.rb +1 -1
  421. data/lib/repull/models/listing_parent.rb +1 -1
  422. data/lib/repull/models/listing_photo.rb +1 -1
  423. data/lib/repull/models/listing_photo_delete_request.rb +1 -1
  424. data/lib/repull/models/listing_photo_delete_response.rb +1 -1
  425. data/lib/repull/models/listing_photo_upload_url_request.rb +1 -1
  426. data/lib/repull/models/listing_photo_upload_url_response.rb +1 -1
  427. data/lib/repull/models/listing_photos_response.rb +1 -1
  428. data/lib/repull/models/listing_policies.rb +1 -1
  429. data/lib/repull/models/listing_policies_check_in.rb +1 -1
  430. data/lib/repull/models/listing_policies_check_out.rb +1 -1
  431. data/lib/repull/models/listing_policies_quiet_hours.rb +1 -1
  432. data/lib/repull/models/listing_pricing_apply_request.rb +1 -1
  433. data/lib/repull/models/listing_pricing_apply_response.rb +1 -1
  434. data/lib/repull/models/listing_pricing_history_entry.rb +1 -1
  435. data/lib/repull/models/listing_pricing_history_response.rb +1 -1
  436. data/lib/repull/models/listing_pricing_recommendation.rb +1 -1
  437. data/lib/repull/models/listing_pricing_response.rb +1 -1
  438. data/lib/repull/models/listing_pricing_response_comp_summary.rb +1 -1
  439. data/lib/repull/models/listing_pricing_response_date_range.rb +1 -1
  440. data/lib/repull/models/listing_pricing_response_listing.rb +1 -1
  441. data/lib/repull/models/listing_pricing_settings.rb +1 -1
  442. data/lib/repull/models/listing_pricing_strategy.rb +1 -1
  443. data/lib/repull/models/listing_pricing_strategy_input.rb +1 -1
  444. data/lib/repull/models/listing_publish_airbnb_request.rb +1 -1
  445. data/lib/repull/models/listing_publish_airbnb_response.rb +1 -1
  446. data/lib/repull/models/listing_publish_booking_request.rb +1 -1
  447. data/lib/repull/models/listing_publish_booking_response.rb +1 -1
  448. data/lib/repull/models/listing_publish_status_channel.rb +1 -1
  449. data/lib/repull/models/listing_publish_status_connection.rb +1 -1
  450. data/lib/repull/models/listing_publish_status_response.rb +1 -1
  451. data/lib/repull/models/listing_pull_airbnb_request.rb +1 -1
  452. data/lib/repull/models/listing_pull_response.rb +1 -1
  453. data/lib/repull/models/listing_quality_tier.rb +1 -1
  454. data/lib/repull/models/listing_reactivated_event.rb +1 -1
  455. data/lib/repull/models/listing_room.rb +1 -1
  456. data/lib/repull/models/listing_room_beds_inner.rb +1 -1
  457. data/lib/repull/models/listing_rules.rb +1 -1
  458. data/lib/repull/models/listing_segment.rb +1 -1
  459. data/lib/repull/models/listing_segment_recommendation.rb +1 -1
  460. data/lib/repull/models/listing_segments_response.rb +1 -1
  461. data/lib/repull/models/listing_segments_response_scope.rb +1 -1
  462. data/lib/repull/models/listing_status_batch_request.rb +1 -1
  463. data/lib/repull/models/listing_status_batch_response.rb +1 -1
  464. data/lib/repull/models/listing_suspended_event.rb +1 -1
  465. data/lib/repull/models/listing_suspension_payload.rb +1 -1
  466. data/lib/repull/models/listing_tax.rb +1 -1
  467. data/lib/repull/models/listing_units_inner.rb +1 -1
  468. data/lib/repull/models/listing_updated_event.rb +1 -1
  469. data/lib/repull/models/listing_updated_payload.rb +1 -1
  470. data/lib/repull/models/listing_webhook_object.rb +1 -1
  471. data/lib/repull/models/listing_webhook_object_address.rb +1 -1
  472. data/lib/repull/models/listing_webhook_object_channels_inner.rb +1 -1
  473. data/lib/repull/models/map_airbnb_listing_request.rb +1 -1
  474. data/lib/repull/models/map_airbnb_listing_response.rb +1 -1
  475. data/lib/repull/models/map_booking_room_request.rb +1 -1
  476. data/lib/repull/models/map_booking_room_response.rb +1 -1
  477. data/lib/repull/models/map_connect_booking_rooms_request.rb +1 -1
  478. data/lib/repull/models/map_connect_booking_rooms_response.rb +1 -1
  479. data/lib/repull/models/market_browse_category.rb +1 -1
  480. data/lib/repull/models/market_browse_entry.rb +1 -1
  481. data/lib/repull/models/market_browse_featured.rb +1 -1
  482. data/lib/repull/models/market_browse_response.rb +1 -1
  483. data/lib/repull/models/market_calendar_day.rb +1 -1
  484. data/lib/repull/models/market_calendar_day_events_inner.rb +1 -1
  485. data/lib/repull/models/market_calendar_response.rb +1 -1
  486. data/lib/repull/models/market_detail_response.rb +1 -1
  487. data/lib/repull/models/market_detail_response_price_distribution_inner.rb +1 -1
  488. data/lib/repull/models/market_detail_response_property_type_mix_inner.rb +1 -1
  489. data/lib/repull/models/market_detail_response_supply_trend_inner.rb +1 -1
  490. data/lib/repull/models/market_detail_response_top_comps.rb +1 -1
  491. data/lib/repull/models/market_event.rb +1 -1
  492. data/lib/repull/models/market_my_listing.rb +1 -1
  493. data/lib/repull/models/market_summary.rb +1 -1
  494. data/lib/repull/models/market_top_comp.rb +1 -1
  495. data/lib/repull/models/markets_overview_response.rb +1 -1
  496. data/lib/repull/models/markets_overview_response_browse.rb +1 -1
  497. data/lib/repull/models/markets_overview_response_subscriptions.rb +1 -1
  498. data/lib/repull/models/markets_overview_response_totals.rb +1 -1
  499. data/lib/repull/models/message.rb +1 -1
  500. data/lib/repull/models/message_actor.rb +1 -1
  501. data/lib/repull/models/message_list_response.rb +1 -1
  502. data/lib/repull/models/message_reaction.rb +1 -1
  503. data/lib/repull/models/migration.rb +1 -1
  504. data/lib/repull/models/migration_channel_map.rb +1 -1
  505. data/lib/repull/models/migration_channel_map_listings_inner.rb +1 -1
  506. data/lib/repull/models/migration_channel_map_listings_inner_airbnb.rb +1 -1
  507. data/lib/repull/models/migration_channel_map_listings_inner_booking.rb +1 -1
  508. data/lib/repull/models/migration_channel_map_sources_inner.rb +1 -1
  509. data/lib/repull/models/migration_completed_event.rb +1 -1
  510. data/lib/repull/models/migration_connections_inner.rb +1 -1
  511. data/lib/repull/models/migration_counts.rb +1 -1
  512. data/lib/repull/models/migration_cutover_check.rb +1 -1
  513. data/lib/repull/models/migration_cutover_check_mismatched_inner.rb +1 -1
  514. data/lib/repull/models/migration_failed_event.rb +1 -1
  515. data/lib/repull/models/migration_import_payload.rb +1 -1
  516. data/lib/repull/models/migration_import_payload_results_inner.rb +1 -1
  517. data/lib/repull/models/migration_import_run.rb +1 -1
  518. data/lib/repull/models/migration_import_run_results_inner.rb +1 -1
  519. data/lib/repull/models/migration_report.rb +1 -1
  520. data/lib/repull/models/migration_report_issues_inner.rb +1 -1
  521. data/lib/repull/models/migration_reservation_ref.rb +1 -1
  522. data/lib/repull/models/pagination.rb +1 -1
  523. data/lib/repull/models/payment_completed_event.rb +1 -1
  524. data/lib/repull/models/payment_completed_payload.rb +1 -1
  525. data/lib/repull/models/payment_refunded_event.rb +1 -1
  526. data/lib/repull/models/payment_refunded_payload.rb +1 -1
  527. data/lib/repull/models/payment_webhook_object.rb +1 -1
  528. data/lib/repull/models/payout_completed_event.rb +1 -1
  529. data/lib/repull/models/payout_completed_payload.rb +1 -1
  530. data/lib/repull/models/plan_notice.rb +1 -1
  531. data/lib/repull/models/pms_capabilities.rb +1 -1
  532. data/lib/repull/models/pms_capabilities_calendar.rb +1 -1
  533. data/lib/repull/models/pms_capabilities_conversations.rb +1 -1
  534. data/lib/repull/models/pms_capabilities_guests.rb +1 -1
  535. data/lib/repull/models/pms_capabilities_listings.rb +1 -1
  536. data/lib/repull/models/pms_capabilities_payments.rb +1 -1
  537. data/lib/repull/models/pms_capabilities_reservations.rb +1 -1
  538. data/lib/repull/models/pms_capabilities_reviews.rb +1 -1
  539. data/lib/repull/models/pms_capabilities_tasks.rb +1 -1
  540. data/lib/repull/models/pms_write_policy.rb +1 -1
  541. data/lib/repull/models/pms_write_policy_calendar.rb +1 -1
  542. data/lib/repull/models/pms_write_policy_reservations.rb +1 -1
  543. data/lib/repull/models/postal_address.rb +1 -1
  544. data/lib/repull/models/preapprove_conversation201_response.rb +1 -1
  545. data/lib/repull/models/preapprove_conversation_request.rb +1 -1
  546. data/lib/repull/models/preview_conversation_special_offer_request.rb +1 -1
  547. data/lib/repull/models/preview_conversation_special_offer_request_fees_inner.rb +1 -1
  548. data/lib/repull/models/preview_conversation_special_offer_request_guests.rb +1 -1
  549. data/lib/repull/models/promotion.rb +1 -1
  550. data/lib/repull/models/promotion_applies_to.rb +1 -1
  551. data/lib/repull/models/promotion_bulk_request.rb +1 -1
  552. data/lib/repull/models/promotion_bulk_response.rb +1 -1
  553. data/lib/repull/models/promotion_bulk_response_data_inner.rb +1 -1
  554. data/lib/repull/models/promotion_bulk_response_data_inner_error.rb +1 -1
  555. data/lib/repull/models/promotion_bulk_response_summary.rb +1 -1
  556. data/lib/repull/models/promotion_catalog.rb +1 -1
  557. data/lib/repull/models/promotion_catalog_channels_inner.rb +1 -1
  558. data/lib/repull/models/promotion_catalog_entry.rb +1 -1
  559. data/lib/repull/models/promotion_catalog_field.rb +1 -1
  560. data/lib/repull/models/promotion_catalog_field_options_inner.rb +1 -1
  561. data/lib/repull/models/promotion_catalog_response.rb +1 -1
  562. data/lib/repull/models/promotion_create_request.rb +1 -1
  563. data/lib/repull/models/promotion_delete_response.rb +1 -1
  564. data/lib/repull/models/promotion_delete_response_data.rb +1 -1
  565. data/lib/repull/models/promotion_discount.rb +1 -1
  566. data/lib/repull/models/promotion_input.rb +1 -1
  567. data/lib/repull/models/promotion_list_response.rb +1 -1
  568. data/lib/repull/models/promotion_refresh_response.rb +1 -1
  569. data/lib/repull/models/promotion_response.rb +1 -1
  570. data/lib/repull/models/promotion_rules.rb +1 -1
  571. data/lib/repull/models/promotion_rules_blackout_dates_quota.rb +1 -1
  572. data/lib/repull/models/promotion_rules_booking_window.rb +1 -1
  573. data/lib/repull/models/promotion_rules_last_minute.rb +1 -1
  574. data/lib/repull/models/promotion_rules_stay_window.rb +1 -1
  575. data/lib/repull/models/promotion_type.rb +1 -1
  576. data/lib/repull/models/promotion_update_request.rb +1 -1
  577. data/lib/repull/models/promotion_usage.rb +1 -1
  578. data/lib/repull/models/promotion_usage_revenue.rb +1 -1
  579. data/lib/repull/models/property.rb +1 -1
  580. data/lib/repull/models/property_availability.rb +1 -1
  581. data/lib/repull/models/property_availability_coverage.rb +1 -1
  582. data/lib/repull/models/property_availability_day.rb +1 -1
  583. data/lib/repull/models/property_availability_unit.rb +1 -1
  584. data/lib/repull/models/property_list_response.rb +1 -1
  585. data/lib/repull/models/publish_listing_to_vrbo_request.rb +1 -1
  586. data/lib/repull/models/publish_section_error.rb +1 -1
  587. data/lib/repull/models/quote.rb +1 -1
  588. data/lib/repull/models/quote_pricing.rb +1 -1
  589. data/lib/repull/models/recheck_booking_extranet_login200_response.rb +1 -1
  590. data/lib/repull/models/recheck_booking_extranet_login_request.rb +1 -1
  591. data/lib/repull/models/record_account.rb +1 -1
  592. data/lib/repull/models/refresh_airbnb_resolutions200_response.rb +1 -1
  593. data/lib/repull/models/refresh_airbnb_resolutions200_response_accounts_inner.rb +1 -1
  594. data/lib/repull/models/refresh_airbnb_resolutions200_response_accounts_inner_error.rb +1 -1
  595. data/lib/repull/models/refresh_airbnb_resolutions_request.rb +1 -1
  596. data/lib/repull/models/reorder_airbnb_listing_photos200_response.rb +1 -1
  597. data/lib/repull/models/reorder_airbnb_listing_photos200_response_data.rb +1 -1
  598. data/lib/repull/models/reorder_airbnb_listing_photos_request.rb +1 -1
  599. data/lib/repull/models/replay_webhook_delivery_request.rb +1 -1
  600. data/lib/repull/models/reply_booking_review200_response.rb +1 -1
  601. data/lib/repull/models/reply_booking_review_request.rb +1 -1
  602. data/lib/repull/models/reply_to_review201_response.rb +1 -1
  603. data/lib/repull/models/reply_to_review_request.rb +1 -1
  604. data/lib/repull/models/repull_ping_event.rb +1 -1
  605. data/lib/repull/models/repull_ping_payload.rb +1 -1
  606. data/lib/repull/models/reservation.rb +1 -1
  607. data/lib/repull/models/reservation_access_code.rb +1 -1
  608. data/lib/repull/models/reservation_access_code_locks_inner.rb +1 -1
  609. data/lib/repull/models/reservation_alteration_created_event.rb +1 -1
  610. data/lib/repull/models/reservation_alteration_created_payload.rb +1 -1
  611. data/lib/repull/models/reservation_alteration_responded_event.rb +1 -1
  612. data/lib/repull/models/reservation_alteration_responded_payload.rb +1 -1
  613. data/lib/repull/models/reservation_cancelled_event.rb +1 -1
  614. data/lib/repull/models/reservation_cancelled_payload.rb +1 -1
  615. data/lib/repull/models/reservation_capabilities.rb +1 -1
  616. data/lib/repull/models/reservation_create_request.rb +1 -1
  617. data/lib/repull/models/reservation_create_response.rb +1 -1
  618. data/lib/repull/models/reservation_create_response_unit.rb +1 -1
  619. data/lib/repull/models/reservation_created_event.rb +1 -1
  620. data/lib/repull/models/reservation_created_payload.rb +1 -1
  621. data/lib/repull/models/reservation_financials.rb +1 -1
  622. data/lib/repull/models/reservation_guest_financials.rb +1 -1
  623. data/lib/repull/models/reservation_guest_input.rb +1 -1
  624. data/lib/repull/models/reservation_host_financials.rb +1 -1
  625. data/lib/repull/models/reservation_list_response.rb +1 -1
  626. data/lib/repull/models/reservation_message_reaction_event.rb +1 -1
  627. data/lib/repull/models/reservation_message_reaction_payload.rb +1 -1
  628. data/lib/repull/models/reservation_message_reaction_payload_reaction.rb +1 -1
  629. data/lib/repull/models/reservation_message_read_event.rb +1 -1
  630. data/lib/repull/models/reservation_message_read_payload.rb +1 -1
  631. data/lib/repull/models/reservation_message_received_event.rb +1 -1
  632. data/lib/repull/models/reservation_message_received_payload.rb +166 -6
  633. data/lib/repull/models/reservation_message_received_payload_from.rb +3 -2
  634. data/lib/repull/models/reservation_message_sent_event.rb +1 -1
  635. data/lib/repull/models/reservation_message_sent_payload.rb +110 -16
  636. data/lib/repull/models/reservation_message_sent_payload_from.rb +1 -1
  637. data/lib/repull/models/reservation_message_updated_event.rb +1 -1
  638. data/lib/repull/models/reservation_message_updated_payload.rb +132 -11
  639. data/lib/repull/models/reservation_message_updated_payload_from.rb +1 -1
  640. data/lib/repull/models/reservation_money_line.rb +1 -1
  641. data/lib/repull/models/reservation_occupancy.rb +1 -1
  642. data/lib/repull/models/reservation_pms_outcome.rb +1 -1
  643. data/lib/repull/models/reservation_pms_outcome_quote.rb +1 -1
  644. data/lib/repull/models/reservation_pms_section_error.rb +1 -1
  645. data/lib/repull/models/reservation_primary_guest.rb +1 -1
  646. data/lib/repull/models/reservation_quote_request.rb +1 -1
  647. data/lib/repull/models/reservation_quote_response.rb +1 -1
  648. data/lib/repull/models/reservation_quote_response_breakdown.rb +1 -1
  649. data/lib/repull/models/reservation_request_created_event.rb +1 -1
  650. data/lib/repull/models/reservation_request_created_payload.rb +1 -1
  651. data/lib/repull/models/reservation_request_updated_event.rb +1 -1
  652. data/lib/repull/models/reservation_request_updated_payload.rb +1 -1
  653. data/lib/repull/models/reservation_thread_assigned_event.rb +1 -1
  654. data/lib/repull/models/reservation_thread_assigned_payload.rb +1 -1
  655. data/lib/repull/models/reservation_thread_assigned_payload_object.rb +1 -1
  656. data/lib/repull/models/reservation_unit.rb +1 -1
  657. data/lib/repull/models/reservation_update_request.rb +1 -1
  658. data/lib/repull/models/reservation_update_response.rb +1 -1
  659. data/lib/repull/models/reservation_updated_event.rb +1 -1
  660. data/lib/repull/models/reservation_updated_payload.rb +1 -1
  661. data/lib/repull/models/reservation_webhook_object.rb +1 -1
  662. data/lib/repull/models/resolution.rb +1 -1
  663. data/lib/repull/models/respond_airbnb_review_request.rb +1 -1
  664. data/lib/repull/models/resume_connect400_response.rb +1 -1
  665. data/lib/repull/models/resume_connect500_response.rb +1 -1
  666. data/lib/repull/models/review.rb +1 -1
  667. data/lib/repull/models/review_category.rb +1 -1
  668. data/lib/repull/models/review_created_event.rb +1 -1
  669. data/lib/repull/models/review_created_payload.rb +1 -1
  670. data/lib/repull/models/review_list_response.rb +1 -1
  671. data/lib/repull/models/review_responded_event.rb +1 -1
  672. data/lib/repull/models/review_responded_payload.rb +1 -1
  673. data/lib/repull/models/review_response.rb +1 -1
  674. data/lib/repull/models/review_webhook_object.rb +1 -1
  675. data/lib/repull/models/rotate_webhook_secret200_response.rb +1 -1
  676. data/lib/repull/models/run_migration_import202_response.rb +1 -1
  677. data/lib/repull/models/run_migration_import202_response_data.rb +1 -1
  678. data/lib/repull/models/run_migration_import202_response_data_queued_inner.rb +1 -1
  679. data/lib/repull/models/run_migration_import_request.rb +1 -1
  680. data/lib/repull/models/search_connect_session_listing_options200_response.rb +1 -1
  681. data/lib/repull/models/search_connect_session_listing_options200_response_data_inner.rb +1 -1
  682. data/lib/repull/models/search_connection_listing_options200_response.rb +1 -1
  683. data/lib/repull/models/select_connect_provider_request.rb +1 -1
  684. data/lib/repull/models/select_provider_response.rb +1 -1
  685. data/lib/repull/models/send_airbnb_message201_response.rb +1 -1
  686. data/lib/repull/models/send_airbnb_message_request.rb +1 -1
  687. data/lib/repull/models/send_booking_message_request.rb +1 -1
  688. data/lib/repull/models/send_message_attachment.rb +1 -1
  689. data/lib/repull/models/send_message_part.rb +1 -1
  690. data/lib/repull/models/send_message_request.rb +1 -1
  691. data/lib/repull/models/send_message_response.rb +1 -1
  692. data/lib/repull/models/sent_attachment.rb +1 -1
  693. data/lib/repull/models/set_airbnb_listing_cover_photo200_response.rb +1 -1
  694. data/lib/repull/models/set_airbnb_listing_cover_photo200_response_data.rb +1 -1
  695. data/lib/repull/models/set_airbnb_listing_cover_photo_request.rb +1 -1
  696. data/lib/repull/models/set_kv_request.rb +1 -1
  697. data/lib/repull/models/set_listing_markup_request.rb +1 -1
  698. data/lib/repull/models/start_booking_extranet_login200_response.rb +1 -1
  699. data/lib/repull/models/start_booking_extranet_login_request.rb +1 -1
  700. data/lib/repull/models/submit_beds24_credentials200_response.rb +1 -1
  701. data/lib/repull/models/submit_beds24_credentials_request.rb +1 -1
  702. data/lib/repull/models/submit_bookingsync_credentials_request.rb +1 -1
  703. data/lib/repull/models/submit_ciirus_credentials200_response.rb +1 -1
  704. data/lib/repull/models/submit_ciirus_credentials200_response_account_info.rb +1 -1
  705. data/lib/repull/models/submit_ciirus_credentials_request.rb +1 -1
  706. data/lib/repull/models/submit_ciirus_credentials_request_credentials.rb +1 -1
  707. data/lib/repull/models/submit_cloudbeds_credentials200_response.rb +1 -1
  708. data/lib/repull/models/submit_cloudbeds_credentials200_response_account_info.rb +1 -1
  709. data/lib/repull/models/submit_cloudbeds_credentials200_response_webhooks.rb +1 -1
  710. data/lib/repull/models/submit_cloudbeds_credentials_request.rb +1 -1
  711. data/lib/repull/models/submit_cloudbeds_credentials_request_credentials.rb +1 -1
  712. data/lib/repull/models/submit_guest_review200_response.rb +1 -1
  713. data/lib/repull/models/submit_guesty_credentials_request.rb +1 -1
  714. data/lib/repull/models/submit_hospitable_credentials_request.rb +1 -1
  715. data/lib/repull/models/submit_hostaway_credentials_request.rb +1 -1
  716. data/lib/repull/models/submit_igms_credentials_request.rb +1 -1
  717. data/lib/repull/models/submit_lodgify_credentials_request.rb +1 -1
  718. data/lib/repull/models/submit_mews_credentials200_response.rb +1 -1
  719. data/lib/repull/models/submit_mews_credentials200_response_account_info.rb +1 -1
  720. data/lib/repull/models/submit_mews_credentials_request.rb +1 -1
  721. data/lib/repull/models/submit_mews_credentials_request_credentials.rb +1 -1
  722. data/lib/repull/models/submit_ownerrez_credentials_request.rb +1 -1
  723. data/lib/repull/models/submit_smoobu_credentials_request.rb +1 -1
  724. data/lib/repull/models/submit_smoobu_credentials_request_credentials.rb +1 -1
  725. data/lib/repull/models/submit_track_credentials200_response.rb +1 -1
  726. data/lib/repull/models/submit_track_credentials200_response_account_info.rb +1 -1
  727. data/lib/repull/models/submit_track_credentials200_response_first_sync.rb +1 -1
  728. data/lib/repull/models/submit_track_credentials_request.rb +1 -1
  729. data/lib/repull/models/submit_track_credentials_request_credentials.rb +1 -1
  730. data/lib/repull/models/submit_vrbo_credentials_request.rb +1 -1
  731. data/lib/repull/models/sync_airbnb_transactions200_response.rb +1 -1
  732. data/lib/repull/models/sync_airbnb_transactions200_response_accounts_inner.rb +1 -1
  733. data/lib/repull/models/sync_airbnb_transactions200_response_accounts_inner_error.rb +1 -1
  734. data/lib/repull/models/sync_airbnb_transactions_request.rb +1 -1
  735. data/lib/repull/models/test_webhook_request.rb +1 -1
  736. data/lib/repull/models/transaction.rb +1 -1
  737. data/lib/repull/models/transaction_fees.rb +1 -1
  738. data/lib/repull/models/transaction_payout.rb +1 -1
  739. data/lib/repull/models/update_airbnb_booking_settings200_response.rb +1 -1
  740. data/lib/repull/models/update_airbnb_booking_settings200_response_data.rb +1 -1
  741. data/lib/repull/models/update_airbnb_booking_settings_request.rb +1 -1
  742. data/lib/repull/models/update_airbnb_booking_settings_request_advance_notice.rb +1 -1
  743. data/lib/repull/models/update_airbnb_booking_settings_request_booking_window.rb +1 -1
  744. data/lib/repull/models/update_airbnb_booking_settings_request_cancellation.rb +1 -1
  745. data/lib/repull/models/update_airbnb_booking_settings_request_cancellation_non_refundable.rb +1 -1
  746. data/lib/repull/models/update_airbnb_booking_settings_request_check_in.rb +1 -1
  747. data/lib/repull/models/update_airbnb_booking_settings_request_check_out.rb +1 -1
  748. data/lib/repull/models/update_airbnb_booking_settings_request_instant_book.rb +1 -1
  749. data/lib/repull/models/update_airbnb_booking_settings_request_preparation_time.rb +1 -1
  750. data/lib/repull/models/update_airbnb_checkin_guide200_response.rb +1 -1
  751. data/lib/repull/models/update_airbnb_checkin_guide200_response_data.rb +1 -1
  752. data/lib/repull/models/update_airbnb_checkin_guide200_response_data_steps_inner.rb +1 -1
  753. data/lib/repull/models/update_airbnb_checkin_guide_request.rb +1 -1
  754. data/lib/repull/models/update_airbnb_checkin_guide_request_steps_inner.rb +1 -1
  755. data/lib/repull/models/update_airbnb_listing_amenities200_response.rb +1 -1
  756. data/lib/repull/models/update_airbnb_listing_amenities200_response_data.rb +1 -1
  757. data/lib/repull/models/update_airbnb_listing_amenities_request.rb +1 -1
  758. data/lib/repull/models/update_airbnb_listing_amenities_request_accessibility_amenities_inner.rb +1 -1
  759. data/lib/repull/models/update_airbnb_listing_amenities_request_amenities_inner.rb +1 -1
  760. data/lib/repull/models/update_airbnb_listing_permits200_response.rb +1 -1
  761. data/lib/repull/models/update_airbnb_listing_photo200_response.rb +1 -1
  762. data/lib/repull/models/update_airbnb_listing_photo_request.rb +1 -1
  763. data/lib/repull/models/update_airbnb_listing_room200_response.rb +1 -1
  764. data/lib/repull/models/update_airbnb_listing_room_request.rb +1 -1
  765. data/lib/repull/models/update_airbnb_listing_room_request_beds_inner.rb +1 -1
  766. data/lib/repull/models/update_airbnb_listing_room_request_room_amenities_inner.rb +1 -1
  767. data/lib/repull/models/update_airbnb_listing_room_request_room_amenities_inner_value.rb +1 -1
  768. data/lib/repull/models/update_airbnb_listing_safety_disclosures200_response.rb +1 -1
  769. data/lib/repull/models/update_airbnb_message_request.rb +1 -1
  770. data/lib/repull/models/update_booking_availability200_response.rb +1 -1
  771. data/lib/repull/models/update_booking_charges_request.rb +1 -1
  772. data/lib/repull/models/update_booking_content_request.rb +1 -1
  773. data/lib/repull/models/update_booking_content_request_content_data_inner.rb +1 -1
  774. data/lib/repull/models/update_booking_content_request_photos_inner.rb +1 -1
  775. data/lib/repull/models/update_connect_write_policy_request.rb +1 -1
  776. data/lib/repull/models/update_connect_write_policy_request_calendar.rb +1 -1
  777. data/lib/repull/models/update_connect_write_policy_request_reservations.rb +1 -1
  778. data/lib/repull/models/update_listing_pricing_strategy200_response.rb +1 -1
  779. data/lib/repull/models/update_webhook_request.rb +1 -1
  780. data/lib/repull/models/upload_airbnb_listing_photos_request.rb +1 -1
  781. data/lib/repull/models/upload_airbnb_listing_photos_request_photos_inner.rb +1 -1
  782. data/lib/repull/models/upload_airbnb_listing_photos_request_photos_inner_listing_id.rb +1 -1
  783. data/lib/repull/models/usage_quota_warning_event.rb +1 -1
  784. data/lib/repull/models/usage_quota_warning_payload.rb +1 -1
  785. data/lib/repull/models/usage_quota_warning_payload_top_operation.rb +1 -1
  786. data/lib/repull/models/vrbo_import_status.rb +1 -1
  787. data/lib/repull/models/vrbo_listing.rb +1 -1
  788. data/lib/repull/models/vrbo_login200_response.rb +1 -1
  789. data/lib/repull/models/vrbo_login_request.rb +1 -1
  790. data/lib/repull/models/vrbo_reservation.rb +1 -1
  791. data/lib/repull/models/vrbo_reservation_list_response.rb +1 -1
  792. data/lib/repull/models/webhook_delivery.rb +1 -1
  793. data/lib/repull/models/webhook_delivery_detail.rb +1 -1
  794. data/lib/repull/models/webhook_delivery_list_response.rb +1 -1
  795. data/lib/repull/models/webhook_event.rb +1 -1
  796. data/lib/repull/models/webhook_event_account.rb +1 -1
  797. data/lib/repull/models/webhook_event_catalog.rb +1 -1
  798. data/lib/repull/models/webhook_event_catalog_domains_inner.rb +1 -1
  799. data/lib/repull/models/webhook_event_catalog_entry.rb +1 -1
  800. data/lib/repull/models/webhook_event_type.rb +1 -1
  801. data/lib/repull/models/webhook_list_response.rb +1 -1
  802. data/lib/repull/models/webhook_subscription.rb +1 -1
  803. data/lib/repull/models/withdraw_conversation_preapproval200_response.rb +1 -1
  804. data/lib/repull/models/withdraw_conversation_special_offer200_response.rb +1 -1
  805. data/lib/repull/models/workspace.rb +1 -1
  806. data/lib/repull/version.rb +2 -2
  807. data/lib/repull.rb +1 -1
  808. data/openapi/v1.json +198 -14
  809. data/repull.gemspec +2 -2
  810. data/scripts/regen.sh +1 -1
  811. metadata +5 -5
@@ -1,7 +1,7 @@
1
1
  =begin
2
2
  #Repull API
3
3
 
4
- #The unified API for vacation rental tech. Connect to 50+ PMS platforms and 4 OTA channels through one REST API. Built-in AI operations for guest communication, pricing, and listing optimization. ## 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`, and `resetsAt` fields. ## 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 15 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`, and `resetsAt` fields. ## 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\").
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 to 50+ PMS platforms and 4 OTA channels through one REST API. Built-in AI operations for guest communication, pricing, and listing optimization. ## 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`, and `resetsAt` fields. ## 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 15 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`, and `resetsAt` fields. ## 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\").
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 to 50+ PMS platforms and 4 OTA channels through one REST API. Built-in AI operations for guest communication, pricing, and listing optimization. ## 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`, and `resetsAt` fields. ## 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 15 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`, and `resetsAt` fields. ## 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\").
5
5
 
6
6
  The version of the OpenAPI document: 1.0.0
7
7
 
@@ -21,13 +21,20 @@ module Repull
21
21
 
22
22
  attr_accessor :reservation_id
23
23
 
24
+ # The Repull conversation id (numeric, as a string), for `GET /v1/conversations/{id}`.
24
25
  attr_accessor :thread_id
25
26
 
27
+ attr_accessor :external_thread_id
28
+
29
+ attr_accessor :listing_id
30
+
31
+ attr_accessor :channel
32
+
26
33
  attr_accessor :message_id
27
34
 
28
35
  attr_accessor :external_message_id
29
36
 
30
- attr_accessor :channel
37
+ attr_accessor :confirmation_code
31
38
 
32
39
  attr_accessor :from
33
40
 
@@ -45,21 +52,52 @@ module Repull
45
52
 
46
53
  attr_accessor :direction
47
54
 
55
+ attr_accessor :sender_type
56
+
57
+ attr_accessor :sender_name
58
+
59
+ attr_accessor :sender_avatar
60
+
61
+ attr_accessor :translated_body
62
+
63
+ attr_accessor :attachments
64
+
65
+ attr_accessor :is_automated
66
+
67
+ attr_accessor :ai_generated
68
+
69
+ attr_accessor :status
70
+
71
+ # Same as `editedAt`.
72
+ attr_accessor :revision
73
+
48
74
  # Attribute mapping from ruby-style variable name to JSON key.
49
75
  def self.attribute_map
50
76
  {
51
77
  :'hotel_id' => :'hotelId',
52
78
  :'reservation_id' => :'reservationId',
53
79
  :'thread_id' => :'threadId',
80
+ :'external_thread_id' => :'externalThreadId',
81
+ :'listing_id' => :'listingId',
82
+ :'channel' => :'channel',
54
83
  :'message_id' => :'messageId',
55
84
  :'external_message_id' => :'externalMessageId',
56
- :'channel' => :'channel',
85
+ :'confirmation_code' => :'confirmationCode',
57
86
  :'from' => :'from',
58
87
  :'body' => :'body',
59
88
  :'previous_body' => :'previousBody',
60
89
  :'edited_at' => :'editedAt',
61
90
  :'sent_at' => :'sentAt',
62
- :'direction' => :'direction'
91
+ :'direction' => :'direction',
92
+ :'sender_type' => :'senderType',
93
+ :'sender_name' => :'senderName',
94
+ :'sender_avatar' => :'senderAvatar',
95
+ :'translated_body' => :'translatedBody',
96
+ :'attachments' => :'attachments',
97
+ :'is_automated' => :'isAutomated',
98
+ :'ai_generated' => :'aiGenerated',
99
+ :'status' => :'status',
100
+ :'revision' => :'revision'
63
101
  }
64
102
  end
65
103
 
@@ -79,15 +117,27 @@ module Repull
79
117
  :'hotel_id' => :'String',
80
118
  :'reservation_id' => :'Integer',
81
119
  :'thread_id' => :'String',
120
+ :'external_thread_id' => :'String',
121
+ :'listing_id' => :'Integer',
122
+ :'channel' => :'String',
82
123
  :'message_id' => :'String',
83
124
  :'external_message_id' => :'String',
84
- :'channel' => :'String',
125
+ :'confirmation_code' => :'String',
85
126
  :'from' => :'ReservationMessageUpdatedPayloadFrom',
86
127
  :'body' => :'String',
87
128
  :'previous_body' => :'String',
88
129
  :'edited_at' => :'Time',
89
130
  :'sent_at' => :'Time',
90
- :'direction' => :'String'
131
+ :'direction' => :'String',
132
+ :'sender_type' => :'String',
133
+ :'sender_name' => :'String',
134
+ :'sender_avatar' => :'String',
135
+ :'translated_body' => :'String',
136
+ :'attachments' => :'Array<ConversationMessageAttachment>',
137
+ :'is_automated' => :'Boolean',
138
+ :'ai_generated' => :'Boolean',
139
+ :'status' => :'String',
140
+ :'revision' => :'Time'
91
141
  }
92
142
  end
93
143
 
@@ -96,7 +146,16 @@ module Repull
96
146
  Set.new([
97
147
  :'hotel_id',
98
148
  :'reservation_id',
149
+ :'external_thread_id',
150
+ :'listing_id',
99
151
  :'external_message_id',
152
+ :'confirmation_code',
153
+ :'sender_type',
154
+ :'sender_name',
155
+ :'sender_avatar',
156
+ :'translated_body',
157
+ :'status',
158
+ :'revision'
100
159
  ])
101
160
  end
102
161
 
@@ -128,6 +187,18 @@ module Repull
128
187
  self.thread_id = attributes[:'thread_id']
129
188
  end
130
189
 
190
+ if attributes.key?(:'external_thread_id')
191
+ self.external_thread_id = attributes[:'external_thread_id']
192
+ end
193
+
194
+ if attributes.key?(:'listing_id')
195
+ self.listing_id = attributes[:'listing_id']
196
+ end
197
+
198
+ if attributes.key?(:'channel')
199
+ self.channel = attributes[:'channel']
200
+ end
201
+
131
202
  if attributes.key?(:'message_id')
132
203
  self.message_id = attributes[:'message_id']
133
204
  end
@@ -136,8 +207,8 @@ module Repull
136
207
  self.external_message_id = attributes[:'external_message_id']
137
208
  end
138
209
 
139
- if attributes.key?(:'channel')
140
- self.channel = attributes[:'channel']
210
+ if attributes.key?(:'confirmation_code')
211
+ self.confirmation_code = attributes[:'confirmation_code']
141
212
  end
142
213
 
143
214
  if attributes.key?(:'from')
@@ -163,6 +234,44 @@ module Repull
163
234
  if attributes.key?(:'direction')
164
235
  self.direction = attributes[:'direction']
165
236
  end
237
+
238
+ if attributes.key?(:'sender_type')
239
+ self.sender_type = attributes[:'sender_type']
240
+ end
241
+
242
+ if attributes.key?(:'sender_name')
243
+ self.sender_name = attributes[:'sender_name']
244
+ end
245
+
246
+ if attributes.key?(:'sender_avatar')
247
+ self.sender_avatar = attributes[:'sender_avatar']
248
+ end
249
+
250
+ if attributes.key?(:'translated_body')
251
+ self.translated_body = attributes[:'translated_body']
252
+ end
253
+
254
+ if attributes.key?(:'attachments')
255
+ if (value = attributes[:'attachments']).is_a?(Array)
256
+ self.attachments = value
257
+ end
258
+ end
259
+
260
+ if attributes.key?(:'is_automated')
261
+ self.is_automated = attributes[:'is_automated']
262
+ end
263
+
264
+ if attributes.key?(:'ai_generated')
265
+ self.ai_generated = attributes[:'ai_generated']
266
+ end
267
+
268
+ if attributes.key?(:'status')
269
+ self.status = attributes[:'status']
270
+ end
271
+
272
+ if attributes.key?(:'revision')
273
+ self.revision = attributes[:'revision']
274
+ end
166
275
  end
167
276
 
168
277
  # Show invalid properties with the reasons. Usually used together with valid?
@@ -188,15 +297,27 @@ module Repull
188
297
  hotel_id == o.hotel_id &&
189
298
  reservation_id == o.reservation_id &&
190
299
  thread_id == o.thread_id &&
300
+ external_thread_id == o.external_thread_id &&
301
+ listing_id == o.listing_id &&
302
+ channel == o.channel &&
191
303
  message_id == o.message_id &&
192
304
  external_message_id == o.external_message_id &&
193
- channel == o.channel &&
305
+ confirmation_code == o.confirmation_code &&
194
306
  from == o.from &&
195
307
  body == o.body &&
196
308
  previous_body == o.previous_body &&
197
309
  edited_at == o.edited_at &&
198
310
  sent_at == o.sent_at &&
199
- direction == o.direction
311
+ direction == o.direction &&
312
+ sender_type == o.sender_type &&
313
+ sender_name == o.sender_name &&
314
+ sender_avatar == o.sender_avatar &&
315
+ translated_body == o.translated_body &&
316
+ attachments == o.attachments &&
317
+ is_automated == o.is_automated &&
318
+ ai_generated == o.ai_generated &&
319
+ status == o.status &&
320
+ revision == o.revision
200
321
  end
201
322
 
202
323
  # @see the `==` method
@@ -208,7 +329,7 @@ module Repull
208
329
  # Calculates hash code according to all attributes.
209
330
  # @return [Integer] Hash code
210
331
  def hash
211
- [hotel_id, reservation_id, thread_id, message_id, external_message_id, channel, from, body, previous_body, edited_at, sent_at, direction].hash
332
+ [hotel_id, reservation_id, thread_id, external_thread_id, listing_id, channel, message_id, external_message_id, confirmation_code, from, body, previous_body, edited_at, sent_at, direction, sender_type, sender_name, sender_avatar, translated_body, attachments, is_automated, ai_generated, status, revision].hash
212
333
  end
213
334
 
214
335
  # 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 to 50+ PMS platforms and 4 OTA channels through one REST API. Built-in AI operations for guest communication, pricing, and listing optimization. ## 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`, and `resetsAt` fields. ## 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 15 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`, and `resetsAt` fields. ## 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\").
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 to 50+ PMS platforms and 4 OTA channels through one REST API. Built-in AI operations for guest communication, pricing, and listing optimization. ## 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`, and `resetsAt` fields. ## 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 15 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`, and `resetsAt` fields. ## 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\").
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 to 50+ PMS platforms and 4 OTA channels through one REST API. Built-in AI operations for guest communication, pricing, and listing optimization. ## 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`, and `resetsAt` fields. ## 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 15 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`, and `resetsAt` fields. ## 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\").
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 to 50+ PMS platforms and 4 OTA channels through one REST API. Built-in AI operations for guest communication, pricing, and listing optimization. ## 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`, and `resetsAt` fields. ## 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 15 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`, and `resetsAt` fields. ## 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\").
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 to 50+ PMS platforms and 4 OTA channels through one REST API. Built-in AI operations for guest communication, pricing, and listing optimization. ## 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`, and `resetsAt` fields. ## 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 15 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`, and `resetsAt` fields. ## 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\").
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 to 50+ PMS platforms and 4 OTA channels through one REST API. Built-in AI operations for guest communication, pricing, and listing optimization. ## 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`, and `resetsAt` fields. ## 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 15 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`, and `resetsAt` fields. ## 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\").
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 to 50+ PMS platforms and 4 OTA channels through one REST API. Built-in AI operations for guest communication, pricing, and listing optimization. ## 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`, and `resetsAt` fields. ## 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 15 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`, and `resetsAt` fields. ## 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\").
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 to 50+ PMS platforms and 4 OTA channels through one REST API. Built-in AI operations for guest communication, pricing, and listing optimization. ## 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`, and `resetsAt` fields. ## 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 15 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`, and `resetsAt` fields. ## 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\").
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 to 50+ PMS platforms and 4 OTA channels through one REST API. Built-in AI operations for guest communication, pricing, and listing optimization. ## 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`, and `resetsAt` fields. ## 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 15 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`, and `resetsAt` fields. ## 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\").
5
5
 
6
6
  The version of the OpenAPI document: 1.0.0
7
7