wink-sdk-travel-agent 0.0.24__py3-none-any.whl → 0.0.26__py3-none-any.whl
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.
- wink_sdk_travel_agent/__init__.py +17 -28
- wink_sdk_travel_agent/api/travel_agent_api.py +29 -29
- wink_sdk_travel_agent/api_client.py +2 -2
- wink_sdk_travel_agent/configuration.py +4 -4
- wink_sdk_travel_agent/exceptions.py +2 -2
- wink_sdk_travel_agent/models/__init__.py +16 -27
- wink_sdk_travel_agent/models/address_agent.py +7 -6
- wink_sdk_travel_agent/models/affiliate_account_agent.py +179 -0
- wink_sdk_travel_agent/models/affiliate_account_user_agent.py +115 -0
- wink_sdk_travel_agent/models/agent_booking_request_agent.py +13 -28
- wink_sdk_travel_agent/models/aggregate_descriptor_agent.py +3 -3
- wink_sdk_travel_agent/models/ancillary_request_agent.py +1 -1
- wink_sdk_travel_agent/models/authenticated_user_agent.py +7 -6
- wink_sdk_travel_agent/models/bed_agent.py +4 -4
- wink_sdk_travel_agent/models/bedroom_agent.py +4 -3
- wink_sdk_travel_agent/models/bedroom_configuration_agent.py +8 -7
- wink_sdk_travel_agent/models/beneficiary_agent.py +13 -21
- wink_sdk_travel_agent/models/beneficiary_charge_agent.py +2 -2
- wink_sdk_travel_agent/models/booking_agent.py +37 -74
- wink_sdk_travel_agent/models/booking_ancillary_agent.py +16 -15
- wink_sdk_travel_agent/models/booking_confirmations_agent.py +8 -16
- wink_sdk_travel_agent/models/booking_contract_agent.py +104 -104
- wink_sdk_travel_agent/models/booking_contract_item_agent.py +13 -21
- wink_sdk_travel_agent/models/booking_contract_payment_details_agent.py +10 -17
- wink_sdk_travel_agent/models/booking_itinerary_agent.py +3 -3
- wink_sdk_travel_agent/models/booking_itinerary_room_configuration_agent.py +4 -4
- wink_sdk_travel_agent/models/booking_itinerary_room_configuration_child_agent.py +2 -2
- wink_sdk_travel_agent/models/booking_user_agent.py +7 -6
- wink_sdk_travel_agent/models/booking_user_request_agent.py +3 -3
- wink_sdk_travel_agent/models/booking_user_session_agent.py +4 -4
- wink_sdk_travel_agent/models/booking_view_agent.py +2 -2
- wink_sdk_travel_agent/models/boolean_response_agent.py +2 -2
- wink_sdk_travel_agent/models/cancellation_detail_agent.py +4 -3
- wink_sdk_travel_agent/models/cancellation_policy_agent.py +1 -1
- wink_sdk_travel_agent/models/cancellation_policy_exception_agent.py +8 -7
- wink_sdk_travel_agent/models/cancellation_policy_exceptions_agent.py +5 -4
- wink_sdk_travel_agent/models/cancellation_policy_lightweight_agent.py +166 -0
- wink_sdk_travel_agent/models/child_agent.py +2 -2
- wink_sdk_travel_agent/models/commissionable_entry_agent.py +6 -5
- wink_sdk_travel_agent/models/company_agent.py +1 -1
- wink_sdk_travel_agent/models/company_user_agent.py +1 -1
- wink_sdk_travel_agent/models/company_view_agent.py +1 -1
- wink_sdk_travel_agent/models/composite_filter_descriptor_agent.py +3 -3
- wink_sdk_travel_agent/models/contact_agent.py +3 -3
- wink_sdk_travel_agent/models/country_agent.py +1 -1
- wink_sdk_travel_agent/models/country_lightweight_agent.py +100 -0
- wink_sdk_travel_agent/models/create_agent_booking400_response.py +3 -3
- wink_sdk_travel_agent/models/create_agent_booking_request_agent.py +7 -6
- wink_sdk_travel_agent/models/custom_monetary_amount.py +5 -4
- wink_sdk_travel_agent/models/customization_lightweight_agent.py +231 -0
- wink_sdk_travel_agent/models/customization_theme_colors_agent.py +108 -0
- wink_sdk_travel_agent/models/daily_rate_agent.py +1 -1
- wink_sdk_travel_agent/models/engine_configuration_booking_report_agent.py +1 -1
- wink_sdk_travel_agent/models/engine_configuration_theme_colors_agent.py +1 -1
- wink_sdk_travel_agent/models/extra_charge_agent.py +6 -6
- wink_sdk_travel_agent/models/extra_charges_agent.py +3 -3
- wink_sdk_travel_agent/models/fee_agent.py +1 -1
- wink_sdk_travel_agent/models/filter_descriptor_agent.py +11 -5
- wink_sdk_travel_agent/models/general_manager_agent.py +4 -4
- wink_sdk_travel_agent/models/generic_error_message.py +2 -2
- wink_sdk_travel_agent/models/geo_json_point_agent.py +3 -3
- wink_sdk_travel_agent/models/geo_name_agent.py +1 -1
- wink_sdk_travel_agent/models/geo_name_lightweight_agent.py +136 -0
- wink_sdk_travel_agent/models/group_descriptor_agent.py +3 -3
- wink_sdk_travel_agent/models/guest_room_lightweight_agent.py +22 -22
- wink_sdk_travel_agent/models/guest_user_agent.py +9 -8
- wink_sdk_travel_agent/models/hotel_on_map_agent.py +1 -1
- wink_sdk_travel_agent/models/image_attribution_agent.py +5 -4
- wink_sdk_travel_agent/models/localized_description_agent.py +25 -7
- wink_sdk_travel_agent/models/localized_price_agent.py +18 -18
- wink_sdk_travel_agent/models/managed_by_entity_agent.py +8 -7
- wink_sdk_travel_agent/models/managed_by_entity_rules_agent.py +3 -3
- wink_sdk_travel_agent/models/online_presence_agent.py +1 -1
- wink_sdk_travel_agent/models/page_booking_agent.py +124 -0
- wink_sdk_travel_agent/models/page_booking_view_agent.py +1 -1
- wink_sdk_travel_agent/models/pageable_object_agent.py +6 -6
- wink_sdk_travel_agent/models/payout_agent.py +10 -9
- wink_sdk_travel_agent/models/payout_fee_agent.py +7 -6
- wink_sdk_travel_agent/models/pending_refund_agent.py +1 -1
- wink_sdk_travel_agent/models/perk_lightweight_agent.py +7 -6
- wink_sdk_travel_agent/models/personal_agent.py +8 -24
- wink_sdk_travel_agent/models/pet_info_dto_agent.py +1 -1
- wink_sdk_travel_agent/models/preferences_agent.py +13 -13
- wink_sdk_travel_agent/models/profile_agent.py +1 -1
- wink_sdk_travel_agent/models/profile_lightweight_agent.py +111 -0
- wink_sdk_travel_agent/models/profile_user_agent.py +3 -3
- wink_sdk_travel_agent/models/property_aggregate_lightweight_agent.py +242 -0
- wink_sdk_travel_agent/models/property_policy_agent.py +6 -5
- wink_sdk_travel_agent/models/quote_agent.py +1 -1
- wink_sdk_travel_agent/models/quote_lightweight_agent.py +95 -0
- wink_sdk_travel_agent/models/rate_plan_level_fee_agent.py +6 -5
- wink_sdk_travel_agent/models/refund_agent.py +6 -5
- wink_sdk_travel_agent/models/reporting_ancillary_agent.py +1 -1
- wink_sdk_travel_agent/models/reporting_daily_rate_agent.py +1 -1
- wink_sdk_travel_agent/models/reporting_extra_charge_agent.py +1 -1
- wink_sdk_travel_agent/models/review_agent.py +1 -1
- wink_sdk_travel_agent/models/review_answer_agent.py +4 -3
- wink_sdk_travel_agent/models/review_lightweight_agent.py +133 -0
- wink_sdk_travel_agent/models/review_user_agent.py +3 -3
- wink_sdk_travel_agent/models/room_configuration_agent.py +3 -3
- wink_sdk_travel_agent/models/room_configuration_price_rate_plan_agent.py +23 -12
- wink_sdk_travel_agent/models/room_stay_agent.py +23 -22
- wink_sdk_travel_agent/models/simple_address_agent.py +12 -7
- wink_sdk_travel_agent/models/simple_date_time_itinerary_agent.py +6 -6
- wink_sdk_travel_agent/models/simple_description_agent.py +25 -7
- wink_sdk_travel_agent/models/simple_multimedia_agent.py +5 -5
- wink_sdk_travel_agent/models/social_agent.py +2 -2
- wink_sdk_travel_agent/models/sort_descriptor_agent.py +3 -3
- wink_sdk_travel_agent/models/sort_object_agent.py +2 -2
- wink_sdk_travel_agent/models/state_agent.py +3 -3
- wink_sdk_travel_agent/models/stay_rate_agent.py +16 -16
- wink_sdk_travel_agent/models/sub_country_agent.py +1 -1
- wink_sdk_travel_agent/models/sub_country_lightweight_agent.py +92 -0
- wink_sdk_travel_agent/models/sub_sub_country_agent.py +1 -1
- wink_sdk_travel_agent/models/sub_sub_country_lightweight_agent.py +92 -0
- wink_sdk_travel_agent/models/supplier_contract_item_policy_agent.py +2 -2
- wink_sdk_travel_agent/models/travel_agent_agent.py +3 -3
- wink_sdk_travel_agent/models/travel_inventory_recognition_agent.py +4 -4
- wink_sdk_travel_agent/models/upsert_travel_agent_request_agent.py +2 -2
- wink_sdk_travel_agent/rest.py +2 -2
- {wink_sdk_travel_agent-0.0.24.dist-info → wink_sdk_travel_agent-0.0.26.dist-info}/METADATA +20 -31
- wink_sdk_travel_agent-0.0.26.dist-info/RECORD +133 -0
- {wink_sdk_travel_agent-0.0.24.dist-info → wink_sdk_travel_agent-0.0.26.dist-info}/WHEEL +1 -1
- wink_sdk_travel_agent-0.0.24.dist-info/RECORD +0 -119
- {wink_sdk_travel_agent-0.0.24.dist-info → wink_sdk_travel_agent-0.0.26.dist-info}/licenses/LICENSE +0 -0
- {wink_sdk_travel_agent-0.0.24.dist-info → wink_sdk_travel_agent-0.0.26.dist-info}/top_level.txt +0 -0
|
@@ -0,0 +1,92 @@
|
|
|
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 inventory on the Wink platform. The API gives you all the tools you need to ready your properties and inventory for sale across 1000s of our native sales channels. Integrators, affiliates, travel agents and content creators have the ability search for your travel inventory 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 inventory and get that same inventory 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 inventory and either book it or use it to advertise through one of their Wink affiliate accounts. - [Configuration](/customization-client): A single endpoint to retrieve whitelabel + customization information for the booking customization. - [Lookup](/lookup): All APIs related to locating inventory by region, locale and property flags. - [Inventory](/inventory): All APIs related to retrieve known travel inventory 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 inventory. #### 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 inventory 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 inventory to sell. - [Inventory](/affiliate/inventory): The Inventory API exposes endpoints for affiliates to manage the inventory 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 inventory and need taxonomies of standard and non-standard codes for inventory 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 inventory. 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.17.1
|
|
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
|
+
from __future__ import annotations
|
|
17
|
+
import pprint
|
|
18
|
+
import re # noqa: F401
|
|
19
|
+
import json
|
|
20
|
+
|
|
21
|
+
from pydantic import BaseModel, ConfigDict, Field, StrictStr
|
|
22
|
+
from typing import Any, ClassVar, Dict, List, Optional
|
|
23
|
+
from typing import Optional, Set
|
|
24
|
+
from typing_extensions import Self
|
|
25
|
+
|
|
26
|
+
class SubSubCountryLightweightAgent(BaseModel):
|
|
27
|
+
"""
|
|
28
|
+
SubSubCountryLightweightAgent
|
|
29
|
+
""" # noqa: E501
|
|
30
|
+
name: Optional[StrictStr] = None
|
|
31
|
+
ascii_name: Optional[StrictStr] = Field(default=None, alias="asciiName")
|
|
32
|
+
geo_name_id: Optional[StrictStr] = Field(default=None, alias="geoNameId")
|
|
33
|
+
__properties: ClassVar[List[str]] = ["name", "asciiName", "geoNameId"]
|
|
34
|
+
|
|
35
|
+
model_config = ConfigDict(
|
|
36
|
+
populate_by_name=True,
|
|
37
|
+
validate_assignment=True,
|
|
38
|
+
protected_namespaces=(),
|
|
39
|
+
)
|
|
40
|
+
|
|
41
|
+
|
|
42
|
+
def to_str(self) -> str:
|
|
43
|
+
"""Returns the string representation of the model using alias"""
|
|
44
|
+
return pprint.pformat(self.model_dump(by_alias=True))
|
|
45
|
+
|
|
46
|
+
def to_json(self) -> str:
|
|
47
|
+
"""Returns the JSON representation of the model using alias"""
|
|
48
|
+
# TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
|
|
49
|
+
return json.dumps(self.to_dict())
|
|
50
|
+
|
|
51
|
+
@classmethod
|
|
52
|
+
def from_json(cls, json_str: str) -> Optional[Self]:
|
|
53
|
+
"""Create an instance of SubSubCountryLightweightAgent from a JSON string"""
|
|
54
|
+
return cls.from_dict(json.loads(json_str))
|
|
55
|
+
|
|
56
|
+
def to_dict(self) -> Dict[str, Any]:
|
|
57
|
+
"""Return the dictionary representation of the model using alias.
|
|
58
|
+
|
|
59
|
+
This has the following differences from calling pydantic's
|
|
60
|
+
`self.model_dump(by_alias=True)`:
|
|
61
|
+
|
|
62
|
+
* `None` is only added to the output dict for nullable fields that
|
|
63
|
+
were set at model initialization. Other fields with value `None`
|
|
64
|
+
are ignored.
|
|
65
|
+
"""
|
|
66
|
+
excluded_fields: Set[str] = set([
|
|
67
|
+
])
|
|
68
|
+
|
|
69
|
+
_dict = self.model_dump(
|
|
70
|
+
by_alias=True,
|
|
71
|
+
exclude=excluded_fields,
|
|
72
|
+
exclude_none=True,
|
|
73
|
+
)
|
|
74
|
+
return _dict
|
|
75
|
+
|
|
76
|
+
@classmethod
|
|
77
|
+
def from_dict(cls, obj: Optional[Dict[str, Any]]) -> Optional[Self]:
|
|
78
|
+
"""Create an instance of SubSubCountryLightweightAgent from a dict"""
|
|
79
|
+
if obj is None:
|
|
80
|
+
return None
|
|
81
|
+
|
|
82
|
+
if not isinstance(obj, dict):
|
|
83
|
+
return cls.model_validate(obj)
|
|
84
|
+
|
|
85
|
+
_obj = cls.model_validate({
|
|
86
|
+
"name": obj.get("name"),
|
|
87
|
+
"asciiName": obj.get("asciiName"),
|
|
88
|
+
"geoNameId": obj.get("geoNameId")
|
|
89
|
+
})
|
|
90
|
+
return _obj
|
|
91
|
+
|
|
92
|
+
|
|
@@ -3,9 +3,9 @@
|
|
|
3
3
|
"""
|
|
4
4
|
Wink API
|
|
5
5
|
|
|
6
|
-
# Introduction Welcome to the Wink API - A programmer-friendly way to manage, sell and book travel inventory on the Wink platform. The API gives you all the tools you need to ready your properties and inventory for sale across 1000s of our native sales channels. Integrators, affiliates, travel agents and content creators have the ability search for your travel inventory 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 inventory and get that same inventory 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 inventory and either book it or use it to advertise through one of their Wink affiliate accounts. - [Configuration](/
|
|
6
|
+
# Introduction Welcome to the Wink API - A programmer-friendly way to manage, sell and book travel inventory on the Wink platform. The API gives you all the tools you need to ready your properties and inventory for sale across 1000s of our native sales channels. Integrators, affiliates, travel agents and content creators have the ability search for your travel inventory 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 inventory and get that same inventory 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 inventory and either book it or use it to advertise through one of their Wink affiliate accounts. - [Configuration](/customization-client): A single endpoint to retrieve whitelabel + customization information for the booking customization. - [Lookup](/lookup): All APIs related to locating inventory by region, locale and property flags. - [Inventory](/inventory): All APIs related to retrieve known travel inventory 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 inventory. #### 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 inventory 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 inventory to sell. - [Inventory](/affiliate/inventory): The Inventory API exposes endpoints for affiliates to manage the inventory 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 inventory and need taxonomies of standard and non-standard codes for inventory 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 inventory. 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.
|
|
8
|
+
The version of the OpenAPI document: 30.17.1
|
|
9
9
|
Contact: bjorn@wink.travel
|
|
10
10
|
Generated by OpenAPI Generator (https://openapi-generator.tech)
|
|
11
11
|
|
|
@@ -3,9 +3,9 @@
|
|
|
3
3
|
"""
|
|
4
4
|
Wink API
|
|
5
5
|
|
|
6
|
-
# Introduction Welcome to the Wink API - A programmer-friendly way to manage, sell and book travel inventory on the Wink platform. The API gives you all the tools you need to ready your properties and inventory for sale across 1000s of our native sales channels. Integrators, affiliates, travel agents and content creators have the ability search for your travel inventory 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 inventory and get that same inventory 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 inventory and either book it or use it to advertise through one of their Wink affiliate accounts. - [Configuration](/
|
|
6
|
+
# Introduction Welcome to the Wink API - A programmer-friendly way to manage, sell and book travel inventory on the Wink platform. The API gives you all the tools you need to ready your properties and inventory for sale across 1000s of our native sales channels. Integrators, affiliates, travel agents and content creators have the ability search for your travel inventory 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 inventory and get that same inventory 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 inventory and either book it or use it to advertise through one of their Wink affiliate accounts. - [Configuration](/customization-client): A single endpoint to retrieve whitelabel + customization information for the booking customization. - [Lookup](/lookup): All APIs related to locating inventory by region, locale and property flags. - [Inventory](/inventory): All APIs related to retrieve known travel inventory 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 inventory. #### 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 inventory 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 inventory to sell. - [Inventory](/affiliate/inventory): The Inventory API exposes endpoints for affiliates to manage the inventory 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 inventory and need taxonomies of standard and non-standard codes for inventory 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 inventory. 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.
|
|
8
|
+
The version of the OpenAPI document: 30.17.1
|
|
9
9
|
Contact: bjorn@wink.travel
|
|
10
10
|
Generated by OpenAPI Generator (https://openapi-generator.tech)
|
|
11
11
|
|
|
@@ -25,7 +25,7 @@ from typing_extensions import Self
|
|
|
25
25
|
|
|
26
26
|
class TravelAgentAgent(BaseModel):
|
|
27
27
|
"""
|
|
28
|
-
|
|
28
|
+
TravelAgentAgent
|
|
29
29
|
""" # noqa: E501
|
|
30
30
|
self_acquires: StrictBool = Field(description="Whether the agent is in charge of charging the property.", alias="selfAcquires")
|
|
31
31
|
self_disburses: StrictBool = Field(description="Whether the agent is in charge of paying the property.", alias="selfDisburses")
|
|
@@ -3,9 +3,9 @@
|
|
|
3
3
|
"""
|
|
4
4
|
Wink API
|
|
5
5
|
|
|
6
|
-
# Introduction Welcome to the Wink API - A programmer-friendly way to manage, sell and book travel inventory on the Wink platform. The API gives you all the tools you need to ready your properties and inventory for sale across 1000s of our native sales channels. Integrators, affiliates, travel agents and content creators have the ability search for your travel inventory 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 inventory and get that same inventory 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 inventory and either book it or use it to advertise through one of their Wink affiliate accounts. - [Configuration](/
|
|
6
|
+
# Introduction Welcome to the Wink API - A programmer-friendly way to manage, sell and book travel inventory on the Wink platform. The API gives you all the tools you need to ready your properties and inventory for sale across 1000s of our native sales channels. Integrators, affiliates, travel agents and content creators have the ability search for your travel inventory 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 inventory and get that same inventory 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 inventory and either book it or use it to advertise through one of their Wink affiliate accounts. - [Configuration](/customization-client): A single endpoint to retrieve whitelabel + customization information for the booking customization. - [Lookup](/lookup): All APIs related to locating inventory by region, locale and property flags. - [Inventory](/inventory): All APIs related to retrieve known travel inventory 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 inventory. #### 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 inventory 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 inventory to sell. - [Inventory](/affiliate/inventory): The Inventory API exposes endpoints for affiliates to manage the inventory 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 inventory and need taxonomies of standard and non-standard codes for inventory 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 inventory. 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.
|
|
8
|
+
The version of the OpenAPI document: 30.17.1
|
|
9
9
|
Contact: bjorn@wink.travel
|
|
10
10
|
Generated by OpenAPI Generator (https://openapi-generator.tech)
|
|
11
11
|
|
|
@@ -29,10 +29,10 @@ class TravelInventoryRecognitionAgent(BaseModel):
|
|
|
29
29
|
"""
|
|
30
30
|
Recognition for the ancillary blocking.
|
|
31
31
|
""" # noqa: E501
|
|
32
|
-
identifier:
|
|
32
|
+
identifier: Annotated[str, Field(min_length=1, strict=True)] = Field(description="Recognition identifier.")
|
|
33
33
|
category: StrictStr = Field(description="Recognition category.")
|
|
34
34
|
type: StrictStr = Field(description="Type of rating system the recognition operated on. This allows us to display the score properly.")
|
|
35
|
-
provider:
|
|
35
|
+
provider: Annotated[str, Field(min_length=1, strict=True)] = Field(description="The name of the entity that administers this recognition.")
|
|
36
36
|
rating: Union[Annotated[float, Field(strict=True, ge=0.0)], Annotated[int, Field(strict=True, ge=0)]] = Field(description="The actual award or rating received by the hotel facility.")
|
|
37
37
|
max_rating: Union[StrictFloat, StrictInt] = Field(description="Use this to let hotels indicate what the total score for this award is.", alias="maxRating")
|
|
38
38
|
var_date: Optional[date] = Field(default=None, description="The date the award was received", alias="date")
|
|
@@ -3,9 +3,9 @@
|
|
|
3
3
|
"""
|
|
4
4
|
Wink API
|
|
5
5
|
|
|
6
|
-
# Introduction Welcome to the Wink API - A programmer-friendly way to manage, sell and book travel inventory on the Wink platform. The API gives you all the tools you need to ready your properties and inventory for sale across 1000s of our native sales channels. Integrators, affiliates, travel agents and content creators have the ability search for your travel inventory 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 inventory and get that same inventory 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 inventory and either book it or use it to advertise through one of their Wink affiliate accounts. - [Configuration](/
|
|
6
|
+
# Introduction Welcome to the Wink API - A programmer-friendly way to manage, sell and book travel inventory on the Wink platform. The API gives you all the tools you need to ready your properties and inventory for sale across 1000s of our native sales channels. Integrators, affiliates, travel agents and content creators have the ability search for your travel inventory 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 inventory and get that same inventory 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 inventory and either book it or use it to advertise through one of their Wink affiliate accounts. - [Configuration](/customization-client): A single endpoint to retrieve whitelabel + customization information for the booking customization. - [Lookup](/lookup): All APIs related to locating inventory by region, locale and property flags. - [Inventory](/inventory): All APIs related to retrieve known travel inventory 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 inventory. #### 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 inventory 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 inventory to sell. - [Inventory](/affiliate/inventory): The Inventory API exposes endpoints for affiliates to manage the inventory 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 inventory and need taxonomies of standard and non-standard codes for inventory 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 inventory. 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.
|
|
8
|
+
The version of the OpenAPI document: 30.17.1
|
|
9
9
|
Contact: bjorn@wink.travel
|
|
10
10
|
Generated by OpenAPI Generator (https://openapi-generator.tech)
|
|
11
11
|
|
wink_sdk_travel_agent/rest.py
CHANGED
|
@@ -3,9 +3,9 @@
|
|
|
3
3
|
"""
|
|
4
4
|
Wink API
|
|
5
5
|
|
|
6
|
-
# Introduction Welcome to the Wink API - A programmer-friendly way to manage, sell and book travel inventory on the Wink platform. The API gives you all the tools you need to ready your properties and inventory for sale across 1000s of our native sales channels. Integrators, affiliates, travel agents and content creators have the ability search for your travel inventory 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 inventory and get that same inventory 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 inventory and either book it or use it to advertise through one of their Wink affiliate accounts. - [Configuration](/
|
|
6
|
+
# Introduction Welcome to the Wink API - A programmer-friendly way to manage, sell and book travel inventory on the Wink platform. The API gives you all the tools you need to ready your properties and inventory for sale across 1000s of our native sales channels. Integrators, affiliates, travel agents and content creators have the ability search for your travel inventory 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 inventory and get that same inventory 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 inventory and either book it or use it to advertise through one of their Wink affiliate accounts. - [Configuration](/customization-client): A single endpoint to retrieve whitelabel + customization information for the booking customization. - [Lookup](/lookup): All APIs related to locating inventory by region, locale and property flags. - [Inventory](/inventory): All APIs related to retrieve known travel inventory 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 inventory. #### 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 inventory 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 inventory to sell. - [Inventory](/affiliate/inventory): The Inventory API exposes endpoints for affiliates to manage the inventory 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 inventory and need taxonomies of standard and non-standard codes for inventory 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 inventory. 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.
|
|
8
|
+
The version of the OpenAPI document: 30.17.1
|
|
9
9
|
Contact: bjorn@wink.travel
|
|
10
10
|
Generated by OpenAPI Generator (https://openapi-generator.tech)
|
|
11
11
|
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.4
|
|
2
2
|
Name: wink_sdk_travel_agent
|
|
3
|
-
Version: 0.0.
|
|
3
|
+
Version: 0.0.26
|
|
4
4
|
Summary: Wink API
|
|
5
5
|
Home-page: https://github.com/wink-travel/wink-sdk-python.git
|
|
6
6
|
Author: Bjorn Harvold
|
|
@@ -249,7 +249,7 @@ Dynamic: license-file
|
|
|
249
249
|
### Consume APIs
|
|
250
250
|
Consume endpoints are for developers who want to find existing travel inventory and either book it or use it to advertise through one of their Wink affiliate accounts.
|
|
251
251
|
|
|
252
|
-
- [Configuration](/
|
|
252
|
+
- [Configuration](/customization-client): A single endpoint to retrieve whitelabel + customization information for the booking customization.
|
|
253
253
|
- [Lookup](/lookup): All APIs related to locating inventory by region, locale and property flags.
|
|
254
254
|
- [Inventory](/inventory): All APIs related to retrieve known travel inventory as it was found using the Lookup API..
|
|
255
255
|
- [Booking](/booking): All APIs related to creating bookings on the platform.
|
|
@@ -320,8 +320,8 @@ Browse the endpoints in the left navigation bar to get started.
|
|
|
320
320
|
|
|
321
321
|
This Python package is automatically generated by the [OpenAPI Generator](https://openapi-generator.tech) project:
|
|
322
322
|
|
|
323
|
-
- API version: 30.
|
|
324
|
-
- Package version: 0.0.
|
|
323
|
+
- API version: 30.17.1
|
|
324
|
+
- Package version: 0.0.26
|
|
325
325
|
- Generator version: 7.12.0
|
|
326
326
|
- Build package: org.openapitools.codegen.languages.PythonClientCodegen
|
|
327
327
|
|
|
@@ -339,9 +339,9 @@ pip install wink_sdk_travel_agent
|
|
|
339
339
|
|
|
340
340
|
Or you can install it directly from the repository using:
|
|
341
341
|
```sh
|
|
342
|
-
pip install git+https://github.com/wink-travel/wink-sdk-python.git@v0.0.
|
|
342
|
+
pip install git+https://github.com/wink-travel/wink-sdk-python.git@v0.0.26#egg=wink_sdk_travel_agent&subdirectory=wink-sdk-travel-agent
|
|
343
343
|
```
|
|
344
|
-
(you may need to run `pip` with root permission: `sudo pip install git+https://github.com/wink-travel/wink-sdk-python.git@v0.0.
|
|
344
|
+
(you may need to run `pip` with root permission: `sudo pip install git+https://github.com/wink-travel/wink-sdk-python.git@v0.0.26#egg=wink_sdk_travel_agent&subdirectory=wink_sdk_travel_agent`)
|
|
345
345
|
|
|
346
346
|
Then import the package:
|
|
347
347
|
```python
|
|
@@ -426,9 +426,10 @@ Class | Method | HTTP request | Description
|
|
|
426
426
|
## Documentation For Models
|
|
427
427
|
|
|
428
428
|
- [AddressAgent](docs/AddressAgent.md)
|
|
429
|
+
- [AffiliateAccountAgent](docs/AffiliateAccountAgent.md)
|
|
430
|
+
- [AffiliateAccountUserAgent](docs/AffiliateAccountUserAgent.md)
|
|
429
431
|
- [AgentBookingRequestAgent](docs/AgentBookingRequestAgent.md)
|
|
430
432
|
- [AggregateDescriptorAgent](docs/AggregateDescriptorAgent.md)
|
|
431
|
-
- [AncillaryRequestAgent](docs/AncillaryRequestAgent.md)
|
|
432
433
|
- [AuthenticatedUserAgent](docs/AuthenticatedUserAgent.md)
|
|
433
434
|
- [BedAgent](docs/BedAgent.md)
|
|
434
435
|
- [BedroomAgent](docs/BedroomAgent.md)
|
|
@@ -447,64 +448,52 @@ Class | Method | HTTP request | Description
|
|
|
447
448
|
- [BookingUserAgent](docs/BookingUserAgent.md)
|
|
448
449
|
- [BookingUserRequestAgent](docs/BookingUserRequestAgent.md)
|
|
449
450
|
- [BookingUserSessionAgent](docs/BookingUserSessionAgent.md)
|
|
450
|
-
- [BookingViewAgent](docs/BookingViewAgent.md)
|
|
451
451
|
- [BooleanResponseAgent](docs/BooleanResponseAgent.md)
|
|
452
452
|
- [CancellationDetailAgent](docs/CancellationDetailAgent.md)
|
|
453
|
-
- [CancellationPolicyAgent](docs/CancellationPolicyAgent.md)
|
|
454
453
|
- [CancellationPolicyExceptionAgent](docs/CancellationPolicyExceptionAgent.md)
|
|
455
454
|
- [CancellationPolicyExceptionsAgent](docs/CancellationPolicyExceptionsAgent.md)
|
|
455
|
+
- [CancellationPolicyLightweightAgent](docs/CancellationPolicyLightweightAgent.md)
|
|
456
456
|
- [ChildAgent](docs/ChildAgent.md)
|
|
457
457
|
- [CommissionableEntryAgent](docs/CommissionableEntryAgent.md)
|
|
458
|
-
- [CompanyAgent](docs/CompanyAgent.md)
|
|
459
|
-
- [CompanyUserAgent](docs/CompanyUserAgent.md)
|
|
460
|
-
- [CompanyViewAgent](docs/CompanyViewAgent.md)
|
|
461
458
|
- [CompositeFilterDescriptorAgent](docs/CompositeFilterDescriptorAgent.md)
|
|
462
459
|
- [ContactAgent](docs/ContactAgent.md)
|
|
463
|
-
- [
|
|
460
|
+
- [CountryLightweightAgent](docs/CountryLightweightAgent.md)
|
|
464
461
|
- [CreateAgentBooking400Response](docs/CreateAgentBooking400Response.md)
|
|
465
462
|
- [CreateAgentBookingRequestAgent](docs/CreateAgentBookingRequestAgent.md)
|
|
466
463
|
- [CustomMonetaryAmount](docs/CustomMonetaryAmount.md)
|
|
467
|
-
- [
|
|
468
|
-
- [
|
|
469
|
-
- [EngineConfigurationThemeColorsAgent](docs/EngineConfigurationThemeColorsAgent.md)
|
|
464
|
+
- [CustomizationLightweightAgent](docs/CustomizationLightweightAgent.md)
|
|
465
|
+
- [CustomizationThemeColorsAgent](docs/CustomizationThemeColorsAgent.md)
|
|
470
466
|
- [ExtraChargeAgent](docs/ExtraChargeAgent.md)
|
|
471
467
|
- [ExtraChargesAgent](docs/ExtraChargesAgent.md)
|
|
472
|
-
- [FeeAgent](docs/FeeAgent.md)
|
|
473
468
|
- [FilterDescriptorAgent](docs/FilterDescriptorAgent.md)
|
|
474
469
|
- [GeneralManagerAgent](docs/GeneralManagerAgent.md)
|
|
475
470
|
- [GenericErrorMessage](docs/GenericErrorMessage.md)
|
|
476
471
|
- [GeoJsonPointAgent](docs/GeoJsonPointAgent.md)
|
|
477
|
-
- [
|
|
472
|
+
- [GeoNameLightweightAgent](docs/GeoNameLightweightAgent.md)
|
|
478
473
|
- [GroupDescriptorAgent](docs/GroupDescriptorAgent.md)
|
|
479
474
|
- [GuestRoomLightweightAgent](docs/GuestRoomLightweightAgent.md)
|
|
480
475
|
- [GuestUserAgent](docs/GuestUserAgent.md)
|
|
481
|
-
- [HotelOnMapAgent](docs/HotelOnMapAgent.md)
|
|
482
476
|
- [ImageAttributionAgent](docs/ImageAttributionAgent.md)
|
|
483
477
|
- [LocalizedDescriptionAgent](docs/LocalizedDescriptionAgent.md)
|
|
484
478
|
- [LocalizedPriceAgent](docs/LocalizedPriceAgent.md)
|
|
485
479
|
- [ManagedByEntityAgent](docs/ManagedByEntityAgent.md)
|
|
486
480
|
- [ManagedByEntityRulesAgent](docs/ManagedByEntityRulesAgent.md)
|
|
487
|
-
- [
|
|
488
|
-
- [PageBookingViewAgent](docs/PageBookingViewAgent.md)
|
|
481
|
+
- [PageBookingAgent](docs/PageBookingAgent.md)
|
|
489
482
|
- [PageableObjectAgent](docs/PageableObjectAgent.md)
|
|
490
483
|
- [PayoutAgent](docs/PayoutAgent.md)
|
|
491
484
|
- [PayoutFeeAgent](docs/PayoutFeeAgent.md)
|
|
492
|
-
- [PendingRefundAgent](docs/PendingRefundAgent.md)
|
|
493
485
|
- [PerkLightweightAgent](docs/PerkLightweightAgent.md)
|
|
494
486
|
- [PersonalAgent](docs/PersonalAgent.md)
|
|
495
|
-
- [PetInfoDtoAgent](docs/PetInfoDtoAgent.md)
|
|
496
487
|
- [PreferencesAgent](docs/PreferencesAgent.md)
|
|
497
|
-
- [
|
|
488
|
+
- [ProfileLightweightAgent](docs/ProfileLightweightAgent.md)
|
|
498
489
|
- [ProfileUserAgent](docs/ProfileUserAgent.md)
|
|
490
|
+
- [PropertyAggregateLightweightAgent](docs/PropertyAggregateLightweightAgent.md)
|
|
499
491
|
- [PropertyPolicyAgent](docs/PropertyPolicyAgent.md)
|
|
500
|
-
- [
|
|
492
|
+
- [QuoteLightweightAgent](docs/QuoteLightweightAgent.md)
|
|
501
493
|
- [RatePlanLevelFeeAgent](docs/RatePlanLevelFeeAgent.md)
|
|
502
494
|
- [RefundAgent](docs/RefundAgent.md)
|
|
503
|
-
- [ReportingAncillaryAgent](docs/ReportingAncillaryAgent.md)
|
|
504
|
-
- [ReportingDailyRateAgent](docs/ReportingDailyRateAgent.md)
|
|
505
|
-
- [ReportingExtraChargeAgent](docs/ReportingExtraChargeAgent.md)
|
|
506
|
-
- [ReviewAgent](docs/ReviewAgent.md)
|
|
507
495
|
- [ReviewAnswerAgent](docs/ReviewAnswerAgent.md)
|
|
496
|
+
- [ReviewLightweightAgent](docs/ReviewLightweightAgent.md)
|
|
508
497
|
- [ReviewUserAgent](docs/ReviewUserAgent.md)
|
|
509
498
|
- [RoomConfigurationAgent](docs/RoomConfigurationAgent.md)
|
|
510
499
|
- [RoomConfigurationPriceRatePlanAgent](docs/RoomConfigurationPriceRatePlanAgent.md)
|
|
@@ -518,8 +507,8 @@ Class | Method | HTTP request | Description
|
|
|
518
507
|
- [SortObjectAgent](docs/SortObjectAgent.md)
|
|
519
508
|
- [StateAgent](docs/StateAgent.md)
|
|
520
509
|
- [StayRateAgent](docs/StayRateAgent.md)
|
|
521
|
-
- [
|
|
522
|
-
- [
|
|
510
|
+
- [SubCountryLightweightAgent](docs/SubCountryLightweightAgent.md)
|
|
511
|
+
- [SubSubCountryLightweightAgent](docs/SubSubCountryLightweightAgent.md)
|
|
523
512
|
- [SupplierContractItemPolicyAgent](docs/SupplierContractItemPolicyAgent.md)
|
|
524
513
|
- [TravelAgentAgent](docs/TravelAgentAgent.md)
|
|
525
514
|
- [TravelInventoryRecognitionAgent](docs/TravelInventoryRecognitionAgent.md)
|