Deprecations are features of the API which you are discouraged from using, even though they may still be supported for a period of time for the sake of backwards compatibility. Such features are normally deprecated because they are superseded by a better alternative. They can include object properties, entire objects or entire API operations. The list of deprecations is as follows. Individual items are also highlighted in the Changelog when they occur. Historic deprecations that have already been discontinued may not be listed. For more information, see our Deprecations Policy.
Important: We strongly advise you to review this list and if you are using any of the deprecated items in your integration, to update your implementation accordingly. If the feature change requires re-certification, please contact Mews before making the change.
The table columns have the following meanings:
- Feature - What entity or feature is being deprecated
- Comments - Additional information, such as the reason for the deprecation and what the replacement is
- Deprecated - The date at which the deprecation notice was given (see the Changelog)
- Discontinued - The date at which it is planned to discontinue support completely; a value of '-' indicates no date has been set
| Feature | Comments | Deprecated | Discontinued |
|---|---|---|---|
| - | - | - | - |
| Feature | Comments | Deprecated | Discontinued |
|---|---|---|---|
loyaltyCode in Customer object in Mews: Process group |
Replaced by loyaltyInfo |
4 Nov 2024 | - |
releasedDate in CHM: Dates object in CHM: Availability block |
Replaced by fixedDate in Release strategy of Availability block |
11 Oct 2024 | - |
error in Synchronous error response |
Replaced by errors (plural and an array) |
15 May 2024 | - |
paymentType in RatePlan returned by Mews: Get configuration |
May yield incorrect value. More info below (*1). | 16 May 2024 | - |
channel in Process group |
Replaced by sources |
26 Sep 2022 | - |
iata in Company in Process group |
Replaced by iata in the Travel Agency object |
26 Sep 2022 | - |
adultCount and childCount in Reservation object in Process group |
Replaced by guestCounts; Requires re-certification |
29 Apr 2022 | - |
code in Payment card object in Process group |
Replaced by type |
08 Mar 2018 | End Apr 2018 |
accessToken in all API calls on both Mews side and CHM side |
Replaced by clientToken |
10 Jan 2018 | End Mar 2018 |
connectionCode in all API calls on both Mews side and CHM side |
Replaced by connectionToken |
10 Jan 2018 | End Mar 2018 |
code in Connection Info object in Get properties |
Replaced by token |
10 Jan 2018 | End Mar 2018 |
distributor in Reservation object in Process group |
Replaced by channel |
10 Jan 2018 | End Mar 2018 |
(*1) paymentType: We are introducing enhancements that elevate settlement rules to the enterprise level, allowing them to be assigned either to a rate group or directly to a rate. Due to the complex nature of settlement rules, which can vary within a rate group,
paymentTypeis now obsolete as the value may vary depending on reservation dates, which can't be reflected in this field.
| Feature | Comments | Deprecated | Discontinued |
|---|---|---|---|
| Error response codes 4 and 5 | Use codes 9 and 10 instead | 11 Aug 2022 | - |