wink-sdk-travel-agent 0.0.3__tar.gz → 0.0.4__tar.gz

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.

Potentially problematic release.

This version of wink-sdk-travel-agent might be problematic. Click here for more details.

Files changed (214) hide show
  1. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/PKG-INFO +1 -1
  2. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/README.md +5 -5
  3. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/pyproject.toml +1 -1
  4. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/setup.py +2 -2
  5. wink_sdk_travel_agent-0.0.4/test/test_engine_configuration_theme_colors_agent.py +62 -0
  6. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/__init__.py +3 -3
  7. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/api/travel_agent_api.py +1 -1
  8. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/api_client.py +1 -1
  9. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/configuration.py +3 -3
  10. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/exceptions.py +1 -1
  11. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/__init__.py +2 -2
  12. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/address_agent.py +1 -1
  13. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/agent_booking_request_agent.py +1 -1
  14. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/aggregate_descriptor_agent.py +1 -1
  15. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/ancillary_request_agent.py +1 -1
  16. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/authenticated_user_agent.py +1 -1
  17. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/bed_agent.py +1 -1
  18. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/bedroom_agent.py +1 -1
  19. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/bedroom_configuration_agent.py +1 -1
  20. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/beneficiary_agent.py +5 -3
  21. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/beneficiary_charge_agent.py +1 -1
  22. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/booking_agent.py +10 -10
  23. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/booking_ancillary_agent.py +1 -1
  24. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/booking_confirmations_agent.py +1 -1
  25. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/booking_contract_agent.py +8 -10
  26. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/booking_contract_item_agent.py +1 -1
  27. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/booking_contract_payment_details_agent.py +1 -1
  28. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/booking_itinerary_agent.py +1 -1
  29. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/booking_itinerary_room_configuration_agent.py +1 -1
  30. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/booking_itinerary_room_configuration_child_agent.py +1 -1
  31. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/booking_user_agent.py +1 -1
  32. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/booking_user_request_agent.py +1 -1
  33. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/booking_user_session_agent.py +1 -1
  34. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/booking_view_agent.py +1 -1
  35. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/boolean_response_agent.py +1 -1
  36. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/cancellation_detail_agent.py +1 -1
  37. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/cancellation_policy_agent.py +1 -1
  38. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/cancellation_policy_exception_agent.py +1 -1
  39. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/cancellation_policy_exceptions_agent.py +1 -1
  40. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/child_agent.py +1 -1
  41. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/commissionable_entry_agent.py +1 -1
  42. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/company_agent.py +1 -1
  43. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/company_user_agent.py +1 -1
  44. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/company_view_agent.py +1 -1
  45. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/composite_filter_descriptor_agent.py +1 -1
  46. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/contact_agent.py +1 -1
  47. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/country_agent.py +1 -1
  48. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/create_agent_booking400_response.py +1 -1
  49. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/create_agent_booking_request_agent.py +1 -1
  50. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/custom_monetary_amount.py +1 -1
  51. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/daily_rate_agent.py +1 -1
  52. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/dow_pattern_group_agent.py +1 -1
  53. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/engine_configuration_booking_report_agent.py +41 -5
  54. wink_sdk_travel_agent-0.0.4/wink_sdk_travel_agent/models/engine_configuration_theme_colors_agent.py +108 -0
  55. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/extra_charge_agent.py +1 -1
  56. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/extra_charges_agent.py +1 -1
  57. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/fee_agent.py +1 -1
  58. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/filter_descriptor_agent.py +1 -1
  59. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/general_manager_agent.py +1 -1
  60. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/generic_error_message.py +1 -1
  61. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/geo_json_point_agent.py +1 -1
  62. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/geo_name_agent.py +1 -1
  63. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/group_descriptor_agent.py +1 -1
  64. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/guest_room_agent.py +1 -1
  65. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/guest_user_agent.py +1 -1
  66. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/hotel_on_map_agent.py +1 -1
  67. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/image_attribution_agent.py +1 -1
  68. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/localized_description_agent.py +1 -1
  69. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/localized_price_agent.py +12 -12
  70. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/page_booking_view_agent.py +6 -6
  71. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/pageable_object_agent.py +7 -7
  72. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/payout_agent.py +14 -10
  73. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/payout_fee_agent.py +1 -1
  74. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/pending_refund_agent.py +1 -1
  75. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/personal_agent.py +1 -1
  76. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/pet_info_dto_agent.py +1 -1
  77. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/preferences_agent.py +1 -1
  78. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/profile_agent.py +1 -1
  79. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/profile_user_agent.py +1 -1
  80. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/property_policy_agent.py +1 -1
  81. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/quote_agent.py +2 -2
  82. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/rate_plan_agent.py +1 -1
  83. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/rate_plan_level_fee_agent.py +1 -1
  84. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/refund_agent.py +1 -1
  85. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/reporting_ancillary_agent.py +1 -1
  86. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/reporting_daily_rate_agent.py +1 -1
  87. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/reporting_extra_charge_agent.py +1 -1
  88. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/review_agent.py +1 -1
  89. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/review_answer_agent.py +1 -1
  90. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/review_user_agent.py +1 -1
  91. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/room_configuration_agent.py +1 -1
  92. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/room_stay_agent.py +9 -9
  93. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/simple_date_time_itinerary_agent.py +1 -1
  94. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/simple_description_agent.py +1 -1
  95. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/simple_multimedia_agent.py +1 -1
  96. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/social_agent.py +1 -1
  97. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/sort_descriptor_agent.py +1 -1
  98. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/sort_object.py +1 -1
  99. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/state_agent.py +1 -1
  100. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/stay_rate_agent.py +5 -5
  101. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/sub_country_agent.py +1 -1
  102. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/sub_sub_country_agent.py +1 -1
  103. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/supplier_contract_item_policy_agent.py +1 -1
  104. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/travel_agent_agent.py +1 -1
  105. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/travel_inventory_recognition_agent.py +1 -1
  106. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/upsert_travel_agent_request_agent.py +1 -1
  107. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/rest.py +1 -1
  108. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent.egg-info/PKG-INFO +1 -1
  109. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent.egg-info/SOURCES.txt +2 -0
  110. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/LICENSE +0 -0
  111. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/setup.cfg +0 -0
  112. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_address_agent.py +0 -0
  113. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_agent_booking_request_agent.py +0 -0
  114. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_aggregate_descriptor_agent.py +0 -0
  115. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_ancillary_request_agent.py +0 -0
  116. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_authenticated_user_agent.py +0 -0
  117. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_bed_agent.py +0 -0
  118. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_bedroom_agent.py +0 -0
  119. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_bedroom_configuration_agent.py +0 -0
  120. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_beneficiary_agent.py +0 -0
  121. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_beneficiary_charge_agent.py +0 -0
  122. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_booking_agent.py +0 -0
  123. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_booking_ancillary_agent.py +0 -0
  124. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_booking_confirmations_agent.py +0 -0
  125. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_booking_contract_agent.py +0 -0
  126. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_booking_contract_item_agent.py +0 -0
  127. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_booking_contract_payment_details_agent.py +0 -0
  128. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_booking_itinerary_agent.py +0 -0
  129. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_booking_itinerary_room_configuration_agent.py +0 -0
  130. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_booking_itinerary_room_configuration_child_agent.py +0 -0
  131. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_booking_user_agent.py +0 -0
  132. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_booking_user_request_agent.py +0 -0
  133. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_booking_user_session_agent.py +0 -0
  134. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_booking_view_agent.py +0 -0
  135. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_boolean_response_agent.py +0 -0
  136. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_cancellation_detail_agent.py +0 -0
  137. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_cancellation_policy_agent.py +0 -0
  138. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_cancellation_policy_exception_agent.py +0 -0
  139. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_cancellation_policy_exceptions_agent.py +0 -0
  140. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_child_agent.py +0 -0
  141. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_commissionable_entry_agent.py +0 -0
  142. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_company_agent.py +0 -0
  143. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_company_user_agent.py +0 -0
  144. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_company_view_agent.py +0 -0
  145. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_composite_filter_descriptor_agent.py +0 -0
  146. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_contact_agent.py +0 -0
  147. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_country_agent.py +0 -0
  148. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_create_agent_booking400_response.py +0 -0
  149. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_create_agent_booking_request_agent.py +0 -0
  150. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_custom_monetary_amount.py +0 -0
  151. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_daily_rate_agent.py +0 -0
  152. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_dow_pattern_group_agent.py +0 -0
  153. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_engine_configuration_booking_report_agent.py +0 -0
  154. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_engine_configuration_theme_agent.py +0 -0
  155. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_extra_charge_agent.py +0 -0
  156. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_extra_charges_agent.py +0 -0
  157. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_fee_agent.py +0 -0
  158. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_filter_descriptor_agent.py +0 -0
  159. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_general_manager_agent.py +0 -0
  160. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_generic_error_message.py +0 -0
  161. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_geo_json_point_agent.py +0 -0
  162. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_geo_name_agent.py +0 -0
  163. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_group_descriptor_agent.py +0 -0
  164. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_guest_room_agent.py +0 -0
  165. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_guest_user_agent.py +0 -0
  166. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_hotel_on_map_agent.py +0 -0
  167. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_image_attribution_agent.py +0 -0
  168. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_localized_description_agent.py +0 -0
  169. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_localized_price_agent.py +0 -0
  170. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_page_booking_view_agent.py +0 -0
  171. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_pageable_object_agent.py +0 -0
  172. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_payout_agent.py +0 -0
  173. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_payout_fee_agent.py +0 -0
  174. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_pending_refund_agent.py +0 -0
  175. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_personal_agent.py +0 -0
  176. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_pet_info_dto_agent.py +0 -0
  177. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_preferences_agent.py +0 -0
  178. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_profile_agent.py +0 -0
  179. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_profile_user_agent.py +0 -0
  180. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_property_policy_agent.py +0 -0
  181. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_quote_agent.py +0 -0
  182. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_rate_plan_agent.py +0 -0
  183. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_rate_plan_level_fee_agent.py +0 -0
  184. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_refund_agent.py +0 -0
  185. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_reporting_ancillary_agent.py +0 -0
  186. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_reporting_daily_rate_agent.py +0 -0
  187. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_reporting_extra_charge_agent.py +0 -0
  188. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_review_agent.py +0 -0
  189. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_review_answer_agent.py +0 -0
  190. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_review_user_agent.py +0 -0
  191. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_room_configuration_agent.py +0 -0
  192. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_room_stay_agent.py +0 -0
  193. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_simple_date_time_itinerary_agent.py +0 -0
  194. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_simple_description_agent.py +0 -0
  195. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_simple_multimedia_agent.py +0 -0
  196. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_social_agent.py +0 -0
  197. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_sort_descriptor_agent.py +0 -0
  198. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_sort_object.py +0 -0
  199. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_state_agent.py +0 -0
  200. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_stay_rate_agent.py +0 -0
  201. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_sub_country_agent.py +0 -0
  202. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_sub_sub_country_agent.py +0 -0
  203. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_supplier_contract_item_policy_agent.py +0 -0
  204. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_travel_agent_agent.py +0 -0
  205. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_travel_agent_api.py +0 -0
  206. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_travel_inventory_recognition_agent.py +0 -0
  207. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/test/test_upsert_travel_agent_request_agent.py +0 -0
  208. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/api/__init__.py +0 -0
  209. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/api_response.py +0 -0
  210. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/engine_configuration_theme_agent.py +0 -0
  211. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/py.typed +0 -0
  212. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent.egg-info/dependency_links.txt +0 -0
  213. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent.egg-info/requires.txt +0 -0
  214. {wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent.egg-info/top_level.txt +0 -0
{wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/PKG-INFO RENAMED
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.1
2
2
  Name: wink-sdk-travel-agent
3
- Version: 0.0.3
3
+ Version: 0.0.4
4
4
  Summary: Wink API
5
5
  Home-page: https://github.com/wink-travel/wink-sdk-python.git
6
6
  Author: Bjorn Harvold
{wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/README.md RENAMED
@@ -104,8 +104,8 @@ Browse the endpoints in the left navigation bar to get started.
104
104
 
105
105
  This Python package is automatically generated by the [OpenAPI Generator](https://openapi-generator.tech) project:
106
106
 
107
- - API version: 30.7.10
108
- - Package version: 0.0.3
107
+ - API version: 30.9.11
108
+ - Package version: 0.0.4
109
109
  - Generator version: 7.9.0
110
110
  - Build package: org.openapitools.codegen.languages.PythonClientCodegen
111
111
 
@@ -123,9 +123,9 @@ pip install wink_sdk_travel_agent
123
123
 
124
124
  Or you can install it directly from the repository using:
125
125
  ```sh
126
- pip install git+https://github.com/wink-travel/wink-sdk-python.git@v0.0.3#egg=wink_sdk_travel_agent&subdirectory=wink-sdk-travel-agent
126
+ pip install git+https://github.com/wink-travel/wink-sdk-python.git@v0.0.4#egg=wink_sdk_travel_agent&subdirectory=wink-sdk-travel-agent
127
127
  ```
128
- (you may need to run `pip` with root permission: `sudo pip install git+https://github.com/wink-travel/wink-sdk-python.git@v0.0.3#egg=wink_sdk_travel_agent&subdirectory=wink_sdk_travel_agent`)
128
+ (you may need to run `pip` with root permission: `sudo pip install git+https://github.com/wink-travel/wink-sdk-python.git@v0.0.4#egg=wink_sdk_travel_agent&subdirectory=wink_sdk_travel_agent`)
129
129
 
130
130
  Then import the package:
131
131
  ```python
@@ -251,7 +251,7 @@ Class | Method | HTTP request | Description
251
251
  - [DailyRateAgent](docs/DailyRateAgent.md)
252
252
  - [DowPatternGroupAgent](docs/DowPatternGroupAgent.md)
253
253
  - [EngineConfigurationBookingReportAgent](docs/EngineConfigurationBookingReportAgent.md)
254
- - [EngineConfigurationThemeAgent](docs/EngineConfigurationThemeAgent.md)
254
+ - [EngineConfigurationThemeColorsAgent](docs/EngineConfigurationThemeColorsAgent.md)
255
255
  - [ExtraChargeAgent](docs/ExtraChargeAgent.md)
256
256
  - [ExtraChargesAgent](docs/ExtraChargesAgent.md)
257
257
  - [FeeAgent](docs/FeeAgent.md)
{wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/pyproject.toml RENAMED
@@ -1,6 +1,6 @@
1
1
  [tool.poetry]
2
2
  name = "wink_sdk_travel_agent"
3
- version = "0.0.3"
3
+ version = "0.0.4"
4
4
  description = "Wink API"
5
5
  authors = ["Bjorn Harvold <bjorn@wink.travel>"]
6
6
  license = "NoLicense"
{wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/setup.py RENAMED
@@ -5,7 +5,7 @@
5
5
 
6
6
  # Introduction Welcome to the Wink API - A programmer-friendly way to manage, sell and book travel blocking on the Wink platform. The API gives you all the tools you need to ready your properties and blocking for sale across 1000s of our native sales channels. Integrators, affiliates, travel agents and content creators have the ability search for your travel blocking and promote / sell it in a wide variety of ways. # Integrations We have already integrated with the most well-known channel managers so you don't have to. To see our current integrations, please go to https://extranet.wink.travel and scroll to Connectivity section. Once your properties are set up, you can finish the setup by mapping your property to Wink using your channel manager partner portal. If your properties don't have a channel manager, you can easily manage rates and availability with this API. # Intended Audience Programmers are [most likely] a requirement to start integrating with Wink. Companies and organizations that would most benefit from integrating with us are new and existing travel companies that have relationships with suppliers and that need an advanced system from which to manage their travel blocking and get that same blocking out to as many eyeballs as possible at the lowest price possible. - Hotel chains - Hotel brands - Travel tech companies - Destination sites - Integrators - Aggregators - Destination management companies - Travel agencies - OTAs ## APIs Not every integrator needs every API. For that reason, we have separated APIs into context. ### Test API - [Ping](/ping): The Ping API is a quick test endpoint to verify that your credentials work Wink. ### Common APIs - [Notifications](/notifications): The Notifications API is a way for us to stay in touch with your user, property or affiliate account. - [User Settings](/user-settings): The User Settings API exposes endpoints to allow 3rd party integrators to communicate with Wink. ### Consume APIs Consume endpoints are for developers who want to find existing travel blocking and either book it or use it to advertise through one of their Wink affiliate accounts. - [Configuration](/engine-client): A single endpoint to retrieve whitelabel + customization information for the booking engine. - [Lookup](/lookup): All APIs related to locating blocking by region, locale and property flags. - [Inventory](/blocking): All APIs related to retrieve known travel blocking as it was found using the Lookup API.. - [Booking](/booking): All APIs related to creating bookings on the platform. - [Travel Agent](/travel-agent): The Travel Agent API exposes endpoints to manage agent-facilitated bookings. ### Produce APIs Produce endpoints are for developers who want to create and manage travel blocking. #### Property - [Property registration](/extranet/property/register): As a producer, this is, oftentimes, where you start your journey. These endpoints let you create properties on Wink. - [Property](/extranet/property): This collection of property endpoints are mostly management endpoints that let you display, change status and similar for your existing properties. - [Facilities](/extranet/facilities): This collection of endpoints let you manage facilities; such as room types. - [Experiences](/extranet/experiences): This collection of endpoints let you manage experiences, such as activities. - [Monetize](/extranet/monetize): The Monetize API exposes endpoints for managing cancellation polies, rate plans, promotions and more on Wink. - [Distribution](/extranet/distribution): The Distribution API exposes endpoints for sales channels, connecting with affiliates, managing rates and blocking calendars and more on Wink. - [Property Booking](/extranet/booking): The Property Booking API exposes endpoints for managing bookings and reviews at the property-level. #### Affiliate - [Affiliate](/affiliate): This collection of affiliate endpoints are mostly management endpoints that let you display, change status and similar for your existing accounts. - [Browse](/affiliate/browse): The Browse API exposes endpoints for affiliates to find suppliers and blocking to sell. - [Inventory](/affiliate/blocking): The Inventory API exposes endpoints for affiliates to manage the blocking they want to sell and how they want to sell it. - [Sales Channel](/affiliate/sales-channel): The Sales Channel API exposes endpoints for affiliates to manage existing sales channels as well as find new ones. - [WinkLinks](/affiliate/winklinks): The WinkLinks API exposes endpoints for affiliates to manage their WinkLinks page. #### Rate provider - [Channel manager](/channel-manager): The Channel Manager API enables external channel manager partners to map, exchange rate / availability information with us as well as be informed of bookings that occur on the Wink platform for one of their properties. ### Taxonomy APIs Taxonomy endpoints are for developers who want to consume and produce travel blocking and need taxonomies of standard and non-standard codes for blocking types, classes, statuses etc. - [Reference](/reactive): All APIs related to retrieving platform-supported taxonomies. ### Insight APIs Insight endpoints do exactly what the name implies - They offer platform-level insight into the activities of producers and consumers. - [Analytics](/analytics): All APIs related to tracking metrics across a wide variety of data source segments including, more entertaining, leaderboard metrics. ### Payment APIs Payment endpoints are for developers who want to purchase travel blocking. This can be done via the API as a registered Travel Agent or using our API in conjunction with our PCI compliant reactive widget for all other entities. - [TripPay](/reactive): All APIs related to TripPay account management, booking, mapping and integration features. ## SDKs We are actively working on supporting the most used languages out there. If you don't see your language here, reach out to us with a request to officially add your language. In the meantime, if you want to roll your own SDK, you can do so by downloading the OpenAPI spec and using one of the many available OpenAPI generators available: [https://openapi-generator.tech/docs/generators](https://openapi-generator.tech/docs/generators). - Java SDK [https://github.com/wink-travel/wink-sdk-java](https://github.com/wink-travel/wink-sdk-java) ## Usage These features are made available to you via a [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer). This API is language agnostic. ## Versioning We chose to version our endpoints in a way that we hope affects your integration minimally. You request the version of our API you wish to work with via the `Wink-Version` header. When it's time for you to upgrade, you only have to change the version number to get access to our updated endpoints. ## Release history - Follow updates on Github: https://github.com/wink-travel/wink-sdk-java/blob/master/CHANGELOG.md # Travel Agent API The Travel Agent API exposes endpoints to manage agent-facilitated bookings. This API lets you: 1. Travel Agent: Manage agent entity. 2. Booking: Create / Manage bookings Browse the endpoints in the left navigation bar to get started.
7
7
 
8
- The version of the OpenAPI document: 30.7.10
8
+ The version of the OpenAPI document: 30.9.11
9
9
  Contact: bjorn@wink.travel
10
10
  Generated by OpenAPI Generator (https://openapi-generator.tech)
11
11
 
@@ -22,7 +22,7 @@ from setuptools import setup, find_packages # noqa: H301
22
22
  # prerequisite: setuptools
23
23
  # http://pypi.python.org/pypi/setuptools
24
24
  NAME = "wink-sdk-travel-agent"
25
- VERSION = "0.0.3"
25
+ VERSION = "0.0.4"
26
26
  PYTHON_REQUIRES = ">= 3.8"
27
27
  REQUIRES = [
28
28
  "urllib3 >= 1.25.3, < 3.0.0",
wink_sdk_travel_agent-0.0.4/test/test_engine_configuration_theme_colors_agent.py ADDED
@@ -0,0 +1,62 @@
1
+ # coding: utf-8
2
+
3
+ """
4
+ Wink API
5
+
6
+ # Introduction Welcome to the Wink API - A programmer-friendly way to manage, sell and book travel blocking on the Wink platform. The API gives you all the tools you need to ready your properties and blocking for sale across 1000s of our native sales channels. Integrators, affiliates, travel agents and content creators have the ability search for your travel blocking and promote / sell it in a wide variety of ways. # Integrations We have already integrated with the most well-known channel managers so you don't have to. To see our current integrations, please go to https://extranet.wink.travel and scroll to Connectivity section. Once your properties are set up, you can finish the setup by mapping your property to Wink using your channel manager partner portal. If your properties don't have a channel manager, you can easily manage rates and availability with this API. # Intended Audience Programmers are [most likely] a requirement to start integrating with Wink. Companies and organizations that would most benefit from integrating with us are new and existing travel companies that have relationships with suppliers and that need an advanced system from which to manage their travel blocking and get that same blocking out to as many eyeballs as possible at the lowest price possible. - Hotel chains - Hotel brands - Travel tech companies - Destination sites - Integrators - Aggregators - Destination management companies - Travel agencies - OTAs ## APIs Not every integrator needs every API. For that reason, we have separated APIs into context. ### Test API - [Ping](/ping): The Ping API is a quick test endpoint to verify that your credentials work Wink. ### Common APIs - [Notifications](/notifications): The Notifications API is a way for us to stay in touch with your user, property or affiliate account. - [User Settings](/user-settings): The User Settings API exposes endpoints to allow 3rd party integrators to communicate with Wink. ### Consume APIs Consume endpoints are for developers who want to find existing travel blocking and either book it or use it to advertise through one of their Wink affiliate accounts. - [Configuration](/engine-client): A single endpoint to retrieve whitelabel + customization information for the booking engine. - [Lookup](/lookup): All APIs related to locating blocking by region, locale and property flags. - [Inventory](/blocking): All APIs related to retrieve known travel blocking as it was found using the Lookup API.. - [Booking](/booking): All APIs related to creating bookings on the platform. - [Travel Agent](/travel-agent): The Travel Agent API exposes endpoints to manage agent-facilitated bookings. ### Produce APIs Produce endpoints are for developers who want to create and manage travel blocking. #### Property - [Property registration](/extranet/property/register): As a producer, this is, oftentimes, where you start your journey. These endpoints let you create properties on Wink. - [Property](/extranet/property): This collection of property endpoints are mostly management endpoints that let you display, change status and similar for your existing properties. - [Facilities](/extranet/facilities): This collection of endpoints let you manage facilities; such as room types. - [Experiences](/extranet/experiences): This collection of endpoints let you manage experiences, such as activities. - [Monetize](/extranet/monetize): The Monetize API exposes endpoints for managing cancellation polies, rate plans, promotions and more on Wink. - [Distribution](/extranet/distribution): The Distribution API exposes endpoints for sales channels, connecting with affiliates, managing rates and blocking calendars and more on Wink. - [Property Booking](/extranet/booking): The Property Booking API exposes endpoints for managing bookings and reviews at the property-level. #### Affiliate - [Affiliate](/affiliate): This collection of affiliate endpoints are mostly management endpoints that let you display, change status and similar for your existing accounts. - [Browse](/affiliate/browse): The Browse API exposes endpoints for affiliates to find suppliers and blocking to sell. - [Inventory](/affiliate/blocking): The Inventory API exposes endpoints for affiliates to manage the blocking they want to sell and how they want to sell it. - [Sales Channel](/affiliate/sales-channel): The Sales Channel API exposes endpoints for affiliates to manage existing sales channels as well as find new ones. - [WinkLinks](/affiliate/winklinks): The WinkLinks API exposes endpoints for affiliates to manage their WinkLinks page. #### Rate provider - [Channel manager](/channel-manager): The Channel Manager API enables external channel manager partners to map, exchange rate / availability information with us as well as be informed of bookings that occur on the Wink platform for one of their properties. ### Taxonomy APIs Taxonomy endpoints are for developers who want to consume and produce travel blocking and need taxonomies of standard and non-standard codes for blocking types, classes, statuses etc. - [Reference](/reactive): All APIs related to retrieving platform-supported taxonomies. ### Insight APIs Insight endpoints do exactly what the name implies - They offer platform-level insight into the activities of producers and consumers. - [Analytics](/analytics): All APIs related to tracking metrics across a wide variety of data source segments including, more entertaining, leaderboard metrics. ### Payment APIs Payment endpoints are for developers who want to purchase travel blocking. This can be done via the API as a registered Travel Agent or using our API in conjunction with our PCI compliant reactive widget for all other entities. - [TripPay](/reactive): All APIs related to TripPay account management, booking, mapping and integration features. ## SDKs We are actively working on supporting the most used languages out there. If you don't see your language here, reach out to us with a request to officially add your language. In the meantime, if you want to roll your own SDK, you can do so by downloading the OpenAPI spec and using one of the many available OpenAPI generators available: [https://openapi-generator.tech/docs/generators](https://openapi-generator.tech/docs/generators). - Java SDK [https://github.com/wink-travel/wink-sdk-java](https://github.com/wink-travel/wink-sdk-java) ## Usage These features are made available to you via a [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer). This API is language agnostic. ## Versioning We chose to version our endpoints in a way that we hope affects your integration minimally. You request the version of our API you wish to work with via the `Wink-Version` header. When it's time for you to upgrade, you only have to change the version number to get access to our updated endpoints. ## Release history - Follow updates on Github: https://github.com/wink-travel/wink-sdk-java/blob/master/CHANGELOG.md # Travel Agent API The Travel Agent API exposes endpoints to manage agent-facilitated bookings. This API lets you: 1. Travel Agent: Manage agent entity. 2. Booking: Create / Manage bookings Browse the endpoints in the left navigation bar to get started.
7
+
8
+ The version of the OpenAPI document: 30.9.11
9
+ Contact: bjorn@wink.travel
10
+ Generated by OpenAPI Generator (https://openapi-generator.tech)
11
+
12
+ Do not edit the class manually.
13
+ """ # noqa: E501
14
+
15
+
16
+ import unittest
17
+
18
+ from wink_sdk_travel_agent.models.engine_configuration_theme_colors_agent import EngineConfigurationThemeColorsAgent
19
+
20
+ class TestEngineConfigurationThemeColorsAgent(unittest.TestCase):
21
+ """EngineConfigurationThemeColorsAgent unit test stubs"""
22
+
23
+ def setUp(self):
24
+ pass
25
+
26
+ def tearDown(self):
27
+ pass
28
+
29
+ def make_instance(self, include_optional) -> EngineConfigurationThemeColorsAgent:
30
+ """Test EngineConfigurationThemeColorsAgent
31
+ include_optional is a boolean, when False only required
32
+ params are included, when True both required and
33
+ optional params are included """
34
+ # uncomment below to create an instance of `EngineConfigurationThemeColorsAgent`
35
+ """
36
+ model = EngineConfigurationThemeColorsAgent()
37
+ if include_optional:
38
+ return EngineConfigurationThemeColorsAgent(
39
+ primary = '#dc3545',
40
+ secondary = '#6c757d',
41
+ success = '#28a745',
42
+ danger = '#dc3545',
43
+ warning = '#ffc107',
44
+ info = '#17a2b8',
45
+ light = '#f8f9fa',
46
+ dark = '#343a40',
47
+ body = '#212529',
48
+ muted = '#6c757d',
49
+ white = '#ffffff'
50
+ )
51
+ else:
52
+ return EngineConfigurationThemeColorsAgent(
53
+ )
54
+ """
55
+
56
+ def testEngineConfigurationThemeColorsAgent(self):
57
+ """Test EngineConfigurationThemeColorsAgent"""
58
+ # inst_req_only = self.make_instance(include_optional=False)
59
+ # inst_req_and_optional = self.make_instance(include_optional=True)
60
+
61
+ if __name__ == '__main__':
62
+ unittest.main()
{wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/__init__.py RENAMED
@@ -7,7 +7,7 @@
7
7
 
8
8
  # Introduction Welcome to the Wink API - A programmer-friendly way to manage, sell and book travel blocking on the Wink platform. The API gives you all the tools you need to ready your properties and blocking for sale across 1000s of our native sales channels. Integrators, affiliates, travel agents and content creators have the ability search for your travel blocking and promote / sell it in a wide variety of ways. # Integrations We have already integrated with the most well-known channel managers so you don't have to. To see our current integrations, please go to https://extranet.wink.travel and scroll to Connectivity section. Once your properties are set up, you can finish the setup by mapping your property to Wink using your channel manager partner portal. If your properties don't have a channel manager, you can easily manage rates and availability with this API. # Intended Audience Programmers are [most likely] a requirement to start integrating with Wink. Companies and organizations that would most benefit from integrating with us are new and existing travel companies that have relationships with suppliers and that need an advanced system from which to manage their travel blocking and get that same blocking out to as many eyeballs as possible at the lowest price possible. - Hotel chains - Hotel brands - Travel tech companies - Destination sites - Integrators - Aggregators - Destination management companies - Travel agencies - OTAs ## APIs Not every integrator needs every API. For that reason, we have separated APIs into context. ### Test API - [Ping](/ping): The Ping API is a quick test endpoint to verify that your credentials work Wink. ### Common APIs - [Notifications](/notifications): The Notifications API is a way for us to stay in touch with your user, property or affiliate account. - [User Settings](/user-settings): The User Settings API exposes endpoints to allow 3rd party integrators to communicate with Wink. ### Consume APIs Consume endpoints are for developers who want to find existing travel blocking and either book it or use it to advertise through one of their Wink affiliate accounts. - [Configuration](/engine-client): A single endpoint to retrieve whitelabel + customization information for the booking engine. - [Lookup](/lookup): All APIs related to locating blocking by region, locale and property flags. - [Inventory](/blocking): All APIs related to retrieve known travel blocking as it was found using the Lookup API.. - [Booking](/booking): All APIs related to creating bookings on the platform. - [Travel Agent](/travel-agent): The Travel Agent API exposes endpoints to manage agent-facilitated bookings. ### Produce APIs Produce endpoints are for developers who want to create and manage travel blocking. #### Property - [Property registration](/extranet/property/register): As a producer, this is, oftentimes, where you start your journey. These endpoints let you create properties on Wink. - [Property](/extranet/property): This collection of property endpoints are mostly management endpoints that let you display, change status and similar for your existing properties. - [Facilities](/extranet/facilities): This collection of endpoints let you manage facilities; such as room types. - [Experiences](/extranet/experiences): This collection of endpoints let you manage experiences, such as activities. - [Monetize](/extranet/monetize): The Monetize API exposes endpoints for managing cancellation polies, rate plans, promotions and more on Wink. - [Distribution](/extranet/distribution): The Distribution API exposes endpoints for sales channels, connecting with affiliates, managing rates and blocking calendars and more on Wink. - [Property Booking](/extranet/booking): The Property Booking API exposes endpoints for managing bookings and reviews at the property-level. #### Affiliate - [Affiliate](/affiliate): This collection of affiliate endpoints are mostly management endpoints that let you display, change status and similar for your existing accounts. - [Browse](/affiliate/browse): The Browse API exposes endpoints for affiliates to find suppliers and blocking to sell. - [Inventory](/affiliate/blocking): The Inventory API exposes endpoints for affiliates to manage the blocking they want to sell and how they want to sell it. - [Sales Channel](/affiliate/sales-channel): The Sales Channel API exposes endpoints for affiliates to manage existing sales channels as well as find new ones. - [WinkLinks](/affiliate/winklinks): The WinkLinks API exposes endpoints for affiliates to manage their WinkLinks page. #### Rate provider - [Channel manager](/channel-manager): The Channel Manager API enables external channel manager partners to map, exchange rate / availability information with us as well as be informed of bookings that occur on the Wink platform for one of their properties. ### Taxonomy APIs Taxonomy endpoints are for developers who want to consume and produce travel blocking and need taxonomies of standard and non-standard codes for blocking types, classes, statuses etc. - [Reference](/reactive): All APIs related to retrieving platform-supported taxonomies. ### Insight APIs Insight endpoints do exactly what the name implies - They offer platform-level insight into the activities of producers and consumers. - [Analytics](/analytics): All APIs related to tracking metrics across a wide variety of data source segments including, more entertaining, leaderboard metrics. ### Payment APIs Payment endpoints are for developers who want to purchase travel blocking. This can be done via the API as a registered Travel Agent or using our API in conjunction with our PCI compliant reactive widget for all other entities. - [TripPay](/reactive): All APIs related to TripPay account management, booking, mapping and integration features. ## SDKs We are actively working on supporting the most used languages out there. If you don't see your language here, reach out to us with a request to officially add your language. In the meantime, if you want to roll your own SDK, you can do so by downloading the OpenAPI spec and using one of the many available OpenAPI generators available: [https://openapi-generator.tech/docs/generators](https://openapi-generator.tech/docs/generators). - Java SDK [https://github.com/wink-travel/wink-sdk-java](https://github.com/wink-travel/wink-sdk-java) ## Usage These features are made available to you via a [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer). This API is language agnostic. ## Versioning We chose to version our endpoints in a way that we hope affects your integration minimally. You request the version of our API you wish to work with via the `Wink-Version` header. When it's time for you to upgrade, you only have to change the version number to get access to our updated endpoints. ## Release history - Follow updates on Github: https://github.com/wink-travel/wink-sdk-java/blob/master/CHANGELOG.md # Travel Agent API The Travel Agent API exposes endpoints to manage agent-facilitated bookings. This API lets you: 1. Travel Agent: Manage agent entity. 2. Booking: Create / Manage bookings Browse the endpoints in the left navigation bar to get started.
9
9
 
10
- The version of the OpenAPI document: 30.7.10
10
+ The version of the OpenAPI document: 30.9.11
11
11
  Contact: bjorn@wink.travel
12
12
  Generated by OpenAPI Generator (https://openapi-generator.tech)
13
13
 
@@ -15,7 +15,7 @@
15
15
  """ # noqa: E501
16
16
 
17
17
 
18
- __version__ = "0.0.3"
18
+ __version__ = "0.0.4"
19
19
 
20
20
  # import apis into sdk package
21
21
  from wink_sdk_travel_agent.api.travel_agent_api import TravelAgentApi
@@ -74,7 +74,7 @@ from wink_sdk_travel_agent.models.custom_monetary_amount import CustomMonetaryAm
74
74
  from wink_sdk_travel_agent.models.daily_rate_agent import DailyRateAgent
75
75
  from wink_sdk_travel_agent.models.dow_pattern_group_agent import DowPatternGroupAgent
76
76
  from wink_sdk_travel_agent.models.engine_configuration_booking_report_agent import EngineConfigurationBookingReportAgent
77
- from wink_sdk_travel_agent.models.engine_configuration_theme_agent import EngineConfigurationThemeAgent
77
+ from wink_sdk_travel_agent.models.engine_configuration_theme_colors_agent import EngineConfigurationThemeColorsAgent
78
78
  from wink_sdk_travel_agent.models.extra_charge_agent import ExtraChargeAgent
79
79
  from wink_sdk_travel_agent.models.extra_charges_agent import ExtraChargesAgent
80
80
  from wink_sdk_travel_agent.models.fee_agent import FeeAgent
{wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/api/travel_agent_api.py RENAMED
@@ -5,7 +5,7 @@
5
5
 
6
6
  # Introduction Welcome to the Wink API - A programmer-friendly way to manage, sell and book travel blocking on the Wink platform. The API gives you all the tools you need to ready your properties and blocking for sale across 1000s of our native sales channels. Integrators, affiliates, travel agents and content creators have the ability search for your travel blocking and promote / sell it in a wide variety of ways. # Integrations We have already integrated with the most well-known channel managers so you don't have to. To see our current integrations, please go to https://extranet.wink.travel and scroll to Connectivity section. Once your properties are set up, you can finish the setup by mapping your property to Wink using your channel manager partner portal. If your properties don't have a channel manager, you can easily manage rates and availability with this API. # Intended Audience Programmers are [most likely] a requirement to start integrating with Wink. Companies and organizations that would most benefit from integrating with us are new and existing travel companies that have relationships with suppliers and that need an advanced system from which to manage their travel blocking and get that same blocking out to as many eyeballs as possible at the lowest price possible. - Hotel chains - Hotel brands - Travel tech companies - Destination sites - Integrators - Aggregators - Destination management companies - Travel agencies - OTAs ## APIs Not every integrator needs every API. For that reason, we have separated APIs into context. ### Test API - [Ping](/ping): The Ping API is a quick test endpoint to verify that your credentials work Wink. ### Common APIs - [Notifications](/notifications): The Notifications API is a way for us to stay in touch with your user, property or affiliate account. - [User Settings](/user-settings): The User Settings API exposes endpoints to allow 3rd party integrators to communicate with Wink. ### Consume APIs Consume endpoints are for developers who want to find existing travel blocking and either book it or use it to advertise through one of their Wink affiliate accounts. - [Configuration](/engine-client): A single endpoint to retrieve whitelabel + customization information for the booking engine. - [Lookup](/lookup): All APIs related to locating blocking by region, locale and property flags. - [Inventory](/blocking): All APIs related to retrieve known travel blocking as it was found using the Lookup API.. - [Booking](/booking): All APIs related to creating bookings on the platform. - [Travel Agent](/travel-agent): The Travel Agent API exposes endpoints to manage agent-facilitated bookings. ### Produce APIs Produce endpoints are for developers who want to create and manage travel blocking. #### Property - [Property registration](/extranet/property/register): As a producer, this is, oftentimes, where you start your journey. These endpoints let you create properties on Wink. - [Property](/extranet/property): This collection of property endpoints are mostly management endpoints that let you display, change status and similar for your existing properties. - [Facilities](/extranet/facilities): This collection of endpoints let you manage facilities; such as room types. - [Experiences](/extranet/experiences): This collection of endpoints let you manage experiences, such as activities. - [Monetize](/extranet/monetize): The Monetize API exposes endpoints for managing cancellation polies, rate plans, promotions and more on Wink. - [Distribution](/extranet/distribution): The Distribution API exposes endpoints for sales channels, connecting with affiliates, managing rates and blocking calendars and more on Wink. - [Property Booking](/extranet/booking): The Property Booking API exposes endpoints for managing bookings and reviews at the property-level. #### Affiliate - [Affiliate](/affiliate): This collection of affiliate endpoints are mostly management endpoints that let you display, change status and similar for your existing accounts. - [Browse](/affiliate/browse): The Browse API exposes endpoints for affiliates to find suppliers and blocking to sell. - [Inventory](/affiliate/blocking): The Inventory API exposes endpoints for affiliates to manage the blocking they want to sell and how they want to sell it. - [Sales Channel](/affiliate/sales-channel): The Sales Channel API exposes endpoints for affiliates to manage existing sales channels as well as find new ones. - [WinkLinks](/affiliate/winklinks): The WinkLinks API exposes endpoints for affiliates to manage their WinkLinks page. #### Rate provider - [Channel manager](/channel-manager): The Channel Manager API enables external channel manager partners to map, exchange rate / availability information with us as well as be informed of bookings that occur on the Wink platform for one of their properties. ### Taxonomy APIs Taxonomy endpoints are for developers who want to consume and produce travel blocking and need taxonomies of standard and non-standard codes for blocking types, classes, statuses etc. - [Reference](/reactive): All APIs related to retrieving platform-supported taxonomies. ### Insight APIs Insight endpoints do exactly what the name implies - They offer platform-level insight into the activities of producers and consumers. - [Analytics](/analytics): All APIs related to tracking metrics across a wide variety of data source segments including, more entertaining, leaderboard metrics. ### Payment APIs Payment endpoints are for developers who want to purchase travel blocking. This can be done via the API as a registered Travel Agent or using our API in conjunction with our PCI compliant reactive widget for all other entities. - [TripPay](/reactive): All APIs related to TripPay account management, booking, mapping and integration features. ## SDKs We are actively working on supporting the most used languages out there. If you don't see your language here, reach out to us with a request to officially add your language. In the meantime, if you want to roll your own SDK, you can do so by downloading the OpenAPI spec and using one of the many available OpenAPI generators available: [https://openapi-generator.tech/docs/generators](https://openapi-generator.tech/docs/generators). - Java SDK [https://github.com/wink-travel/wink-sdk-java](https://github.com/wink-travel/wink-sdk-java) ## Usage These features are made available to you via a [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer). This API is language agnostic. ## Versioning We chose to version our endpoints in a way that we hope affects your integration minimally. You request the version of our API you wish to work with via the `Wink-Version` header. When it's time for you to upgrade, you only have to change the version number to get access to our updated endpoints. ## Release history - Follow updates on Github: https://github.com/wink-travel/wink-sdk-java/blob/master/CHANGELOG.md # Travel Agent API The Travel Agent API exposes endpoints to manage agent-facilitated bookings. This API lets you: 1. Travel Agent: Manage agent entity. 2. Booking: Create / Manage bookings Browse the endpoints in the left navigation bar to get started.
7
7
 
8
- The version of the OpenAPI document: 30.7.10
8
+ The version of the OpenAPI document: 30.9.11
9
9
  Contact: bjorn@wink.travel
10
10
  Generated by OpenAPI Generator (https://openapi-generator.tech)
11
11
 
{wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/api_client.py RENAMED
@@ -5,7 +5,7 @@
5
5
 
6
6
  # Introduction Welcome to the Wink API - A programmer-friendly way to manage, sell and book travel blocking on the Wink platform. The API gives you all the tools you need to ready your properties and blocking for sale across 1000s of our native sales channels. Integrators, affiliates, travel agents and content creators have the ability search for your travel blocking and promote / sell it in a wide variety of ways. # Integrations We have already integrated with the most well-known channel managers so you don't have to. To see our current integrations, please go to https://extranet.wink.travel and scroll to Connectivity section. Once your properties are set up, you can finish the setup by mapping your property to Wink using your channel manager partner portal. If your properties don't have a channel manager, you can easily manage rates and availability with this API. # Intended Audience Programmers are [most likely] a requirement to start integrating with Wink. Companies and organizations that would most benefit from integrating with us are new and existing travel companies that have relationships with suppliers and that need an advanced system from which to manage their travel blocking and get that same blocking out to as many eyeballs as possible at the lowest price possible. - Hotel chains - Hotel brands - Travel tech companies - Destination sites - Integrators - Aggregators - Destination management companies - Travel agencies - OTAs ## APIs Not every integrator needs every API. For that reason, we have separated APIs into context. ### Test API - [Ping](/ping): The Ping API is a quick test endpoint to verify that your credentials work Wink. ### Common APIs - [Notifications](/notifications): The Notifications API is a way for us to stay in touch with your user, property or affiliate account. - [User Settings](/user-settings): The User Settings API exposes endpoints to allow 3rd party integrators to communicate with Wink. ### Consume APIs Consume endpoints are for developers who want to find existing travel blocking and either book it or use it to advertise through one of their Wink affiliate accounts. - [Configuration](/engine-client): A single endpoint to retrieve whitelabel + customization information for the booking engine. - [Lookup](/lookup): All APIs related to locating blocking by region, locale and property flags. - [Inventory](/blocking): All APIs related to retrieve known travel blocking as it was found using the Lookup API.. - [Booking](/booking): All APIs related to creating bookings on the platform. - [Travel Agent](/travel-agent): The Travel Agent API exposes endpoints to manage agent-facilitated bookings. ### Produce APIs Produce endpoints are for developers who want to create and manage travel blocking. #### Property - [Property registration](/extranet/property/register): As a producer, this is, oftentimes, where you start your journey. These endpoints let you create properties on Wink. - [Property](/extranet/property): This collection of property endpoints are mostly management endpoints that let you display, change status and similar for your existing properties. - [Facilities](/extranet/facilities): This collection of endpoints let you manage facilities; such as room types. - [Experiences](/extranet/experiences): This collection of endpoints let you manage experiences, such as activities. - [Monetize](/extranet/monetize): The Monetize API exposes endpoints for managing cancellation polies, rate plans, promotions and more on Wink. - [Distribution](/extranet/distribution): The Distribution API exposes endpoints for sales channels, connecting with affiliates, managing rates and blocking calendars and more on Wink. - [Property Booking](/extranet/booking): The Property Booking API exposes endpoints for managing bookings and reviews at the property-level. #### Affiliate - [Affiliate](/affiliate): This collection of affiliate endpoints are mostly management endpoints that let you display, change status and similar for your existing accounts. - [Browse](/affiliate/browse): The Browse API exposes endpoints for affiliates to find suppliers and blocking to sell. - [Inventory](/affiliate/blocking): The Inventory API exposes endpoints for affiliates to manage the blocking they want to sell and how they want to sell it. - [Sales Channel](/affiliate/sales-channel): The Sales Channel API exposes endpoints for affiliates to manage existing sales channels as well as find new ones. - [WinkLinks](/affiliate/winklinks): The WinkLinks API exposes endpoints for affiliates to manage their WinkLinks page. #### Rate provider - [Channel manager](/channel-manager): The Channel Manager API enables external channel manager partners to map, exchange rate / availability information with us as well as be informed of bookings that occur on the Wink platform for one of their properties. ### Taxonomy APIs Taxonomy endpoints are for developers who want to consume and produce travel blocking and need taxonomies of standard and non-standard codes for blocking types, classes, statuses etc. - [Reference](/reactive): All APIs related to retrieving platform-supported taxonomies. ### Insight APIs Insight endpoints do exactly what the name implies - They offer platform-level insight into the activities of producers and consumers. - [Analytics](/analytics): All APIs related to tracking metrics across a wide variety of data source segments including, more entertaining, leaderboard metrics. ### Payment APIs Payment endpoints are for developers who want to purchase travel blocking. This can be done via the API as a registered Travel Agent or using our API in conjunction with our PCI compliant reactive widget for all other entities. - [TripPay](/reactive): All APIs related to TripPay account management, booking, mapping and integration features. ## SDKs We are actively working on supporting the most used languages out there. If you don't see your language here, reach out to us with a request to officially add your language. In the meantime, if you want to roll your own SDK, you can do so by downloading the OpenAPI spec and using one of the many available OpenAPI generators available: [https://openapi-generator.tech/docs/generators](https://openapi-generator.tech/docs/generators). - Java SDK [https://github.com/wink-travel/wink-sdk-java](https://github.com/wink-travel/wink-sdk-java) ## Usage These features are made available to you via a [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer). This API is language agnostic. ## Versioning We chose to version our endpoints in a way that we hope affects your integration minimally. You request the version of our API you wish to work with via the `Wink-Version` header. When it's time for you to upgrade, you only have to change the version number to get access to our updated endpoints. ## Release history - Follow updates on Github: https://github.com/wink-travel/wink-sdk-java/blob/master/CHANGELOG.md # Travel Agent API The Travel Agent API exposes endpoints to manage agent-facilitated bookings. This API lets you: 1. Travel Agent: Manage agent entity. 2. Booking: Create / Manage bookings Browse the endpoints in the left navigation bar to get started.
7
7
 
8
- The version of the OpenAPI document: 30.7.10
8
+ The version of the OpenAPI document: 30.9.11
9
9
  Contact: bjorn@wink.travel
10
10
  Generated by OpenAPI Generator (https://openapi-generator.tech)
11
11
 
{wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/configuration.py RENAMED
@@ -5,7 +5,7 @@
5
5
 
6
6
  # Introduction Welcome to the Wink API - A programmer-friendly way to manage, sell and book travel blocking on the Wink platform. The API gives you all the tools you need to ready your properties and blocking for sale across 1000s of our native sales channels. Integrators, affiliates, travel agents and content creators have the ability search for your travel blocking and promote / sell it in a wide variety of ways. # Integrations We have already integrated with the most well-known channel managers so you don't have to. To see our current integrations, please go to https://extranet.wink.travel and scroll to Connectivity section. Once your properties are set up, you can finish the setup by mapping your property to Wink using your channel manager partner portal. If your properties don't have a channel manager, you can easily manage rates and availability with this API. # Intended Audience Programmers are [most likely] a requirement to start integrating with Wink. Companies and organizations that would most benefit from integrating with us are new and existing travel companies that have relationships with suppliers and that need an advanced system from which to manage their travel blocking and get that same blocking out to as many eyeballs as possible at the lowest price possible. - Hotel chains - Hotel brands - Travel tech companies - Destination sites - Integrators - Aggregators - Destination management companies - Travel agencies - OTAs ## APIs Not every integrator needs every API. For that reason, we have separated APIs into context. ### Test API - [Ping](/ping): The Ping API is a quick test endpoint to verify that your credentials work Wink. ### Common APIs - [Notifications](/notifications): The Notifications API is a way for us to stay in touch with your user, property or affiliate account. - [User Settings](/user-settings): The User Settings API exposes endpoints to allow 3rd party integrators to communicate with Wink. ### Consume APIs Consume endpoints are for developers who want to find existing travel blocking and either book it or use it to advertise through one of their Wink affiliate accounts. - [Configuration](/engine-client): A single endpoint to retrieve whitelabel + customization information for the booking engine. - [Lookup](/lookup): All APIs related to locating blocking by region, locale and property flags. - [Inventory](/blocking): All APIs related to retrieve known travel blocking as it was found using the Lookup API.. - [Booking](/booking): All APIs related to creating bookings on the platform. - [Travel Agent](/travel-agent): The Travel Agent API exposes endpoints to manage agent-facilitated bookings. ### Produce APIs Produce endpoints are for developers who want to create and manage travel blocking. #### Property - [Property registration](/extranet/property/register): As a producer, this is, oftentimes, where you start your journey. These endpoints let you create properties on Wink. - [Property](/extranet/property): This collection of property endpoints are mostly management endpoints that let you display, change status and similar for your existing properties. - [Facilities](/extranet/facilities): This collection of endpoints let you manage facilities; such as room types. - [Experiences](/extranet/experiences): This collection of endpoints let you manage experiences, such as activities. - [Monetize](/extranet/monetize): The Monetize API exposes endpoints for managing cancellation polies, rate plans, promotions and more on Wink. - [Distribution](/extranet/distribution): The Distribution API exposes endpoints for sales channels, connecting with affiliates, managing rates and blocking calendars and more on Wink. - [Property Booking](/extranet/booking): The Property Booking API exposes endpoints for managing bookings and reviews at the property-level. #### Affiliate - [Affiliate](/affiliate): This collection of affiliate endpoints are mostly management endpoints that let you display, change status and similar for your existing accounts. - [Browse](/affiliate/browse): The Browse API exposes endpoints for affiliates to find suppliers and blocking to sell. - [Inventory](/affiliate/blocking): The Inventory API exposes endpoints for affiliates to manage the blocking they want to sell and how they want to sell it. - [Sales Channel](/affiliate/sales-channel): The Sales Channel API exposes endpoints for affiliates to manage existing sales channels as well as find new ones. - [WinkLinks](/affiliate/winklinks): The WinkLinks API exposes endpoints for affiliates to manage their WinkLinks page. #### Rate provider - [Channel manager](/channel-manager): The Channel Manager API enables external channel manager partners to map, exchange rate / availability information with us as well as be informed of bookings that occur on the Wink platform for one of their properties. ### Taxonomy APIs Taxonomy endpoints are for developers who want to consume and produce travel blocking and need taxonomies of standard and non-standard codes for blocking types, classes, statuses etc. - [Reference](/reactive): All APIs related to retrieving platform-supported taxonomies. ### Insight APIs Insight endpoints do exactly what the name implies - They offer platform-level insight into the activities of producers and consumers. - [Analytics](/analytics): All APIs related to tracking metrics across a wide variety of data source segments including, more entertaining, leaderboard metrics. ### Payment APIs Payment endpoints are for developers who want to purchase travel blocking. This can be done via the API as a registered Travel Agent or using our API in conjunction with our PCI compliant reactive widget for all other entities. - [TripPay](/reactive): All APIs related to TripPay account management, booking, mapping and integration features. ## SDKs We are actively working on supporting the most used languages out there. If you don't see your language here, reach out to us with a request to officially add your language. In the meantime, if you want to roll your own SDK, you can do so by downloading the OpenAPI spec and using one of the many available OpenAPI generators available: [https://openapi-generator.tech/docs/generators](https://openapi-generator.tech/docs/generators). - Java SDK [https://github.com/wink-travel/wink-sdk-java](https://github.com/wink-travel/wink-sdk-java) ## Usage These features are made available to you via a [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer). This API is language agnostic. ## Versioning We chose to version our endpoints in a way that we hope affects your integration minimally. You request the version of our API you wish to work with via the `Wink-Version` header. When it's time for you to upgrade, you only have to change the version number to get access to our updated endpoints. ## Release history - Follow updates on Github: https://github.com/wink-travel/wink-sdk-java/blob/master/CHANGELOG.md # Travel Agent API The Travel Agent API exposes endpoints to manage agent-facilitated bookings. This API lets you: 1. Travel Agent: Manage agent entity. 2. Booking: Create / Manage bookings Browse the endpoints in the left navigation bar to get started.
7
7
 
8
- The version of the OpenAPI document: 30.7.10
8
+ The version of the OpenAPI document: 30.9.11
9
9
  Contact: bjorn@wink.travel
10
10
  Generated by OpenAPI Generator (https://openapi-generator.tech)
11
11
 
@@ -392,8 +392,8 @@ class Configuration:
392
392
  return "Python SDK Debug Report:\n"\
393
393
  "OS: {env}\n"\
394
394
  "Python Version: {pyversion}\n"\
395
- "Version of the API: 30.7.10\n"\
396
- "SDK Package Version: 0.0.3".\
395
+ "Version of the API: 30.9.11\n"\
396
+ "SDK Package Version: 0.0.4".\
397
397
  format(env=sys.platform, pyversion=sys.version)
398
398
 
399
399
  def get_host_settings(self):
{wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/exceptions.py RENAMED
@@ -5,7 +5,7 @@
5
5
 
6
6
  # Introduction Welcome to the Wink API - A programmer-friendly way to manage, sell and book travel blocking on the Wink platform. The API gives you all the tools you need to ready your properties and blocking for sale across 1000s of our native sales channels. Integrators, affiliates, travel agents and content creators have the ability search for your travel blocking and promote / sell it in a wide variety of ways. # Integrations We have already integrated with the most well-known channel managers so you don't have to. To see our current integrations, please go to https://extranet.wink.travel and scroll to Connectivity section. Once your properties are set up, you can finish the setup by mapping your property to Wink using your channel manager partner portal. If your properties don't have a channel manager, you can easily manage rates and availability with this API. # Intended Audience Programmers are [most likely] a requirement to start integrating with Wink. Companies and organizations that would most benefit from integrating with us are new and existing travel companies that have relationships with suppliers and that need an advanced system from which to manage their travel blocking and get that same blocking out to as many eyeballs as possible at the lowest price possible. - Hotel chains - Hotel brands - Travel tech companies - Destination sites - Integrators - Aggregators - Destination management companies - Travel agencies - OTAs ## APIs Not every integrator needs every API. For that reason, we have separated APIs into context. ### Test API - [Ping](/ping): The Ping API is a quick test endpoint to verify that your credentials work Wink. ### Common APIs - [Notifications](/notifications): The Notifications API is a way for us to stay in touch with your user, property or affiliate account. - [User Settings](/user-settings): The User Settings API exposes endpoints to allow 3rd party integrators to communicate with Wink. ### Consume APIs Consume endpoints are for developers who want to find existing travel blocking and either book it or use it to advertise through one of their Wink affiliate accounts. - [Configuration](/engine-client): A single endpoint to retrieve whitelabel + customization information for the booking engine. - [Lookup](/lookup): All APIs related to locating blocking by region, locale and property flags. - [Inventory](/blocking): All APIs related to retrieve known travel blocking as it was found using the Lookup API.. - [Booking](/booking): All APIs related to creating bookings on the platform. - [Travel Agent](/travel-agent): The Travel Agent API exposes endpoints to manage agent-facilitated bookings. ### Produce APIs Produce endpoints are for developers who want to create and manage travel blocking. #### Property - [Property registration](/extranet/property/register): As a producer, this is, oftentimes, where you start your journey. These endpoints let you create properties on Wink. - [Property](/extranet/property): This collection of property endpoints are mostly management endpoints that let you display, change status and similar for your existing properties. - [Facilities](/extranet/facilities): This collection of endpoints let you manage facilities; such as room types. - [Experiences](/extranet/experiences): This collection of endpoints let you manage experiences, such as activities. - [Monetize](/extranet/monetize): The Monetize API exposes endpoints for managing cancellation polies, rate plans, promotions and more on Wink. - [Distribution](/extranet/distribution): The Distribution API exposes endpoints for sales channels, connecting with affiliates, managing rates and blocking calendars and more on Wink. - [Property Booking](/extranet/booking): The Property Booking API exposes endpoints for managing bookings and reviews at the property-level. #### Affiliate - [Affiliate](/affiliate): This collection of affiliate endpoints are mostly management endpoints that let you display, change status and similar for your existing accounts. - [Browse](/affiliate/browse): The Browse API exposes endpoints for affiliates to find suppliers and blocking to sell. - [Inventory](/affiliate/blocking): The Inventory API exposes endpoints for affiliates to manage the blocking they want to sell and how they want to sell it. - [Sales Channel](/affiliate/sales-channel): The Sales Channel API exposes endpoints for affiliates to manage existing sales channels as well as find new ones. - [WinkLinks](/affiliate/winklinks): The WinkLinks API exposes endpoints for affiliates to manage their WinkLinks page. #### Rate provider - [Channel manager](/channel-manager): The Channel Manager API enables external channel manager partners to map, exchange rate / availability information with us as well as be informed of bookings that occur on the Wink platform for one of their properties. ### Taxonomy APIs Taxonomy endpoints are for developers who want to consume and produce travel blocking and need taxonomies of standard and non-standard codes for blocking types, classes, statuses etc. - [Reference](/reactive): All APIs related to retrieving platform-supported taxonomies. ### Insight APIs Insight endpoints do exactly what the name implies - They offer platform-level insight into the activities of producers and consumers. - [Analytics](/analytics): All APIs related to tracking metrics across a wide variety of data source segments including, more entertaining, leaderboard metrics. ### Payment APIs Payment endpoints are for developers who want to purchase travel blocking. This can be done via the API as a registered Travel Agent or using our API in conjunction with our PCI compliant reactive widget for all other entities. - [TripPay](/reactive): All APIs related to TripPay account management, booking, mapping and integration features. ## SDKs We are actively working on supporting the most used languages out there. If you don't see your language here, reach out to us with a request to officially add your language. In the meantime, if you want to roll your own SDK, you can do so by downloading the OpenAPI spec and using one of the many available OpenAPI generators available: [https://openapi-generator.tech/docs/generators](https://openapi-generator.tech/docs/generators). - Java SDK [https://github.com/wink-travel/wink-sdk-java](https://github.com/wink-travel/wink-sdk-java) ## Usage These features are made available to you via a [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer). This API is language agnostic. ## Versioning We chose to version our endpoints in a way that we hope affects your integration minimally. You request the version of our API you wish to work with via the `Wink-Version` header. When it's time for you to upgrade, you only have to change the version number to get access to our updated endpoints. ## Release history - Follow updates on Github: https://github.com/wink-travel/wink-sdk-java/blob/master/CHANGELOG.md # Travel Agent API The Travel Agent API exposes endpoints to manage agent-facilitated bookings. This API lets you: 1. Travel Agent: Manage agent entity. 2. Booking: Create / Manage bookings Browse the endpoints in the left navigation bar to get started.
7
7
 
8
- The version of the OpenAPI document: 30.7.10
8
+ The version of the OpenAPI document: 30.9.11
9
9
  Contact: bjorn@wink.travel
10
10
  Generated by OpenAPI Generator (https://openapi-generator.tech)
11
11
 
{wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/__init__.py RENAMED
@@ -6,7 +6,7 @@
6
6
 
7
7
  # Introduction Welcome to the Wink API - A programmer-friendly way to manage, sell and book travel blocking on the Wink platform. The API gives you all the tools you need to ready your properties and blocking for sale across 1000s of our native sales channels. Integrators, affiliates, travel agents and content creators have the ability search for your travel blocking and promote / sell it in a wide variety of ways. # Integrations We have already integrated with the most well-known channel managers so you don't have to. To see our current integrations, please go to https://extranet.wink.travel and scroll to Connectivity section. Once your properties are set up, you can finish the setup by mapping your property to Wink using your channel manager partner portal. If your properties don't have a channel manager, you can easily manage rates and availability with this API. # Intended Audience Programmers are [most likely] a requirement to start integrating with Wink. Companies and organizations that would most benefit from integrating with us are new and existing travel companies that have relationships with suppliers and that need an advanced system from which to manage their travel blocking and get that same blocking out to as many eyeballs as possible at the lowest price possible. - Hotel chains - Hotel brands - Travel tech companies - Destination sites - Integrators - Aggregators - Destination management companies - Travel agencies - OTAs ## APIs Not every integrator needs every API. For that reason, we have separated APIs into context. ### Test API - [Ping](/ping): The Ping API is a quick test endpoint to verify that your credentials work Wink. ### Common APIs - [Notifications](/notifications): The Notifications API is a way for us to stay in touch with your user, property or affiliate account. - [User Settings](/user-settings): The User Settings API exposes endpoints to allow 3rd party integrators to communicate with Wink. ### Consume APIs Consume endpoints are for developers who want to find existing travel blocking and either book it or use it to advertise through one of their Wink affiliate accounts. - [Configuration](/engine-client): A single endpoint to retrieve whitelabel + customization information for the booking engine. - [Lookup](/lookup): All APIs related to locating blocking by region, locale and property flags. - [Inventory](/blocking): All APIs related to retrieve known travel blocking as it was found using the Lookup API.. - [Booking](/booking): All APIs related to creating bookings on the platform. - [Travel Agent](/travel-agent): The Travel Agent API exposes endpoints to manage agent-facilitated bookings. ### Produce APIs Produce endpoints are for developers who want to create and manage travel blocking. #### Property - [Property registration](/extranet/property/register): As a producer, this is, oftentimes, where you start your journey. These endpoints let you create properties on Wink. - [Property](/extranet/property): This collection of property endpoints are mostly management endpoints that let you display, change status and similar for your existing properties. - [Facilities](/extranet/facilities): This collection of endpoints let you manage facilities; such as room types. - [Experiences](/extranet/experiences): This collection of endpoints let you manage experiences, such as activities. - [Monetize](/extranet/monetize): The Monetize API exposes endpoints for managing cancellation polies, rate plans, promotions and more on Wink. - [Distribution](/extranet/distribution): The Distribution API exposes endpoints for sales channels, connecting with affiliates, managing rates and blocking calendars and more on Wink. - [Property Booking](/extranet/booking): The Property Booking API exposes endpoints for managing bookings and reviews at the property-level. #### Affiliate - [Affiliate](/affiliate): This collection of affiliate endpoints are mostly management endpoints that let you display, change status and similar for your existing accounts. - [Browse](/affiliate/browse): The Browse API exposes endpoints for affiliates to find suppliers and blocking to sell. - [Inventory](/affiliate/blocking): The Inventory API exposes endpoints for affiliates to manage the blocking they want to sell and how they want to sell it. - [Sales Channel](/affiliate/sales-channel): The Sales Channel API exposes endpoints for affiliates to manage existing sales channels as well as find new ones. - [WinkLinks](/affiliate/winklinks): The WinkLinks API exposes endpoints for affiliates to manage their WinkLinks page. #### Rate provider - [Channel manager](/channel-manager): The Channel Manager API enables external channel manager partners to map, exchange rate / availability information with us as well as be informed of bookings that occur on the Wink platform for one of their properties. ### Taxonomy APIs Taxonomy endpoints are for developers who want to consume and produce travel blocking and need taxonomies of standard and non-standard codes for blocking types, classes, statuses etc. - [Reference](/reactive): All APIs related to retrieving platform-supported taxonomies. ### Insight APIs Insight endpoints do exactly what the name implies - They offer platform-level insight into the activities of producers and consumers. - [Analytics](/analytics): All APIs related to tracking metrics across a wide variety of data source segments including, more entertaining, leaderboard metrics. ### Payment APIs Payment endpoints are for developers who want to purchase travel blocking. This can be done via the API as a registered Travel Agent or using our API in conjunction with our PCI compliant reactive widget for all other entities. - [TripPay](/reactive): All APIs related to TripPay account management, booking, mapping and integration features. ## SDKs We are actively working on supporting the most used languages out there. If you don't see your language here, reach out to us with a request to officially add your language. In the meantime, if you want to roll your own SDK, you can do so by downloading the OpenAPI spec and using one of the many available OpenAPI generators available: [https://openapi-generator.tech/docs/generators](https://openapi-generator.tech/docs/generators). - Java SDK [https://github.com/wink-travel/wink-sdk-java](https://github.com/wink-travel/wink-sdk-java) ## Usage These features are made available to you via a [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer). This API is language agnostic. ## Versioning We chose to version our endpoints in a way that we hope affects your integration minimally. You request the version of our API you wish to work with via the `Wink-Version` header. When it's time for you to upgrade, you only have to change the version number to get access to our updated endpoints. ## Release history - Follow updates on Github: https://github.com/wink-travel/wink-sdk-java/blob/master/CHANGELOG.md # Travel Agent API The Travel Agent API exposes endpoints to manage agent-facilitated bookings. This API lets you: 1. Travel Agent: Manage agent entity. 2. Booking: Create / Manage bookings Browse the endpoints in the left navigation bar to get started.
8
8
 
9
- The version of the OpenAPI document: 30.7.10
9
+ The version of the OpenAPI document: 30.9.11
10
10
  Contact: bjorn@wink.travel
11
11
  Generated by OpenAPI Generator (https://openapi-generator.tech)
12
12
 
@@ -57,7 +57,7 @@ from wink_sdk_travel_agent.models.custom_monetary_amount import CustomMonetaryAm
57
57
  from wink_sdk_travel_agent.models.daily_rate_agent import DailyRateAgent
58
58
  from wink_sdk_travel_agent.models.dow_pattern_group_agent import DowPatternGroupAgent
59
59
  from wink_sdk_travel_agent.models.engine_configuration_booking_report_agent import EngineConfigurationBookingReportAgent
60
- from wink_sdk_travel_agent.models.engine_configuration_theme_agent import EngineConfigurationThemeAgent
60
+ from wink_sdk_travel_agent.models.engine_configuration_theme_colors_agent import EngineConfigurationThemeColorsAgent
61
61
  from wink_sdk_travel_agent.models.extra_charge_agent import ExtraChargeAgent
62
62
  from wink_sdk_travel_agent.models.extra_charges_agent import ExtraChargesAgent
63
63
  from wink_sdk_travel_agent.models.fee_agent import FeeAgent
{wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/address_agent.py RENAMED
@@ -5,7 +5,7 @@
5
5
 
6
6
  # Introduction Welcome to the Wink API - A programmer-friendly way to manage, sell and book travel blocking on the Wink platform. The API gives you all the tools you need to ready your properties and blocking for sale across 1000s of our native sales channels. Integrators, affiliates, travel agents and content creators have the ability search for your travel blocking and promote / sell it in a wide variety of ways. # Integrations We have already integrated with the most well-known channel managers so you don't have to. To see our current integrations, please go to https://extranet.wink.travel and scroll to Connectivity section. Once your properties are set up, you can finish the setup by mapping your property to Wink using your channel manager partner portal. If your properties don't have a channel manager, you can easily manage rates and availability with this API. # Intended Audience Programmers are [most likely] a requirement to start integrating with Wink. Companies and organizations that would most benefit from integrating with us are new and existing travel companies that have relationships with suppliers and that need an advanced system from which to manage their travel blocking and get that same blocking out to as many eyeballs as possible at the lowest price possible. - Hotel chains - Hotel brands - Travel tech companies - Destination sites - Integrators - Aggregators - Destination management companies - Travel agencies - OTAs ## APIs Not every integrator needs every API. For that reason, we have separated APIs into context. ### Test API - [Ping](/ping): The Ping API is a quick test endpoint to verify that your credentials work Wink. ### Common APIs - [Notifications](/notifications): The Notifications API is a way for us to stay in touch with your user, property or affiliate account. - [User Settings](/user-settings): The User Settings API exposes endpoints to allow 3rd party integrators to communicate with Wink. ### Consume APIs Consume endpoints are for developers who want to find existing travel blocking and either book it or use it to advertise through one of their Wink affiliate accounts. - [Configuration](/engine-client): A single endpoint to retrieve whitelabel + customization information for the booking engine. - [Lookup](/lookup): All APIs related to locating blocking by region, locale and property flags. - [Inventory](/blocking): All APIs related to retrieve known travel blocking as it was found using the Lookup API.. - [Booking](/booking): All APIs related to creating bookings on the platform. - [Travel Agent](/travel-agent): The Travel Agent API exposes endpoints to manage agent-facilitated bookings. ### Produce APIs Produce endpoints are for developers who want to create and manage travel blocking. #### Property - [Property registration](/extranet/property/register): As a producer, this is, oftentimes, where you start your journey. These endpoints let you create properties on Wink. - [Property](/extranet/property): This collection of property endpoints are mostly management endpoints that let you display, change status and similar for your existing properties. - [Facilities](/extranet/facilities): This collection of endpoints let you manage facilities; such as room types. - [Experiences](/extranet/experiences): This collection of endpoints let you manage experiences, such as activities. - [Monetize](/extranet/monetize): The Monetize API exposes endpoints for managing cancellation polies, rate plans, promotions and more on Wink. - [Distribution](/extranet/distribution): The Distribution API exposes endpoints for sales channels, connecting with affiliates, managing rates and blocking calendars and more on Wink. - [Property Booking](/extranet/booking): The Property Booking API exposes endpoints for managing bookings and reviews at the property-level. #### Affiliate - [Affiliate](/affiliate): This collection of affiliate endpoints are mostly management endpoints that let you display, change status and similar for your existing accounts. - [Browse](/affiliate/browse): The Browse API exposes endpoints for affiliates to find suppliers and blocking to sell. - [Inventory](/affiliate/blocking): The Inventory API exposes endpoints for affiliates to manage the blocking they want to sell and how they want to sell it. - [Sales Channel](/affiliate/sales-channel): The Sales Channel API exposes endpoints for affiliates to manage existing sales channels as well as find new ones. - [WinkLinks](/affiliate/winklinks): The WinkLinks API exposes endpoints for affiliates to manage their WinkLinks page. #### Rate provider - [Channel manager](/channel-manager): The Channel Manager API enables external channel manager partners to map, exchange rate / availability information with us as well as be informed of bookings that occur on the Wink platform for one of their properties. ### Taxonomy APIs Taxonomy endpoints are for developers who want to consume and produce travel blocking and need taxonomies of standard and non-standard codes for blocking types, classes, statuses etc. - [Reference](/reactive): All APIs related to retrieving platform-supported taxonomies. ### Insight APIs Insight endpoints do exactly what the name implies - They offer platform-level insight into the activities of producers and consumers. - [Analytics](/analytics): All APIs related to tracking metrics across a wide variety of data source segments including, more entertaining, leaderboard metrics. ### Payment APIs Payment endpoints are for developers who want to purchase travel blocking. This can be done via the API as a registered Travel Agent or using our API in conjunction with our PCI compliant reactive widget for all other entities. - [TripPay](/reactive): All APIs related to TripPay account management, booking, mapping and integration features. ## SDKs We are actively working on supporting the most used languages out there. If you don't see your language here, reach out to us with a request to officially add your language. In the meantime, if you want to roll your own SDK, you can do so by downloading the OpenAPI spec and using one of the many available OpenAPI generators available: [https://openapi-generator.tech/docs/generators](https://openapi-generator.tech/docs/generators). - Java SDK [https://github.com/wink-travel/wink-sdk-java](https://github.com/wink-travel/wink-sdk-java) ## Usage These features are made available to you via a [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer). This API is language agnostic. ## Versioning We chose to version our endpoints in a way that we hope affects your integration minimally. You request the version of our API you wish to work with via the `Wink-Version` header. When it's time for you to upgrade, you only have to change the version number to get access to our updated endpoints. ## Release history - Follow updates on Github: https://github.com/wink-travel/wink-sdk-java/blob/master/CHANGELOG.md # Travel Agent API The Travel Agent API exposes endpoints to manage agent-facilitated bookings. This API lets you: 1. Travel Agent: Manage agent entity. 2. Booking: Create / Manage bookings Browse the endpoints in the left navigation bar to get started.
7
7
 
8
- The version of the OpenAPI document: 30.7.10
8
+ The version of the OpenAPI document: 30.9.11
9
9
  Contact: bjorn@wink.travel
10
10
  Generated by OpenAPI Generator (https://openapi-generator.tech)
11
11
 
{wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/agent_booking_request_agent.py RENAMED
@@ -5,7 +5,7 @@
5
5
 
6
6
  # Introduction Welcome to the Wink API - A programmer-friendly way to manage, sell and book travel blocking on the Wink platform. The API gives you all the tools you need to ready your properties and blocking for sale across 1000s of our native sales channels. Integrators, affiliates, travel agents and content creators have the ability search for your travel blocking and promote / sell it in a wide variety of ways. # Integrations We have already integrated with the most well-known channel managers so you don't have to. To see our current integrations, please go to https://extranet.wink.travel and scroll to Connectivity section. Once your properties are set up, you can finish the setup by mapping your property to Wink using your channel manager partner portal. If your properties don't have a channel manager, you can easily manage rates and availability with this API. # Intended Audience Programmers are [most likely] a requirement to start integrating with Wink. Companies and organizations that would most benefit from integrating with us are new and existing travel companies that have relationships with suppliers and that need an advanced system from which to manage their travel blocking and get that same blocking out to as many eyeballs as possible at the lowest price possible. - Hotel chains - Hotel brands - Travel tech companies - Destination sites - Integrators - Aggregators - Destination management companies - Travel agencies - OTAs ## APIs Not every integrator needs every API. For that reason, we have separated APIs into context. ### Test API - [Ping](/ping): The Ping API is a quick test endpoint to verify that your credentials work Wink. ### Common APIs - [Notifications](/notifications): The Notifications API is a way for us to stay in touch with your user, property or affiliate account. - [User Settings](/user-settings): The User Settings API exposes endpoints to allow 3rd party integrators to communicate with Wink. ### Consume APIs Consume endpoints are for developers who want to find existing travel blocking and either book it or use it to advertise through one of their Wink affiliate accounts. - [Configuration](/engine-client): A single endpoint to retrieve whitelabel + customization information for the booking engine. - [Lookup](/lookup): All APIs related to locating blocking by region, locale and property flags. - [Inventory](/blocking): All APIs related to retrieve known travel blocking as it was found using the Lookup API.. - [Booking](/booking): All APIs related to creating bookings on the platform. - [Travel Agent](/travel-agent): The Travel Agent API exposes endpoints to manage agent-facilitated bookings. ### Produce APIs Produce endpoints are for developers who want to create and manage travel blocking. #### Property - [Property registration](/extranet/property/register): As a producer, this is, oftentimes, where you start your journey. These endpoints let you create properties on Wink. - [Property](/extranet/property): This collection of property endpoints are mostly management endpoints that let you display, change status and similar for your existing properties. - [Facilities](/extranet/facilities): This collection of endpoints let you manage facilities; such as room types. - [Experiences](/extranet/experiences): This collection of endpoints let you manage experiences, such as activities. - [Monetize](/extranet/monetize): The Monetize API exposes endpoints for managing cancellation polies, rate plans, promotions and more on Wink. - [Distribution](/extranet/distribution): The Distribution API exposes endpoints for sales channels, connecting with affiliates, managing rates and blocking calendars and more on Wink. - [Property Booking](/extranet/booking): The Property Booking API exposes endpoints for managing bookings and reviews at the property-level. #### Affiliate - [Affiliate](/affiliate): This collection of affiliate endpoints are mostly management endpoints that let you display, change status and similar for your existing accounts. - [Browse](/affiliate/browse): The Browse API exposes endpoints for affiliates to find suppliers and blocking to sell. - [Inventory](/affiliate/blocking): The Inventory API exposes endpoints for affiliates to manage the blocking they want to sell and how they want to sell it. - [Sales Channel](/affiliate/sales-channel): The Sales Channel API exposes endpoints for affiliates to manage existing sales channels as well as find new ones. - [WinkLinks](/affiliate/winklinks): The WinkLinks API exposes endpoints for affiliates to manage their WinkLinks page. #### Rate provider - [Channel manager](/channel-manager): The Channel Manager API enables external channel manager partners to map, exchange rate / availability information with us as well as be informed of bookings that occur on the Wink platform for one of their properties. ### Taxonomy APIs Taxonomy endpoints are for developers who want to consume and produce travel blocking and need taxonomies of standard and non-standard codes for blocking types, classes, statuses etc. - [Reference](/reactive): All APIs related to retrieving platform-supported taxonomies. ### Insight APIs Insight endpoints do exactly what the name implies - They offer platform-level insight into the activities of producers and consumers. - [Analytics](/analytics): All APIs related to tracking metrics across a wide variety of data source segments including, more entertaining, leaderboard metrics. ### Payment APIs Payment endpoints are for developers who want to purchase travel blocking. This can be done via the API as a registered Travel Agent or using our API in conjunction with our PCI compliant reactive widget for all other entities. - [TripPay](/reactive): All APIs related to TripPay account management, booking, mapping and integration features. ## SDKs We are actively working on supporting the most used languages out there. If you don't see your language here, reach out to us with a request to officially add your language. In the meantime, if you want to roll your own SDK, you can do so by downloading the OpenAPI spec and using one of the many available OpenAPI generators available: [https://openapi-generator.tech/docs/generators](https://openapi-generator.tech/docs/generators). - Java SDK [https://github.com/wink-travel/wink-sdk-java](https://github.com/wink-travel/wink-sdk-java) ## Usage These features are made available to you via a [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer). This API is language agnostic. ## Versioning We chose to version our endpoints in a way that we hope affects your integration minimally. You request the version of our API you wish to work with via the `Wink-Version` header. When it's time for you to upgrade, you only have to change the version number to get access to our updated endpoints. ## Release history - Follow updates on Github: https://github.com/wink-travel/wink-sdk-java/blob/master/CHANGELOG.md # Travel Agent API The Travel Agent API exposes endpoints to manage agent-facilitated bookings. This API lets you: 1. Travel Agent: Manage agent entity. 2. Booking: Create / Manage bookings Browse the endpoints in the left navigation bar to get started.
7
7
 
8
- The version of the OpenAPI document: 30.7.10
8
+ The version of the OpenAPI document: 30.9.11
9
9
  Contact: bjorn@wink.travel
10
10
  Generated by OpenAPI Generator (https://openapi-generator.tech)
11
11
 
{wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/aggregate_descriptor_agent.py RENAMED
@@ -5,7 +5,7 @@
5
5
 
6
6
  # Introduction Welcome to the Wink API - A programmer-friendly way to manage, sell and book travel blocking on the Wink platform. The API gives you all the tools you need to ready your properties and blocking for sale across 1000s of our native sales channels. Integrators, affiliates, travel agents and content creators have the ability search for your travel blocking and promote / sell it in a wide variety of ways. # Integrations We have already integrated with the most well-known channel managers so you don't have to. To see our current integrations, please go to https://extranet.wink.travel and scroll to Connectivity section. Once your properties are set up, you can finish the setup by mapping your property to Wink using your channel manager partner portal. If your properties don't have a channel manager, you can easily manage rates and availability with this API. # Intended Audience Programmers are [most likely] a requirement to start integrating with Wink. Companies and organizations that would most benefit from integrating with us are new and existing travel companies that have relationships with suppliers and that need an advanced system from which to manage their travel blocking and get that same blocking out to as many eyeballs as possible at the lowest price possible. - Hotel chains - Hotel brands - Travel tech companies - Destination sites - Integrators - Aggregators - Destination management companies - Travel agencies - OTAs ## APIs Not every integrator needs every API. For that reason, we have separated APIs into context. ### Test API - [Ping](/ping): The Ping API is a quick test endpoint to verify that your credentials work Wink. ### Common APIs - [Notifications](/notifications): The Notifications API is a way for us to stay in touch with your user, property or affiliate account. - [User Settings](/user-settings): The User Settings API exposes endpoints to allow 3rd party integrators to communicate with Wink. ### Consume APIs Consume endpoints are for developers who want to find existing travel blocking and either book it or use it to advertise through one of their Wink affiliate accounts. - [Configuration](/engine-client): A single endpoint to retrieve whitelabel + customization information for the booking engine. - [Lookup](/lookup): All APIs related to locating blocking by region, locale and property flags. - [Inventory](/blocking): All APIs related to retrieve known travel blocking as it was found using the Lookup API.. - [Booking](/booking): All APIs related to creating bookings on the platform. - [Travel Agent](/travel-agent): The Travel Agent API exposes endpoints to manage agent-facilitated bookings. ### Produce APIs Produce endpoints are for developers who want to create and manage travel blocking. #### Property - [Property registration](/extranet/property/register): As a producer, this is, oftentimes, where you start your journey. These endpoints let you create properties on Wink. - [Property](/extranet/property): This collection of property endpoints are mostly management endpoints that let you display, change status and similar for your existing properties. - [Facilities](/extranet/facilities): This collection of endpoints let you manage facilities; such as room types. - [Experiences](/extranet/experiences): This collection of endpoints let you manage experiences, such as activities. - [Monetize](/extranet/monetize): The Monetize API exposes endpoints for managing cancellation polies, rate plans, promotions and more on Wink. - [Distribution](/extranet/distribution): The Distribution API exposes endpoints for sales channels, connecting with affiliates, managing rates and blocking calendars and more on Wink. - [Property Booking](/extranet/booking): The Property Booking API exposes endpoints for managing bookings and reviews at the property-level. #### Affiliate - [Affiliate](/affiliate): This collection of affiliate endpoints are mostly management endpoints that let you display, change status and similar for your existing accounts. - [Browse](/affiliate/browse): The Browse API exposes endpoints for affiliates to find suppliers and blocking to sell. - [Inventory](/affiliate/blocking): The Inventory API exposes endpoints for affiliates to manage the blocking they want to sell and how they want to sell it. - [Sales Channel](/affiliate/sales-channel): The Sales Channel API exposes endpoints for affiliates to manage existing sales channels as well as find new ones. - [WinkLinks](/affiliate/winklinks): The WinkLinks API exposes endpoints for affiliates to manage their WinkLinks page. #### Rate provider - [Channel manager](/channel-manager): The Channel Manager API enables external channel manager partners to map, exchange rate / availability information with us as well as be informed of bookings that occur on the Wink platform for one of their properties. ### Taxonomy APIs Taxonomy endpoints are for developers who want to consume and produce travel blocking and need taxonomies of standard and non-standard codes for blocking types, classes, statuses etc. - [Reference](/reactive): All APIs related to retrieving platform-supported taxonomies. ### Insight APIs Insight endpoints do exactly what the name implies - They offer platform-level insight into the activities of producers and consumers. - [Analytics](/analytics): All APIs related to tracking metrics across a wide variety of data source segments including, more entertaining, leaderboard metrics. ### Payment APIs Payment endpoints are for developers who want to purchase travel blocking. This can be done via the API as a registered Travel Agent or using our API in conjunction with our PCI compliant reactive widget for all other entities. - [TripPay](/reactive): All APIs related to TripPay account management, booking, mapping and integration features. ## SDKs We are actively working on supporting the most used languages out there. If you don't see your language here, reach out to us with a request to officially add your language. In the meantime, if you want to roll your own SDK, you can do so by downloading the OpenAPI spec and using one of the many available OpenAPI generators available: [https://openapi-generator.tech/docs/generators](https://openapi-generator.tech/docs/generators). - Java SDK [https://github.com/wink-travel/wink-sdk-java](https://github.com/wink-travel/wink-sdk-java) ## Usage These features are made available to you via a [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer). This API is language agnostic. ## Versioning We chose to version our endpoints in a way that we hope affects your integration minimally. You request the version of our API you wish to work with via the `Wink-Version` header. When it's time for you to upgrade, you only have to change the version number to get access to our updated endpoints. ## Release history - Follow updates on Github: https://github.com/wink-travel/wink-sdk-java/blob/master/CHANGELOG.md # Travel Agent API The Travel Agent API exposes endpoints to manage agent-facilitated bookings. This API lets you: 1. Travel Agent: Manage agent entity. 2. Booking: Create / Manage bookings Browse the endpoints in the left navigation bar to get started.
7
7
 
8
- The version of the OpenAPI document: 30.7.10
8
+ The version of the OpenAPI document: 30.9.11
9
9
  Contact: bjorn@wink.travel
10
10
  Generated by OpenAPI Generator (https://openapi-generator.tech)
11
11
 
{wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/ancillary_request_agent.py RENAMED
@@ -5,7 +5,7 @@
5
5
 
6
6
  # Introduction Welcome to the Wink API - A programmer-friendly way to manage, sell and book travel blocking on the Wink platform. The API gives you all the tools you need to ready your properties and blocking for sale across 1000s of our native sales channels. Integrators, affiliates, travel agents and content creators have the ability search for your travel blocking and promote / sell it in a wide variety of ways. # Integrations We have already integrated with the most well-known channel managers so you don't have to. To see our current integrations, please go to https://extranet.wink.travel and scroll to Connectivity section. Once your properties are set up, you can finish the setup by mapping your property to Wink using your channel manager partner portal. If your properties don't have a channel manager, you can easily manage rates and availability with this API. # Intended Audience Programmers are [most likely] a requirement to start integrating with Wink. Companies and organizations that would most benefit from integrating with us are new and existing travel companies that have relationships with suppliers and that need an advanced system from which to manage their travel blocking and get that same blocking out to as many eyeballs as possible at the lowest price possible. - Hotel chains - Hotel brands - Travel tech companies - Destination sites - Integrators - Aggregators - Destination management companies - Travel agencies - OTAs ## APIs Not every integrator needs every API. For that reason, we have separated APIs into context. ### Test API - [Ping](/ping): The Ping API is a quick test endpoint to verify that your credentials work Wink. ### Common APIs - [Notifications](/notifications): The Notifications API is a way for us to stay in touch with your user, property or affiliate account. - [User Settings](/user-settings): The User Settings API exposes endpoints to allow 3rd party integrators to communicate with Wink. ### Consume APIs Consume endpoints are for developers who want to find existing travel blocking and either book it or use it to advertise through one of their Wink affiliate accounts. - [Configuration](/engine-client): A single endpoint to retrieve whitelabel + customization information for the booking engine. - [Lookup](/lookup): All APIs related to locating blocking by region, locale and property flags. - [Inventory](/blocking): All APIs related to retrieve known travel blocking as it was found using the Lookup API.. - [Booking](/booking): All APIs related to creating bookings on the platform. - [Travel Agent](/travel-agent): The Travel Agent API exposes endpoints to manage agent-facilitated bookings. ### Produce APIs Produce endpoints are for developers who want to create and manage travel blocking. #### Property - [Property registration](/extranet/property/register): As a producer, this is, oftentimes, where you start your journey. These endpoints let you create properties on Wink. - [Property](/extranet/property): This collection of property endpoints are mostly management endpoints that let you display, change status and similar for your existing properties. - [Facilities](/extranet/facilities): This collection of endpoints let you manage facilities; such as room types. - [Experiences](/extranet/experiences): This collection of endpoints let you manage experiences, such as activities. - [Monetize](/extranet/monetize): The Monetize API exposes endpoints for managing cancellation polies, rate plans, promotions and more on Wink. - [Distribution](/extranet/distribution): The Distribution API exposes endpoints for sales channels, connecting with affiliates, managing rates and blocking calendars and more on Wink. - [Property Booking](/extranet/booking): The Property Booking API exposes endpoints for managing bookings and reviews at the property-level. #### Affiliate - [Affiliate](/affiliate): This collection of affiliate endpoints are mostly management endpoints that let you display, change status and similar for your existing accounts. - [Browse](/affiliate/browse): The Browse API exposes endpoints for affiliates to find suppliers and blocking to sell. - [Inventory](/affiliate/blocking): The Inventory API exposes endpoints for affiliates to manage the blocking they want to sell and how they want to sell it. - [Sales Channel](/affiliate/sales-channel): The Sales Channel API exposes endpoints for affiliates to manage existing sales channels as well as find new ones. - [WinkLinks](/affiliate/winklinks): The WinkLinks API exposes endpoints for affiliates to manage their WinkLinks page. #### Rate provider - [Channel manager](/channel-manager): The Channel Manager API enables external channel manager partners to map, exchange rate / availability information with us as well as be informed of bookings that occur on the Wink platform for one of their properties. ### Taxonomy APIs Taxonomy endpoints are for developers who want to consume and produce travel blocking and need taxonomies of standard and non-standard codes for blocking types, classes, statuses etc. - [Reference](/reactive): All APIs related to retrieving platform-supported taxonomies. ### Insight APIs Insight endpoints do exactly what the name implies - They offer platform-level insight into the activities of producers and consumers. - [Analytics](/analytics): All APIs related to tracking metrics across a wide variety of data source segments including, more entertaining, leaderboard metrics. ### Payment APIs Payment endpoints are for developers who want to purchase travel blocking. This can be done via the API as a registered Travel Agent or using our API in conjunction with our PCI compliant reactive widget for all other entities. - [TripPay](/reactive): All APIs related to TripPay account management, booking, mapping and integration features. ## SDKs We are actively working on supporting the most used languages out there. If you don't see your language here, reach out to us with a request to officially add your language. In the meantime, if you want to roll your own SDK, you can do so by downloading the OpenAPI spec and using one of the many available OpenAPI generators available: [https://openapi-generator.tech/docs/generators](https://openapi-generator.tech/docs/generators). - Java SDK [https://github.com/wink-travel/wink-sdk-java](https://github.com/wink-travel/wink-sdk-java) ## Usage These features are made available to you via a [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer). This API is language agnostic. ## Versioning We chose to version our endpoints in a way that we hope affects your integration minimally. You request the version of our API you wish to work with via the `Wink-Version` header. When it's time for you to upgrade, you only have to change the version number to get access to our updated endpoints. ## Release history - Follow updates on Github: https://github.com/wink-travel/wink-sdk-java/blob/master/CHANGELOG.md # Travel Agent API The Travel Agent API exposes endpoints to manage agent-facilitated bookings. This API lets you: 1. Travel Agent: Manage agent entity. 2. Booking: Create / Manage bookings Browse the endpoints in the left navigation bar to get started.
7
7
 
8
- The version of the OpenAPI document: 30.7.10
8
+ The version of the OpenAPI document: 30.9.11
9
9
  Contact: bjorn@wink.travel
10
10
  Generated by OpenAPI Generator (https://openapi-generator.tech)
11
11
 
{wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/authenticated_user_agent.py RENAMED
@@ -5,7 +5,7 @@
5
5
 
6
6
  # Introduction Welcome to the Wink API - A programmer-friendly way to manage, sell and book travel blocking on the Wink platform. The API gives you all the tools you need to ready your properties and blocking for sale across 1000s of our native sales channels. Integrators, affiliates, travel agents and content creators have the ability search for your travel blocking and promote / sell it in a wide variety of ways. # Integrations We have already integrated with the most well-known channel managers so you don't have to. To see our current integrations, please go to https://extranet.wink.travel and scroll to Connectivity section. Once your properties are set up, you can finish the setup by mapping your property to Wink using your channel manager partner portal. If your properties don't have a channel manager, you can easily manage rates and availability with this API. # Intended Audience Programmers are [most likely] a requirement to start integrating with Wink. Companies and organizations that would most benefit from integrating with us are new and existing travel companies that have relationships with suppliers and that need an advanced system from which to manage their travel blocking and get that same blocking out to as many eyeballs as possible at the lowest price possible. - Hotel chains - Hotel brands - Travel tech companies - Destination sites - Integrators - Aggregators - Destination management companies - Travel agencies - OTAs ## APIs Not every integrator needs every API. For that reason, we have separated APIs into context. ### Test API - [Ping](/ping): The Ping API is a quick test endpoint to verify that your credentials work Wink. ### Common APIs - [Notifications](/notifications): The Notifications API is a way for us to stay in touch with your user, property or affiliate account. - [User Settings](/user-settings): The User Settings API exposes endpoints to allow 3rd party integrators to communicate with Wink. ### Consume APIs Consume endpoints are for developers who want to find existing travel blocking and either book it or use it to advertise through one of their Wink affiliate accounts. - [Configuration](/engine-client): A single endpoint to retrieve whitelabel + customization information for the booking engine. - [Lookup](/lookup): All APIs related to locating blocking by region, locale and property flags. - [Inventory](/blocking): All APIs related to retrieve known travel blocking as it was found using the Lookup API.. - [Booking](/booking): All APIs related to creating bookings on the platform. - [Travel Agent](/travel-agent): The Travel Agent API exposes endpoints to manage agent-facilitated bookings. ### Produce APIs Produce endpoints are for developers who want to create and manage travel blocking. #### Property - [Property registration](/extranet/property/register): As a producer, this is, oftentimes, where you start your journey. These endpoints let you create properties on Wink. - [Property](/extranet/property): This collection of property endpoints are mostly management endpoints that let you display, change status and similar for your existing properties. - [Facilities](/extranet/facilities): This collection of endpoints let you manage facilities; such as room types. - [Experiences](/extranet/experiences): This collection of endpoints let you manage experiences, such as activities. - [Monetize](/extranet/monetize): The Monetize API exposes endpoints for managing cancellation polies, rate plans, promotions and more on Wink. - [Distribution](/extranet/distribution): The Distribution API exposes endpoints for sales channels, connecting with affiliates, managing rates and blocking calendars and more on Wink. - [Property Booking](/extranet/booking): The Property Booking API exposes endpoints for managing bookings and reviews at the property-level. #### Affiliate - [Affiliate](/affiliate): This collection of affiliate endpoints are mostly management endpoints that let you display, change status and similar for your existing accounts. - [Browse](/affiliate/browse): The Browse API exposes endpoints for affiliates to find suppliers and blocking to sell. - [Inventory](/affiliate/blocking): The Inventory API exposes endpoints for affiliates to manage the blocking they want to sell and how they want to sell it. - [Sales Channel](/affiliate/sales-channel): The Sales Channel API exposes endpoints for affiliates to manage existing sales channels as well as find new ones. - [WinkLinks](/affiliate/winklinks): The WinkLinks API exposes endpoints for affiliates to manage their WinkLinks page. #### Rate provider - [Channel manager](/channel-manager): The Channel Manager API enables external channel manager partners to map, exchange rate / availability information with us as well as be informed of bookings that occur on the Wink platform for one of their properties. ### Taxonomy APIs Taxonomy endpoints are for developers who want to consume and produce travel blocking and need taxonomies of standard and non-standard codes for blocking types, classes, statuses etc. - [Reference](/reactive): All APIs related to retrieving platform-supported taxonomies. ### Insight APIs Insight endpoints do exactly what the name implies - They offer platform-level insight into the activities of producers and consumers. - [Analytics](/analytics): All APIs related to tracking metrics across a wide variety of data source segments including, more entertaining, leaderboard metrics. ### Payment APIs Payment endpoints are for developers who want to purchase travel blocking. This can be done via the API as a registered Travel Agent or using our API in conjunction with our PCI compliant reactive widget for all other entities. - [TripPay](/reactive): All APIs related to TripPay account management, booking, mapping and integration features. ## SDKs We are actively working on supporting the most used languages out there. If you don't see your language here, reach out to us with a request to officially add your language. In the meantime, if you want to roll your own SDK, you can do so by downloading the OpenAPI spec and using one of the many available OpenAPI generators available: [https://openapi-generator.tech/docs/generators](https://openapi-generator.tech/docs/generators). - Java SDK [https://github.com/wink-travel/wink-sdk-java](https://github.com/wink-travel/wink-sdk-java) ## Usage These features are made available to you via a [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer). This API is language agnostic. ## Versioning We chose to version our endpoints in a way that we hope affects your integration minimally. You request the version of our API you wish to work with via the `Wink-Version` header. When it's time for you to upgrade, you only have to change the version number to get access to our updated endpoints. ## Release history - Follow updates on Github: https://github.com/wink-travel/wink-sdk-java/blob/master/CHANGELOG.md # Travel Agent API The Travel Agent API exposes endpoints to manage agent-facilitated bookings. This API lets you: 1. Travel Agent: Manage agent entity. 2. Booking: Create / Manage bookings Browse the endpoints in the left navigation bar to get started.
7
7
 
8
- The version of the OpenAPI document: 30.7.10
8
+ The version of the OpenAPI document: 30.9.11
9
9
  Contact: bjorn@wink.travel
10
10
  Generated by OpenAPI Generator (https://openapi-generator.tech)
11
11
 
{wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/bed_agent.py RENAMED
@@ -5,7 +5,7 @@
5
5
 
6
6
  # Introduction Welcome to the Wink API - A programmer-friendly way to manage, sell and book travel blocking on the Wink platform. The API gives you all the tools you need to ready your properties and blocking for sale across 1000s of our native sales channels. Integrators, affiliates, travel agents and content creators have the ability search for your travel blocking and promote / sell it in a wide variety of ways. # Integrations We have already integrated with the most well-known channel managers so you don't have to. To see our current integrations, please go to https://extranet.wink.travel and scroll to Connectivity section. Once your properties are set up, you can finish the setup by mapping your property to Wink using your channel manager partner portal. If your properties don't have a channel manager, you can easily manage rates and availability with this API. # Intended Audience Programmers are [most likely] a requirement to start integrating with Wink. Companies and organizations that would most benefit from integrating with us are new and existing travel companies that have relationships with suppliers and that need an advanced system from which to manage their travel blocking and get that same blocking out to as many eyeballs as possible at the lowest price possible. - Hotel chains - Hotel brands - Travel tech companies - Destination sites - Integrators - Aggregators - Destination management companies - Travel agencies - OTAs ## APIs Not every integrator needs every API. For that reason, we have separated APIs into context. ### Test API - [Ping](/ping): The Ping API is a quick test endpoint to verify that your credentials work Wink. ### Common APIs - [Notifications](/notifications): The Notifications API is a way for us to stay in touch with your user, property or affiliate account. - [User Settings](/user-settings): The User Settings API exposes endpoints to allow 3rd party integrators to communicate with Wink. ### Consume APIs Consume endpoints are for developers who want to find existing travel blocking and either book it or use it to advertise through one of their Wink affiliate accounts. - [Configuration](/engine-client): A single endpoint to retrieve whitelabel + customization information for the booking engine. - [Lookup](/lookup): All APIs related to locating blocking by region, locale and property flags. - [Inventory](/blocking): All APIs related to retrieve known travel blocking as it was found using the Lookup API.. - [Booking](/booking): All APIs related to creating bookings on the platform. - [Travel Agent](/travel-agent): The Travel Agent API exposes endpoints to manage agent-facilitated bookings. ### Produce APIs Produce endpoints are for developers who want to create and manage travel blocking. #### Property - [Property registration](/extranet/property/register): As a producer, this is, oftentimes, where you start your journey. These endpoints let you create properties on Wink. - [Property](/extranet/property): This collection of property endpoints are mostly management endpoints that let you display, change status and similar for your existing properties. - [Facilities](/extranet/facilities): This collection of endpoints let you manage facilities; such as room types. - [Experiences](/extranet/experiences): This collection of endpoints let you manage experiences, such as activities. - [Monetize](/extranet/monetize): The Monetize API exposes endpoints for managing cancellation polies, rate plans, promotions and more on Wink. - [Distribution](/extranet/distribution): The Distribution API exposes endpoints for sales channels, connecting with affiliates, managing rates and blocking calendars and more on Wink. - [Property Booking](/extranet/booking): The Property Booking API exposes endpoints for managing bookings and reviews at the property-level. #### Affiliate - [Affiliate](/affiliate): This collection of affiliate endpoints are mostly management endpoints that let you display, change status and similar for your existing accounts. - [Browse](/affiliate/browse): The Browse API exposes endpoints for affiliates to find suppliers and blocking to sell. - [Inventory](/affiliate/blocking): The Inventory API exposes endpoints for affiliates to manage the blocking they want to sell and how they want to sell it. - [Sales Channel](/affiliate/sales-channel): The Sales Channel API exposes endpoints for affiliates to manage existing sales channels as well as find new ones. - [WinkLinks](/affiliate/winklinks): The WinkLinks API exposes endpoints for affiliates to manage their WinkLinks page. #### Rate provider - [Channel manager](/channel-manager): The Channel Manager API enables external channel manager partners to map, exchange rate / availability information with us as well as be informed of bookings that occur on the Wink platform for one of their properties. ### Taxonomy APIs Taxonomy endpoints are for developers who want to consume and produce travel blocking and need taxonomies of standard and non-standard codes for blocking types, classes, statuses etc. - [Reference](/reactive): All APIs related to retrieving platform-supported taxonomies. ### Insight APIs Insight endpoints do exactly what the name implies - They offer platform-level insight into the activities of producers and consumers. - [Analytics](/analytics): All APIs related to tracking metrics across a wide variety of data source segments including, more entertaining, leaderboard metrics. ### Payment APIs Payment endpoints are for developers who want to purchase travel blocking. This can be done via the API as a registered Travel Agent or using our API in conjunction with our PCI compliant reactive widget for all other entities. - [TripPay](/reactive): All APIs related to TripPay account management, booking, mapping and integration features. ## SDKs We are actively working on supporting the most used languages out there. If you don't see your language here, reach out to us with a request to officially add your language. In the meantime, if you want to roll your own SDK, you can do so by downloading the OpenAPI spec and using one of the many available OpenAPI generators available: [https://openapi-generator.tech/docs/generators](https://openapi-generator.tech/docs/generators). - Java SDK [https://github.com/wink-travel/wink-sdk-java](https://github.com/wink-travel/wink-sdk-java) ## Usage These features are made available to you via a [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer). This API is language agnostic. ## Versioning We chose to version our endpoints in a way that we hope affects your integration minimally. You request the version of our API you wish to work with via the `Wink-Version` header. When it's time for you to upgrade, you only have to change the version number to get access to our updated endpoints. ## Release history - Follow updates on Github: https://github.com/wink-travel/wink-sdk-java/blob/master/CHANGELOG.md # Travel Agent API The Travel Agent API exposes endpoints to manage agent-facilitated bookings. This API lets you: 1. Travel Agent: Manage agent entity. 2. Booking: Create / Manage bookings Browse the endpoints in the left navigation bar to get started.
7
7
 
8
- The version of the OpenAPI document: 30.7.10
8
+ The version of the OpenAPI document: 30.9.11
9
9
  Contact: bjorn@wink.travel
10
10
  Generated by OpenAPI Generator (https://openapi-generator.tech)
11
11
 
{wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/bedroom_agent.py RENAMED
@@ -5,7 +5,7 @@
5
5
 
6
6
  # Introduction Welcome to the Wink API - A programmer-friendly way to manage, sell and book travel blocking on the Wink platform. The API gives you all the tools you need to ready your properties and blocking for sale across 1000s of our native sales channels. Integrators, affiliates, travel agents and content creators have the ability search for your travel blocking and promote / sell it in a wide variety of ways. # Integrations We have already integrated with the most well-known channel managers so you don't have to. To see our current integrations, please go to https://extranet.wink.travel and scroll to Connectivity section. Once your properties are set up, you can finish the setup by mapping your property to Wink using your channel manager partner portal. If your properties don't have a channel manager, you can easily manage rates and availability with this API. # Intended Audience Programmers are [most likely] a requirement to start integrating with Wink. Companies and organizations that would most benefit from integrating with us are new and existing travel companies that have relationships with suppliers and that need an advanced system from which to manage their travel blocking and get that same blocking out to as many eyeballs as possible at the lowest price possible. - Hotel chains - Hotel brands - Travel tech companies - Destination sites - Integrators - Aggregators - Destination management companies - Travel agencies - OTAs ## APIs Not every integrator needs every API. For that reason, we have separated APIs into context. ### Test API - [Ping](/ping): The Ping API is a quick test endpoint to verify that your credentials work Wink. ### Common APIs - [Notifications](/notifications): The Notifications API is a way for us to stay in touch with your user, property or affiliate account. - [User Settings](/user-settings): The User Settings API exposes endpoints to allow 3rd party integrators to communicate with Wink. ### Consume APIs Consume endpoints are for developers who want to find existing travel blocking and either book it or use it to advertise through one of their Wink affiliate accounts. - [Configuration](/engine-client): A single endpoint to retrieve whitelabel + customization information for the booking engine. - [Lookup](/lookup): All APIs related to locating blocking by region, locale and property flags. - [Inventory](/blocking): All APIs related to retrieve known travel blocking as it was found using the Lookup API.. - [Booking](/booking): All APIs related to creating bookings on the platform. - [Travel Agent](/travel-agent): The Travel Agent API exposes endpoints to manage agent-facilitated bookings. ### Produce APIs Produce endpoints are for developers who want to create and manage travel blocking. #### Property - [Property registration](/extranet/property/register): As a producer, this is, oftentimes, where you start your journey. These endpoints let you create properties on Wink. - [Property](/extranet/property): This collection of property endpoints are mostly management endpoints that let you display, change status and similar for your existing properties. - [Facilities](/extranet/facilities): This collection of endpoints let you manage facilities; such as room types. - [Experiences](/extranet/experiences): This collection of endpoints let you manage experiences, such as activities. - [Monetize](/extranet/monetize): The Monetize API exposes endpoints for managing cancellation polies, rate plans, promotions and more on Wink. - [Distribution](/extranet/distribution): The Distribution API exposes endpoints for sales channels, connecting with affiliates, managing rates and blocking calendars and more on Wink. - [Property Booking](/extranet/booking): The Property Booking API exposes endpoints for managing bookings and reviews at the property-level. #### Affiliate - [Affiliate](/affiliate): This collection of affiliate endpoints are mostly management endpoints that let you display, change status and similar for your existing accounts. - [Browse](/affiliate/browse): The Browse API exposes endpoints for affiliates to find suppliers and blocking to sell. - [Inventory](/affiliate/blocking): The Inventory API exposes endpoints for affiliates to manage the blocking they want to sell and how they want to sell it. - [Sales Channel](/affiliate/sales-channel): The Sales Channel API exposes endpoints for affiliates to manage existing sales channels as well as find new ones. - [WinkLinks](/affiliate/winklinks): The WinkLinks API exposes endpoints for affiliates to manage their WinkLinks page. #### Rate provider - [Channel manager](/channel-manager): The Channel Manager API enables external channel manager partners to map, exchange rate / availability information with us as well as be informed of bookings that occur on the Wink platform for one of their properties. ### Taxonomy APIs Taxonomy endpoints are for developers who want to consume and produce travel blocking and need taxonomies of standard and non-standard codes for blocking types, classes, statuses etc. - [Reference](/reactive): All APIs related to retrieving platform-supported taxonomies. ### Insight APIs Insight endpoints do exactly what the name implies - They offer platform-level insight into the activities of producers and consumers. - [Analytics](/analytics): All APIs related to tracking metrics across a wide variety of data source segments including, more entertaining, leaderboard metrics. ### Payment APIs Payment endpoints are for developers who want to purchase travel blocking. This can be done via the API as a registered Travel Agent or using our API in conjunction with our PCI compliant reactive widget for all other entities. - [TripPay](/reactive): All APIs related to TripPay account management, booking, mapping and integration features. ## SDKs We are actively working on supporting the most used languages out there. If you don't see your language here, reach out to us with a request to officially add your language. In the meantime, if you want to roll your own SDK, you can do so by downloading the OpenAPI spec and using one of the many available OpenAPI generators available: [https://openapi-generator.tech/docs/generators](https://openapi-generator.tech/docs/generators). - Java SDK [https://github.com/wink-travel/wink-sdk-java](https://github.com/wink-travel/wink-sdk-java) ## Usage These features are made available to you via a [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer). This API is language agnostic. ## Versioning We chose to version our endpoints in a way that we hope affects your integration minimally. You request the version of our API you wish to work with via the `Wink-Version` header. When it's time for you to upgrade, you only have to change the version number to get access to our updated endpoints. ## Release history - Follow updates on Github: https://github.com/wink-travel/wink-sdk-java/blob/master/CHANGELOG.md # Travel Agent API The Travel Agent API exposes endpoints to manage agent-facilitated bookings. This API lets you: 1. Travel Agent: Manage agent entity. 2. Booking: Create / Manage bookings Browse the endpoints in the left navigation bar to get started.
7
7
 
8
- The version of the OpenAPI document: 30.7.10
8
+ The version of the OpenAPI document: 30.9.11
9
9
  Contact: bjorn@wink.travel
10
10
  Generated by OpenAPI Generator (https://openapi-generator.tech)
11
11
 
{wink_sdk_travel_agent-0.0.3 → wink_sdk_travel_agent-0.0.4}/wink_sdk_travel_agent/models/bedroom_configuration_agent.py RENAMED
@@ -5,7 +5,7 @@
5
5
 
6
6
  # Introduction Welcome to the Wink API - A programmer-friendly way to manage, sell and book travel blocking on the Wink platform. The API gives you all the tools you need to ready your properties and blocking for sale across 1000s of our native sales channels. Integrators, affiliates, travel agents and content creators have the ability search for your travel blocking and promote / sell it in a wide variety of ways. # Integrations We have already integrated with the most well-known channel managers so you don't have to. To see our current integrations, please go to https://extranet.wink.travel and scroll to Connectivity section. Once your properties are set up, you can finish the setup by mapping your property to Wink using your channel manager partner portal. If your properties don't have a channel manager, you can easily manage rates and availability with this API. # Intended Audience Programmers are [most likely] a requirement to start integrating with Wink. Companies and organizations that would most benefit from integrating with us are new and existing travel companies that have relationships with suppliers and that need an advanced system from which to manage their travel blocking and get that same blocking out to as many eyeballs as possible at the lowest price possible. - Hotel chains - Hotel brands - Travel tech companies - Destination sites - Integrators - Aggregators - Destination management companies - Travel agencies - OTAs ## APIs Not every integrator needs every API. For that reason, we have separated APIs into context. ### Test API - [Ping](/ping): The Ping API is a quick test endpoint to verify that your credentials work Wink. ### Common APIs - [Notifications](/notifications): The Notifications API is a way for us to stay in touch with your user, property or affiliate account. - [User Settings](/user-settings): The User Settings API exposes endpoints to allow 3rd party integrators to communicate with Wink. ### Consume APIs Consume endpoints are for developers who want to find existing travel blocking and either book it or use it to advertise through one of their Wink affiliate accounts. - [Configuration](/engine-client): A single endpoint to retrieve whitelabel + customization information for the booking engine. - [Lookup](/lookup): All APIs related to locating blocking by region, locale and property flags. - [Inventory](/blocking): All APIs related to retrieve known travel blocking as it was found using the Lookup API.. - [Booking](/booking): All APIs related to creating bookings on the platform. - [Travel Agent](/travel-agent): The Travel Agent API exposes endpoints to manage agent-facilitated bookings. ### Produce APIs Produce endpoints are for developers who want to create and manage travel blocking. #### Property - [Property registration](/extranet/property/register): As a producer, this is, oftentimes, where you start your journey. These endpoints let you create properties on Wink. - [Property](/extranet/property): This collection of property endpoints are mostly management endpoints that let you display, change status and similar for your existing properties. - [Facilities](/extranet/facilities): This collection of endpoints let you manage facilities; such as room types. - [Experiences](/extranet/experiences): This collection of endpoints let you manage experiences, such as activities. - [Monetize](/extranet/monetize): The Monetize API exposes endpoints for managing cancellation polies, rate plans, promotions and more on Wink. - [Distribution](/extranet/distribution): The Distribution API exposes endpoints for sales channels, connecting with affiliates, managing rates and blocking calendars and more on Wink. - [Property Booking](/extranet/booking): The Property Booking API exposes endpoints for managing bookings and reviews at the property-level. #### Affiliate - [Affiliate](/affiliate): This collection of affiliate endpoints are mostly management endpoints that let you display, change status and similar for your existing accounts. - [Browse](/affiliate/browse): The Browse API exposes endpoints for affiliates to find suppliers and blocking to sell. - [Inventory](/affiliate/blocking): The Inventory API exposes endpoints for affiliates to manage the blocking they want to sell and how they want to sell it. - [Sales Channel](/affiliate/sales-channel): The Sales Channel API exposes endpoints for affiliates to manage existing sales channels as well as find new ones. - [WinkLinks](/affiliate/winklinks): The WinkLinks API exposes endpoints for affiliates to manage their WinkLinks page. #### Rate provider - [Channel manager](/channel-manager): The Channel Manager API enables external channel manager partners to map, exchange rate / availability information with us as well as be informed of bookings that occur on the Wink platform for one of their properties. ### Taxonomy APIs Taxonomy endpoints are for developers who want to consume and produce travel blocking and need taxonomies of standard and non-standard codes for blocking types, classes, statuses etc. - [Reference](/reactive): All APIs related to retrieving platform-supported taxonomies. ### Insight APIs Insight endpoints do exactly what the name implies - They offer platform-level insight into the activities of producers and consumers. - [Analytics](/analytics): All APIs related to tracking metrics across a wide variety of data source segments including, more entertaining, leaderboard metrics. ### Payment APIs Payment endpoints are for developers who want to purchase travel blocking. This can be done via the API as a registered Travel Agent or using our API in conjunction with our PCI compliant reactive widget for all other entities. - [TripPay](/reactive): All APIs related to TripPay account management, booking, mapping and integration features. ## SDKs We are actively working on supporting the most used languages out there. If you don't see your language here, reach out to us with a request to officially add your language. In the meantime, if you want to roll your own SDK, you can do so by downloading the OpenAPI spec and using one of the many available OpenAPI generators available: [https://openapi-generator.tech/docs/generators](https://openapi-generator.tech/docs/generators). - Java SDK [https://github.com/wink-travel/wink-sdk-java](https://github.com/wink-travel/wink-sdk-java) ## Usage These features are made available to you via a [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer). This API is language agnostic. ## Versioning We chose to version our endpoints in a way that we hope affects your integration minimally. You request the version of our API you wish to work with via the `Wink-Version` header. When it's time for you to upgrade, you only have to change the version number to get access to our updated endpoints. ## Release history - Follow updates on Github: https://github.com/wink-travel/wink-sdk-java/blob/master/CHANGELOG.md # Travel Agent API The Travel Agent API exposes endpoints to manage agent-facilitated bookings. This API lets you: 1. Travel Agent: Manage agent entity. 2. Booking: Create / Manage bookings Browse the endpoints in the left navigation bar to get started.
7
7
 
8
- The version of the OpenAPI document: 30.7.10
8
+ The version of the OpenAPI document: 30.9.11
9
9
  Contact: bjorn@wink.travel
10
10
  Generated by OpenAPI Generator (https://openapi-generator.tech)
11
11