Sample of SubmitCruiseTransaction without Correlation Token
This sample request of SubmitCruiseTransaction takes the following:
Note:
Request
The following request sailing, rate code, and category availabilities for a cruise. No correlation token is required and the filter is empty, meaning that the full response is being requested.
Explanation |
Code |
Identifies the namespace for the submit cruise transaction. |
<SubmitCruiseTransaction xmlns="http://webservices.galileo.com"> |
Identifies the host access profile being used. |
|
This request does not require a correlation token; therefore, it is empty. |
|
Begins the transaction request. |
|
Begins the request. Follows the format for MultiSubmitXml. |
|
Indicates which cruise transaction is being used. In this case, cruise availability is being used. The information in the request is based on the requirements within the individual cruise transaction. The information in this section changes depending on the transaction used. |
|
This filter is applied to the response. In this case, the filter is empty and the entire response is returned. |
|
Ends the request. |
</SubmitCruiseTransaction> |
Response
The following response returns the cruise availability results. No correlation token is returned in this response.
<SubmitCruiseTransactionResponse xmlns="http://webservices.galileo.com">
</SubmitCruiseTransactionResponse>