# Changelog

### 2024

{% updates format="full" %}
{% update date="2024-12-02" tags="added,reservations" %}

## <sub>ResStatus Redacted</sub>

Reservations with a @ResStatus of “Redacted” will have all ‘PII’ data removed. The SMX partner application should be able to accept all ResStatus values and respond with Success (200 OK status). It will now need to handle the additional ‘Redacted’ value.

{% code overflow="wrap" expandable="true" %}

```xml
<HotelReservations>
	<HotelReservation ResStatus="Redacted" CreateDateTime="2017-09-19T18:02:44+00:00" CreatorID="LINDA-RESAGENT" LastModifyDateTime="2017-09-19T18:13:51+00:00" LastModifierID="651651651651">
		<POS>…</POS>
		<UniqueID ID="BDC-3685569477"/>
		<RoomStays>…</RoomStays>
		<ResGlobalInfo>…</ResGlobalInfo>
	</HotelReservation>
</HotelReservations>
```

{% endcode %}
{% endupdate %}

{% update date="2024-02-08" tags="added,reservations" %}

## <sub>Second AddressLine</sub>

Reservations may include a second AddressLine under ResGuest / Profile and ResGlobalInfo / Profile rather than having the two address lines merged in one AddressLine. LittleHotelier supports two-line addresses and have character limits for each. If there is data in the second line, it will be sent in the XML in a secondary AddressLine as below:

{% code overflow="wrap" expandable="true" %}

```xml
<HotelReservations>
	<HotelReservation ResStatus="Redacted" CreateDateTime="2017-09-19T18:02:44+00:00" CreatorID="LINDA-RESAGENT" LastModifyDateTime="2017-09-19T18:13:51+00:00" LastModifierID="651651651651">
		<POS>…</POS>
		<UniqueID ID="BDC-3685569477"/>
		<RoomStays>…</RoomStays>
		<ResGlobalInfo>…</ResGlobalInfo>
	</HotelReservation>
</HotelReservations>
```

{% endcode %}
{% endupdate %}

{% update date="2024-01-09" tags="added,reservations" %}

## <sub>ResGlobalInfo and ResGuests</sub>

Little Hotelier reservations will contain a Guest ID under Profiles / UniqueID / ID. This is a randomly generated ID and will not be visible in Little Hotelier.

{% code overflow="wrap" expandable="true" %}

```xml
<ResGuests>
    <ResGuest ResGuestRPH="2">
        <Profiles>
            <ProfileInfo>
                <UniqueID ID="1139" Type="1"/>
                <Profile ProfileType="1">
                
<ResGlobalInfo>
    <Profiles>
        <ProfileInfo>
            <UniqueID ID="1140" Type="1"/>
            <Profile ProfileType="1">
                <Customer VIP_Indicator="false">
                    <PersonName>
                        <GivenName>*****</GivenName>
                        <Surname>*****</Surname>
                    </PersonName>
                    <Address Type="1">
                        <AddressLine>*****</AddressLine>
                        <CityName>*****</CityName>
                        <StateProv>*****</StateProv>
                    </Address>
                </Customer>
            </Profile>
        </ProfileInfo>
    </Profiles>
</ResGlobalInfo>               
```

{% endcode %}
{% endupdate %}

{% update date="2024-01-09" tags="added,reservations" %}

## <sub>ResGuest / PrimaryIndicator</sub>

Little Hotelier reservations will now identify the primary guest as PrimaryIndicator=”true” to know which guest is checking in. If multiple ResGuest / Profile are sent, only one will be identified as primary.

{% code overflow="wrap" expandable="true" %}

```xml
<ResGuests>
	<ResGuest ResGuestRPH="1" PrimaryIndicator="true">
		<Profiles>
			<ProfileInfo>
				<Profile ProfileType="1">
                    ...
        </Profile>
			</ProfileInfo>
		</Profiles>
	</ResGuest>
</ResGuests>
```

{% endcode %}
{% endupdate %}
{% endupdates %}

### 2023

{% updates format="full" %}
{% update date="2023-01-06" tags="removed,ari" %}

## <sub>Remove Availability by Hotel</sub>

Other availability endpoints listed below will remain active:

* [Availability by Room Type Code](/smx-api/reference/availability-and-rates/availability.md#availability-by-room-type-code)
* [Availability by Rate Plan Code](/smx-api/reference/availability-and-rates/availability.md#availability-by-rate-plan-code)
  {% endupdate %}
  {% endupdates %}

### 2022

{% updates format="full" %}
{% update date="2022-11-16" tags="added,ari" %}

## <sub>Error Code 405</sub>

**Method Not Supported**

Previously when any publisher-to-hotel connection does not have ARI enabled, a 403 Forbidden error is returned. A more appropriate status code is introduced to handle this type of error.

<table><thead><tr><th width="85.25177001953125">Code</th><th width="204.6285400390625">Reason</th><th>Error Message</th></tr></thead><tbody><tr><td>405</td><td>Method Not Supported</td><td>[Method name] not supported by this publisher</td></tr></tbody></table>

This error code response is added to all ARI endpoints (listed below) besides the metadata endpoints:

* [RoomTypes](/smx-api/reference/availability-and-rates/roomtypes.md)
* [RatePlans](/smx-api/reference/availability-and-rates/rateplans.md)
* [Availability](/smx-api/reference/availability-and-rates/availability.md)
* [Rates](/smx-api/reference/availability-and-rates/rates.md)
  {% endupdate %}

{% update date="2022-02-09" tags="added,reservations" %}

## <sub>ResGlobalInfo / Total / Taxes</sub>

A collection of taxes relating to the total reservation cost.
{% endupdate %}

{% update date="2022-02-07" tags="removed,reservations" %}

## <sub>AcceptedPayment / DirectBill</sub>

Amount = A monetary amount taken for the deposit.\
NmbrOfNights = The number of nights of the hotel stay that are used to calculate the fee amount.
{% endupdate %}

{% update date="2022-02-04" tags="added,reservations" %}

## <sub>ServiceDetails / TimeSpan</sub>

HotelReservation / Services / Service / ServiceDetails / TimeSpan

The Time Span which covers the Service.The Time Span which covers the Service.&#x20;

Start = The starting value of the time span.\
End = The ending value of the time span.
{% endupdate %}

{% update date="2022-02-04" tags="removed,reservations" %}

## <sub>ServiceDetails / GuestCounts / TimeSpan</sub>

{% endupdate %}
{% endupdates %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://developer.siteminder.com/smx-api/additional-resources/changelog.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.