# Response message
The following sections describe in detail the message structure returned from the HCD XML Update Interface.
The payload for transactions returned by ENTERPRISE CONNECTIVITY will follow the schema defined for the OTA\_HotelDescriptiveContentNotifRS message.
| **Element** | **Level** | **Attribute** |
| PrimaryLangID | R | EN | Refer to the Appendix B for valid codes | Mimic the ID found in the inbound XML message. |
| Success | 1 |
| C |
|
|
Either a Success or a Success with Warnings can be present in the response.
If a Success Element is present, the property message was successfully submitted into HCD.
|
| Warnings | 1 |
| C |
|
|
|
| Warning | 2 |
| C |
|
| Will be present if an Warnings element is present |
|
|
| Type | R | 3 | Refer to the Appendix for valid codes |
Due to limited warning types, this code can be a
ENTERPRISE CONNECTIVITY generated code.
|
|
|
| ShortText | R | Invalid Property would result from update. | 64 Char |
A short description of the error
Required for Warning element.
|
|
|
| Code | O | 3 | Refer to the Appendix for valid codes |
Due to limited warning types, this code can be a
ENTERPRISE CONNECTIVITY generated code.
|
| Errors | 1 |
| C |
|
| Either a Success or an Errors element will be present in the response |
| Error | 2 |
| C |
|
| Will be present if an Errors element is present |
|
|
| Type | R | 3 | Refer to the Appendix for valid codes |
Due to limited warning types, this code can be a
ENTERPRISE CONNECTIVITY generated code.
|
|
|
| ShortText | R | Invalid Property would result from update. | 64 Char |
A short description of the error
Required for Error element.
|
|
|
| Code | O | 3 | Refer to the Appendix for valid codes |
Due to limited error types, this code can be a
ENTERPRISE CONNECTIVITY generated code.
|
| UniqueID | 1 |
| R |
|
|
|
|
|
| ID | R | RecordID00 1 | 32 Char | Mimic the MessageID within the inbound XML message. The ID will be appended with a sequence number. |
|
|
| Type | R | 1 | Always displays as 1. |
Unique ID Type (UIT)
Required for UniqueID element.
|
**Schema design view**
**Example transaction**
**The following is a standard Success response.**
```xml
```
**The following is a standard Error response.**
```xml
ERROR:Line=1:cvc-pattern-valid: Value
'4000000' is not facet-valid with respect to pattern '[0-9A-Z]{1,3}(\.[A-Z]{3}(\.X){0,1}){0,1}' for type
'OTA_CodeType'.ERROR:Line=1:cvc-attribute.3: The value '4000000' of attribute 'Code' on element 'LocationCategory' is not valid with respect to its type, 'OTA_CodeType'.
```
---
# 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/response-message.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.