Deprecations
Last updated
Was this helpful?
Last updated
Was this helpful?
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 when they occur. Historic deprecations that have already been discontinued may not be listed. For more information, see our .
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 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 )
Discontinued - The date at which it is planned to discontinue support completely; a value of '-' indicates no date has been set
-
-
-
-
12 March 2025
-
Replaced by loyaltyInfo
4 Nov 2024
-
11 Oct 2024
-
Replaced by errors (plural and an array)
15 May 2024
-
May yield incorrect value. More info below (*1).
16 May 2024
-
Replaced by sources
26 Sep 2022
-
26 Sep 2022
-
Replaced by guestCounts; Requires re-certification
29 Apr 2022
-
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
Replaced by token
10 Jan 2018
End Mar 2018
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.
Use codes 9 and 10 instead
11 Aug 2022
-
grossAmount in object in
Replaced by prices collection of
loyaltyCode in object in
releasedDate in object in
Replaced by fixedDate in of
error in
paymentType in returned by
channel in
iata in in
Replaced by iata in the object
adultCount and childCount in object in
code in object in
code in object in
distributor in object in
4 and 5