Deprecations

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 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.

The table columns have the following meanings:

  • Object - JSON data object containing the deprecated field or property

  • Property - Field or property which is deprecated

  • Replaced by - What the replacement is, if applicable

  • Context - The context in which the property is used, usually the API operation

  • 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

Deprecated object properties

Object
Property
Replaced by
Context
Deprecated
Discontinued

AdultCount, ChildCount

18 Mar 2024

-

Request object

AdultCount, ChildCount

18 Mar 2024

-

AdultCount, ChildCount

18 Mar 2024

-

AdultCount, ChildCount

18 Mar 2024

-

TaxValues

19 Oct 2022

-

ImageIds

21 Oct 2021

-

AverageAmountPerNight

AverageAmountPerTimeUnit

21 Jul 2021

-

SettlementMaximumNights

SettlementMaximumTimeUnits

21 Jul 2021

-

Charging

ChargingMode

21 Jul 2021

-

Posting

PostingMode

21 Jul 2021

-

Amounts, RelativePrice

Pricing

01 Jul 2021

-

PaymentCardInput

PaymentCardRequirement

18 Apr 2021

-

Last updated