# Contact information Although OpenTravel allows unlimited occurrences of each element within the OTA\_HotelDescriptiveContentNotifRQ message, ENTERPRISE CONNECTIVITY has elected to set limits for many of these elements. Unless specified under the Usage column below, ENTERPRISE CONNECTIVITY only allows one instance of each element per property message. | **Element** | **Level** | **Attribute** |

R

O

C

|

G

D

S

| **Example** | **Usage** | **Description** | | ------------ | --------- | ------------- | --------------------------------------------------------------------------- | --------------------------------------------------------------------------- | ----------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------- | | ContactInfos | 3 |


| C |


|


|


|

Element required when action code is Add or Overwrite = true


Only 1 element allowed per Property message.

| | ContactInfo | 4 |


| R |


|


|


|

Required when

ContactInfos element is present.


Only 1 element allowed per Property message.

| | **Element** | **Level** | **Attribute** |

R

O

C

|

G

D

S

| **Example** | **Usage** | **Description** | | ----------- | ----------- | ------------- | --------------------------------------------------------------------------- | --------------------------------------------------------------------------- | --------------------------------------------- | -------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | |


|


| Removal | O |


|


| true false | If not specified, false is assumed. | | Addresses | 5 |


| C |


|


|


|

Only Required when action code is add, Overwrite = true or when adding additional language.


Only 1 element allowed per Property message.

| | Address | 6 |


| R |


|


|


| Required when Addresses element is present. | |


|


| UseType | R | R |


|

Refer to the

“HCD OTA

Supported Codes” spreadsheet for valid codes

|

Address Use Type (AUT).


Required for Address element.


GDS Note: Address Use Type of 5 (Other) will default all address elements/attributes to the usage limitations for the GDSs.

| |


|


| Removal | O |


|


| true false | If not specified, false is assumed. | | AddressLine | 7 |


| C | R |

1530

N. Central

Expressway

|

255 Char


GDS Max: 50

Char

|

Hotel property address.


5 text line are available for the complete address of the property.


Only Required when action code is add, Overwrite = true or when adding additional language.


AddressLine is a multi- lingual attribute.


GDS Note: Only the first 2 lines of address will be delivered to the GDSs.

| | CityName | 7 |


| C | R | Dallas |

64 Char


Max: 128 bytes


GDS Max: 50

Char

|

Hotel property city


Only Required when action code is add, Overwrite = true or when adding additional language.


CityName is a multi-lingual attribute.

| | PostalCode | 7 |


| O | R | 75305 |

16 Char


GDS Max: 10

Char

| Hotel property postal code | | County | 7 |


| O | O | Dallas |

32 Char


Max: 64 bytes

|

Hotel property county


County is a multi-lingual

|
| **Element** | **Level** | **Attribute** |

R

O

C

|

G

D

S

| **Example** | **Usage** | **Description** | | ----------- | ----------- | ------------------ | --------------------------------------------------------------------------- | --------------------------------------------------------------------------- | ----------- | ------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | |


|


|


|


|


|


|


GDS Max: 30

Char

| attribute. | | StateProv | 7 |


| C |


|


|


| Only 1 element allowed per Address. | |


|


| StateCode | C | C | TX | Refer to the Appendix for valid codes |

Hotel property state/province code.


If the Hotel Property

Country is either “AU”,

“BR”, “CA”, “DE”, “MX”, or “US” , the state/province code is validated, otherwise it is not.

GDS Note: Attribute is required for the above countries when delivering data to the GDSs.

| | CountryName | 7 |


| C |


|


|


|

Only Required when action code is add or Overwrite = true


Only 1 element allowed per Address.

| |


|


| Code | R | R | US | Refer to the Appendix for valid codes |

Hotel property country code.


Required for CountryName element.

| | Phones | 5 |


| C |


|


|


|

Only Required when action code is add or Overwrite = true


Only 1 element allowed per Property message.

| | Phone | 6 |


| R |


|


|


| Required when Phones Element is present. | |


|


| PhoneLocationT ype | R | O |


|

Refer to the

“HCD OTA

Supported Codes” spreadsheet for valid codes

|

Phone Location Type (PLT).


Required for Phone element.


At least one phone number with PhoneLocationType = 4 and PhoneTechType = 1 must be present per property.


Phone Location Type of 8 (Other) will default all phone elements/attributes to the usage limitations for the GDSs.

| |


|


| PhoneTechType | R | R |


|

Refer to “HCD

OTA Supported Codes” spreadsheet for valid codes.

|

Phone Tech Type (PTT).


Only codes of 1, 3, 6, or 7 will be accepted. All other

|
| **Element** | **Level** | **Attribute** |

R

O

C

|

G

D

S

| **Example** | **Usage** | **Description** | | ----------- | ----------- | ------------------ | --------------------------------------------------------------------------- | --------------------------------------------------------------------------- | ---------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | |


|


|


|


|


|


| Only codes 1, 3, 6, and 7 will be accepted in this context. |

codes will generate an error.


Required for Phone element.

| |


|


| CountryAccessC ode | C | R | 011 | 3 Char |

The countries direct dial prefix


Attribute required when PhoneLocationType = 4.


CountryAccessCode value must match Property’s Country Code. See appendix for codes.


If not populated when required or value is not valid an error is generated.


GDS Note: HCD can collect more than 1 code per country. Defaults will be applied when sent to the GDSs. See appendix for codes.

| |


|


| AreaCityCode | O | O | 972 | 8 Char | Hotel property area code | |


|


| PhoneNumber | C | R | 555-1212 |

32 Char


GDS Max: 30

Char

|

Hotel property number


Only Required when action code is add or Overwrite = true.

| | Emails | 5 |


| O |


|


|


| Only 1 element allowed per Property message. | | Email | 6 |


| R | O | joebob\@my [hotel.com](http://hotel.com) | 128 Char |

Hotel property Internet e- mail ID.


Only one ID per EmailType is allowed. More than one will generate an error.


Attribute required when

Emails

| |


|


| EmailType | R | O | 5 |

Refer to “HCD

OTA Supported Codes” spreadsheet for valid codes. Only codes of 5 & 7 will be accepted in this context.

|

Email Address Type (EAT).


Only codes of 5 and 7 will be accepted. All others codes will generate an error.


Required for Email Element.

| |


|


| Removal | O |


|


| true false | If not specified, false is assumed. | | URLs | 5 |


| O |


|


|


|


| | **Element** | **Level** | **Attribute** |

R

O

C

|

G

D

S

| **Example** | **Usage** | **Description** | | URL | 6 |


| R |


|


| 128 Char |

Hotel website URL.


Only one Element per ContactInfo allowed. If more than one element is present, an error will be returned.

| **Schema design view**
**Example transaction** ```xml
123 Hotel Street Dallas 75777 Dallas
www.testhotel.com ``` --- # 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.rategain.com/content/content-update-1/transaction-specifications/contact-information.md?ask= ``` 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.