Package travel.wink.hotelbeds.booking.sdk.api

Class BookingApi

java.lang.Object
travel.wink.hotelbeds.booking.sdk.api.BookingApi
@Generated(value="org.openapitools.codegen.languages.JavaClientCodegen", date="2023-10-04T11:28:08.331690043+07:00[Asia/Bangkok]") public class BookingApi extends Object

  • Constructor Details

    • BookingApi

      public BookingApi()

    • BookingApi

      @Autowired public BookingApi(ApiClient apiClient)

  • Method Details

    • getApiClient

      public ApiClient getApiClient()

    • setApiClient

      public void setApiClient(ApiClient apiClient)

    • booking

      public reactor.core.publisher.Mono<BookingRS> booking(String accept, String acceptEncoding, String contentType, BookingRQ body) throws org.springframework.web.reactive.function.client.WebClientResponseException
      Booking confirmation The Booking operation requests a reservation confirmation for the specified ratekey or ratekeys. BookingAPI does not support on-request confirmations. All confirmations are instant confirmations. Timeout for this operation is 60 seconds.

      200 - When the confirmation of a rateKey is successful; the booking reference is provided, along with key information of the booking, which includes: * Hotel confirmed * Holder and pax confirmed * Rate confirmed with the confirmed amounts and dates The response also contains the price breakdown, cancellation policies, supplements, and discounts. Please make sure to **keep the booking reference** of all bookings performed with your credentials, as they are needed for post booking operations such as modification or cancellation.

      400 - **BAD REQUEST** - The server cannot or will not process the request due to an apparent client error. *INVALID_REQUEST* - The request is not compliant with the specified version of the API. The message body will contain more information *INVALID_DATA* - The JSON or XML syntax is correct, however some of the fields contain incorrect data. Please check the documentation for the allowed values and follow the message returned in order to fix this error. *ALLOTMENT EXCEEDED*

      401 - **UNAUTHORIZED** - Authentication has failed or has not been provided. * Authorization field missing * Request signature verification failed

      402 - **PAYMENT** * The parameters were valid but the request failed.

      403 - **FORBIDDEN** - The credentials are correct and authorization was succesful, but access to this resource/operation is not allowed.

      406 - **NOT ACCEPTABLE** - The resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request.

      410 - error repeated

      415 - **UNSUPPORTED MEDIA TYPE** - Use the Content-Type header to set application/json and be sure the format of your payload matches the format

      429 - **Rate limit exceeded** - The user has sent too many requests in a given amount of time.

      500 - **INTERNAL SERVER ERROR** - An unexpected condition was encountered. Possible causes *SYSTEM_ERROR* - These are internal server errors, please send us these errors together with the complete logs (JSON or XML requests and responses) at [apitude@hotelbeds.com]() so that our team can review them. *PRODUCT_ERROR* - This type of error is produced due to product restrictions or due to other account set-up limitations. In all cases, the end result is that the booking cannot be confirmed. Here is a list of common product errors: * *Insufficient allotment*: This means that the user is trying to book a room which is no longer available. This may happen if the room was still available in the Availability stage but someone else has made a reservation for this room or rooms. * *Price has increased*: The price increase between booking steps has exceeded the allowed tolerance that was set. This is a setting to protect clients from booking a room with a higher price than expected. * *Contract is closed/Office or branch not active/Cannot find channel quotation*: There are problems related to the contract. * *Stop sales*: This means that the hotel is forbidding sales on the requested dates. * *Booking confirmation error XXX-YYYYYY*: A confirmation error occurred. Please try again later. * *Release violated* * *There's a stop sales for the date/s* *CONFIGURATION_ERROR* - This type of error is produced by configuration restrictions set-up at account level. Usually this results in the inability to perform an specific operation. Here is a list of common configuration errors: * *This apikey is not associated with a valid client*: This means that the provided apiKey belongs to an inactive client/agency. If you need information regarding the cause for this please contact our support team at [apitude@hotelbeds.com]().

      Parameters:
      accept - Response format.
      acceptEncoding - Defines type of encoding used on the data.
      contentType - Defines request format.
      body - Definition and examples of request body of Booking operation
      Returns:
      BookingRS
      Throws:
      org.springframework.web.reactive.function.client.WebClientResponseException - if an error occurs while attempting to invoke the API

    • bookingWithHttpInfo

      public reactor.core.publisher.Mono<org.springframework.http.ResponseEntity<BookingRS>> bookingWithHttpInfo(String accept, String acceptEncoding, String contentType, BookingRQ body) throws org.springframework.web.reactive.function.client.WebClientResponseException
      Booking confirmation The Booking operation requests a reservation confirmation for the specified ratekey or ratekeys. BookingAPI does not support on-request confirmations. All confirmations are instant confirmations. Timeout for this operation is 60 seconds.

      200 - When the confirmation of a rateKey is successful; the booking reference is provided, along with key information of the booking, which includes: * Hotel confirmed * Holder and pax confirmed * Rate confirmed with the confirmed amounts and dates The response also contains the price breakdown, cancellation policies, supplements, and discounts. Please make sure to **keep the booking reference** of all bookings performed with your credentials, as they are needed for post booking operations such as modification or cancellation.

      400 - **BAD REQUEST** - The server cannot or will not process the request due to an apparent client error. *INVALID_REQUEST* - The request is not compliant with the specified version of the API. The message body will contain more information *INVALID_DATA* - The JSON or XML syntax is correct, however some of the fields contain incorrect data. Please check the documentation for the allowed values and follow the message returned in order to fix this error. *ALLOTMENT EXCEEDED*

      401 - **UNAUTHORIZED** - Authentication has failed or has not been provided. * Authorization field missing * Request signature verification failed

      402 - **PAYMENT** * The parameters were valid but the request failed.

      403 - **FORBIDDEN** - The credentials are correct and authorization was succesful, but access to this resource/operation is not allowed.

      406 - **NOT ACCEPTABLE** - The resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request.

      410 - error repeated

      415 - **UNSUPPORTED MEDIA TYPE** - Use the Content-Type header to set application/json and be sure the format of your payload matches the format

      429 - **Rate limit exceeded** - The user has sent too many requests in a given amount of time.

      500 - **INTERNAL SERVER ERROR** - An unexpected condition was encountered. Possible causes *SYSTEM_ERROR* - These are internal server errors, please send us these errors together with the complete logs (JSON or XML requests and responses) at [apitude@hotelbeds.com]() so that our team can review them. *PRODUCT_ERROR* - This type of error is produced due to product restrictions or due to other account set-up limitations. In all cases, the end result is that the booking cannot be confirmed. Here is a list of common product errors: * *Insufficient allotment*: This means that the user is trying to book a room which is no longer available. This may happen if the room was still available in the Availability stage but someone else has made a reservation for this room or rooms. * *Price has increased*: The price increase between booking steps has exceeded the allowed tolerance that was set. This is a setting to protect clients from booking a room with a higher price than expected. * *Contract is closed/Office or branch not active/Cannot find channel quotation*: There are problems related to the contract. * *Stop sales*: This means that the hotel is forbidding sales on the requested dates. * *Booking confirmation error XXX-YYYYYY*: A confirmation error occurred. Please try again later. * *Release violated* * *There's a stop sales for the date/s* *CONFIGURATION_ERROR* - This type of error is produced by configuration restrictions set-up at account level. Usually this results in the inability to perform an specific operation. Here is a list of common configuration errors: * *This apikey is not associated with a valid client*: This means that the provided apiKey belongs to an inactive client/agency. If you need information regarding the cause for this please contact our support team at [apitude@hotelbeds.com]().

      Parameters:
      accept - Response format.
      acceptEncoding - Defines type of encoding used on the data.
      contentType - Defines request format.
      body - Definition and examples of request body of Booking operation
      Returns:
      ResponseEntity<BookingRS>
      Throws:
      org.springframework.web.reactive.function.client.WebClientResponseException - if an error occurs while attempting to invoke the API

    • bookingWithResponseSpec

      public org.springframework.web.reactive.function.client.WebClient.ResponseSpec bookingWithResponseSpec(String accept, String acceptEncoding, String contentType, BookingRQ body) throws org.springframework.web.reactive.function.client.WebClientResponseException
      Booking confirmation The Booking operation requests a reservation confirmation for the specified ratekey or ratekeys. BookingAPI does not support on-request confirmations. All confirmations are instant confirmations. Timeout for this operation is 60 seconds.

      200 - When the confirmation of a rateKey is successful; the booking reference is provided, along with key information of the booking, which includes: * Hotel confirmed * Holder and pax confirmed * Rate confirmed with the confirmed amounts and dates The response also contains the price breakdown, cancellation policies, supplements, and discounts. Please make sure to **keep the booking reference** of all bookings performed with your credentials, as they are needed for post booking operations such as modification or cancellation.

      400 - **BAD REQUEST** - The server cannot or will not process the request due to an apparent client error. *INVALID_REQUEST* - The request is not compliant with the specified version of the API. The message body will contain more information *INVALID_DATA* - The JSON or XML syntax is correct, however some of the fields contain incorrect data. Please check the documentation for the allowed values and follow the message returned in order to fix this error. *ALLOTMENT EXCEEDED*

      401 - **UNAUTHORIZED** - Authentication has failed or has not been provided. * Authorization field missing * Request signature verification failed

      402 - **PAYMENT** * The parameters were valid but the request failed.

      403 - **FORBIDDEN** - The credentials are correct and authorization was succesful, but access to this resource/operation is not allowed.

      406 - **NOT ACCEPTABLE** - The resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request.

      410 - error repeated

      415 - **UNSUPPORTED MEDIA TYPE** - Use the Content-Type header to set application/json and be sure the format of your payload matches the format

      429 - **Rate limit exceeded** - The user has sent too many requests in a given amount of time.

      500 - **INTERNAL SERVER ERROR** - An unexpected condition was encountered. Possible causes *SYSTEM_ERROR* - These are internal server errors, please send us these errors together with the complete logs (JSON or XML requests and responses) at [apitude@hotelbeds.com]() so that our team can review them. *PRODUCT_ERROR* - This type of error is produced due to product restrictions or due to other account set-up limitations. In all cases, the end result is that the booking cannot be confirmed. Here is a list of common product errors: * *Insufficient allotment*: This means that the user is trying to book a room which is no longer available. This may happen if the room was still available in the Availability stage but someone else has made a reservation for this room or rooms. * *Price has increased*: The price increase between booking steps has exceeded the allowed tolerance that was set. This is a setting to protect clients from booking a room with a higher price than expected. * *Contract is closed/Office or branch not active/Cannot find channel quotation*: There are problems related to the contract. * *Stop sales*: This means that the hotel is forbidding sales on the requested dates. * *Booking confirmation error XXX-YYYYYY*: A confirmation error occurred. Please try again later. * *Release violated* * *There's a stop sales for the date/s* *CONFIGURATION_ERROR* - This type of error is produced by configuration restrictions set-up at account level. Usually this results in the inability to perform an specific operation. Here is a list of common configuration errors: * *This apikey is not associated with a valid client*: This means that the provided apiKey belongs to an inactive client/agency. If you need information regarding the cause for this please contact our support team at [apitude@hotelbeds.com]().

      Parameters:
      accept - Response format.
      acceptEncoding - Defines type of encoding used on the data.
      contentType - Defines request format.
      body - Definition and examples of request body of Booking operation
      Returns:
      ResponseSpec
      Throws:
      org.springframework.web.reactive.function.client.WebClientResponseException - if an error occurs while attempting to invoke the API

    • bookingCancellation

      public reactor.core.publisher.Mono<BookingCancellationRS> bookingCancellation(String accept, String acceptEncoding, String bookingId, String cancellationFlag, String language) throws org.springframework.web.reactive.function.client.WebClientResponseException
      Booking cancellation BookingCancellation is used either to simulate a cancellation or to perform the actual cancellation.Cancellations always take into account day and time of the destination in order to calculate what cancellation policy should be applied. Timeout for this operation is 60 seconds.

      200 - Sample

      401 - **UNAUTHORIZED** - Authentication has failed or has not been provided. * Authorization field missing * Request signature verification failed

      403 - **FORBIDDEN** - The credentials are correct and authorization was succesful, but access to this resource/operation is not allowed.

      406 - **NOT ACCEPTABLE** - The resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request.

      410 - error repeated

      429 - **Rate limit exceeded** - The user has sent too many requests in a given amount of time.

      500 - **INTERNAL SERVER ERROR** - An unexpected condition was encountered. Possible causes *SYSTEM_ERROR* - These are internal server errors, please send us these errors together with the complete logs (JSON or XML requests and responses) at [apitude@hotelbeds.com]() so that our team can review them. *PRODUCT_ERROR* - This type of error is produced due to product restrictions or due to other account set-up limitations. In all cases, the end result is that the booking cannot be confirmed. Here is a list of common product errors: * *Insufficient allotment*: This means that the user is trying to book a room which is no longer available. This may happen if the room was still available in the Availability stage but someone else has made a reservation for this room or rooms. * *Price has increased*: The price increase between booking steps has exceeded the allowed tolerance that was set. This is a setting to protect clients from booking a room with a higher price than expected. * *Contract is closed/Office or branch not active/Cannot find channel quotation*: There are problems related to the contract. * *Stop sales*: This means that the hotel is forbidding sales on the requested dates. * *Booking confirmation error XXX-YYYYYY*: A confirmation error occurred. Please try again later. * *Release violated* * *There's a stop sales for the date/s* *CONFIGURATION_ERROR* - This type of error is produced by configuration restrictions set-up at account level. Usually this results in the inability to perform an specific operation. Here is a list of common configuration errors: * *This apikey is not associated with a valid client*: This means that the provided apiKey belongs to an inactive client/agency. If you need information regarding the cause for this please contact our support team at [apitude@hotelbeds.com]().

      Parameters:
      accept - Response format.
      acceptEncoding - Defines type of encoding used on the data.
      bookingId - Booking reference number taken from the confirmation response or from the booking list function. Format: XXX-YYYYYY
      cancellationFlag - Type of cancellation method to be used.
      language - Language in which the description texts will be returned in the response
      Returns:
      BookingCancellationRS
      Throws:
      org.springframework.web.reactive.function.client.WebClientResponseException - if an error occurs while attempting to invoke the API

    • bookingCancellationWithHttpInfo

      public reactor.core.publisher.Mono<org.springframework.http.ResponseEntity<BookingCancellationRS>> bookingCancellationWithHttpInfo(String accept, String acceptEncoding, String bookingId, String cancellationFlag, String language) throws org.springframework.web.reactive.function.client.WebClientResponseException
      Booking cancellation BookingCancellation is used either to simulate a cancellation or to perform the actual cancellation.Cancellations always take into account day and time of the destination in order to calculate what cancellation policy should be applied. Timeout for this operation is 60 seconds.

      200 - Sample

      401 - **UNAUTHORIZED** - Authentication has failed or has not been provided. * Authorization field missing * Request signature verification failed

      403 - **FORBIDDEN** - The credentials are correct and authorization was succesful, but access to this resource/operation is not allowed.

      406 - **NOT ACCEPTABLE** - The resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request.

      410 - error repeated

      429 - **Rate limit exceeded** - The user has sent too many requests in a given amount of time.

      500 - **INTERNAL SERVER ERROR** - An unexpected condition was encountered. Possible causes *SYSTEM_ERROR* - These are internal server errors, please send us these errors together with the complete logs (JSON or XML requests and responses) at [apitude@hotelbeds.com]() so that our team can review them. *PRODUCT_ERROR* - This type of error is produced due to product restrictions or due to other account set-up limitations. In all cases, the end result is that the booking cannot be confirmed. Here is a list of common product errors: * *Insufficient allotment*: This means that the user is trying to book a room which is no longer available. This may happen if the room was still available in the Availability stage but someone else has made a reservation for this room or rooms. * *Price has increased*: The price increase between booking steps has exceeded the allowed tolerance that was set. This is a setting to protect clients from booking a room with a higher price than expected. * *Contract is closed/Office or branch not active/Cannot find channel quotation*: There are problems related to the contract. * *Stop sales*: This means that the hotel is forbidding sales on the requested dates. * *Booking confirmation error XXX-YYYYYY*: A confirmation error occurred. Please try again later. * *Release violated* * *There's a stop sales for the date/s* *CONFIGURATION_ERROR* - This type of error is produced by configuration restrictions set-up at account level. Usually this results in the inability to perform an specific operation. Here is a list of common configuration errors: * *This apikey is not associated with a valid client*: This means that the provided apiKey belongs to an inactive client/agency. If you need information regarding the cause for this please contact our support team at [apitude@hotelbeds.com]().

      Parameters:
      accept - Response format.
      acceptEncoding - Defines type of encoding used on the data.
      bookingId - Booking reference number taken from the confirmation response or from the booking list function. Format: XXX-YYYYYY
      cancellationFlag - Type of cancellation method to be used.
      language - Language in which the description texts will be returned in the response
      Returns:
      ResponseEntity<BookingCancellationRS>
      Throws:
      org.springframework.web.reactive.function.client.WebClientResponseException - if an error occurs while attempting to invoke the API

    • bookingCancellationWithResponseSpec

      public org.springframework.web.reactive.function.client.WebClient.ResponseSpec bookingCancellationWithResponseSpec(String accept, String acceptEncoding, String bookingId, String cancellationFlag, String language) throws org.springframework.web.reactive.function.client.WebClientResponseException
      Booking cancellation BookingCancellation is used either to simulate a cancellation or to perform the actual cancellation.Cancellations always take into account day and time of the destination in order to calculate what cancellation policy should be applied. Timeout for this operation is 60 seconds.

      200 - Sample

      401 - **UNAUTHORIZED** - Authentication has failed or has not been provided. * Authorization field missing * Request signature verification failed

      403 - **FORBIDDEN** - The credentials are correct and authorization was succesful, but access to this resource/operation is not allowed.

      406 - **NOT ACCEPTABLE** - The resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request.

      410 - error repeated

      429 - **Rate limit exceeded** - The user has sent too many requests in a given amount of time.

      500 - **INTERNAL SERVER ERROR** - An unexpected condition was encountered. Possible causes *SYSTEM_ERROR* - These are internal server errors, please send us these errors together with the complete logs (JSON or XML requests and responses) at [apitude@hotelbeds.com]() so that our team can review them. *PRODUCT_ERROR* - This type of error is produced due to product restrictions or due to other account set-up limitations. In all cases, the end result is that the booking cannot be confirmed. Here is a list of common product errors: * *Insufficient allotment*: This means that the user is trying to book a room which is no longer available. This may happen if the room was still available in the Availability stage but someone else has made a reservation for this room or rooms. * *Price has increased*: The price increase between booking steps has exceeded the allowed tolerance that was set. This is a setting to protect clients from booking a room with a higher price than expected. * *Contract is closed/Office or branch not active/Cannot find channel quotation*: There are problems related to the contract. * *Stop sales*: This means that the hotel is forbidding sales on the requested dates. * *Booking confirmation error XXX-YYYYYY*: A confirmation error occurred. Please try again later. * *Release violated* * *There's a stop sales for the date/s* *CONFIGURATION_ERROR* - This type of error is produced by configuration restrictions set-up at account level. Usually this results in the inability to perform an specific operation. Here is a list of common configuration errors: * *This apikey is not associated with a valid client*: This means that the provided apiKey belongs to an inactive client/agency. If you need information regarding the cause for this please contact our support team at [apitude@hotelbeds.com]().

      Parameters:
      accept - Response format.
      acceptEncoding - Defines type of encoding used on the data.
      bookingId - Booking reference number taken from the confirmation response or from the booking list function. Format: XXX-YYYYYY
      cancellationFlag - Type of cancellation method to be used.
      language - Language in which the description texts will be returned in the response
      Returns:
      ResponseSpec
      Throws:
      org.springframework.web.reactive.function.client.WebClientResponseException - if an error occurs while attempting to invoke the API

    • bookingChange

      public reactor.core.publisher.Mono<BookingChangeRS> bookingChange(String accept, String acceptEncoding, String contentType, String bookingId, BookingChangeRQ body) throws org.springframework.web.reactive.function.client.WebClientResponseException
      Booking change The BookingChange operation is used to change or update different values of a booking. The changes that can be performed are: * Change clientReference * Change remarks * Change holder name and surname * Change checkIn and checkOut date * Change board plans * Change passengers name and surname * Add rooms (only from the same type already in the booking) * Remove rooms from a booking (partial cancellation)

      200 - Sample

      401 - **UNAUTHORIZED** - Authentication has failed or has not been provided. * Authorization field missing * Request signature verification failed

      402 - **PAYMENT** * The parameters were valid but the request failed.

      403 - **FORBIDDEN** - The credentials are correct and authorization was succesful, but access to this resource/operation is not allowed.

      406 - **NOT ACCEPTABLE** - The resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request.

      429 - **Rate limit exceeded** - The user has sent too many requests in a given amount of time.

      500 - **INTERNAL SERVER ERROR** - An unexpected condition was encountered. Possible causes *SYSTEM_ERROR* - These are internal server errors, please send us these errors together with the complete logs (JSON or XML requests and responses) at [apitude@hotelbeds.com]() so that our team can review them. *PRODUCT_ERROR* - This type of error is produced due to product restrictions or due to other account set-up limitations. In all cases, the end result is that the booking cannot be confirmed. Here is a list of common product errors: * *Insufficient allotment*: This means that the user is trying to book a room which is no longer available. This may happen if the room was still available in the Availability stage but someone else has made a reservation for this room or rooms. * *Price has increased*: The price increase between booking steps has exceeded the allowed tolerance that was set. This is a setting to protect clients from booking a room with a higher price than expected. * *Contract is closed/Office or branch not active/Cannot find channel quotation*: There are problems related to the contract. * *Stop sales*: This means that the hotel is forbidding sales on the requested dates. * *Booking confirmation error XXX-YYYYYY*: A confirmation error occurred. Please try again later. * *Release violated* * *There's a stop sales for the date/s* *CONFIGURATION_ERROR* - This type of error is produced by configuration restrictions set-up at account level. Usually this results in the inability to perform an specific operation. Here is a list of common configuration errors: * *This apikey is not associated with a valid client*: This means that the provided apiKey belongs to an inactive client/agency. If you need information regarding the cause for this please contact our support team at [apitude@hotelbeds.com]().

      503 - **SERVICE UNAVAILABLE** - The server is currently unable to handle the request due to a temporary condition which will be alleviated after some delay. You can choose to resend the request again. * *BOOKING CHANGE* - Error during cancellation, the booking XXX-YYYYY is locked. Please try again later. *SERVICE_OVERLOAD* - The server is currently unable to handle the request due to an overwhelming number of requests being processed. Condition which will be alleviated after some delay.

      Parameters:
      accept - Response format.
      acceptEncoding - Defines type of encoding used on the data.
      contentType - Defines request format.
      bookingId - Booking reference number taken from the confirmation response or from the booking list function. Format: XXX-YYYYYY
      body - Definition and examples of request body of BookingChange operation
      Returns:
      BookingChangeRS
      Throws:
      org.springframework.web.reactive.function.client.WebClientResponseException - if an error occurs while attempting to invoke the API

    • bookingChangeWithHttpInfo

      public reactor.core.publisher.Mono<org.springframework.http.ResponseEntity<BookingChangeRS>> bookingChangeWithHttpInfo(String accept, String acceptEncoding, String contentType, String bookingId, BookingChangeRQ body) throws org.springframework.web.reactive.function.client.WebClientResponseException
      Booking change The BookingChange operation is used to change or update different values of a booking. The changes that can be performed are: * Change clientReference * Change remarks * Change holder name and surname * Change checkIn and checkOut date * Change board plans * Change passengers name and surname * Add rooms (only from the same type already in the booking) * Remove rooms from a booking (partial cancellation)

      200 - Sample

      401 - **UNAUTHORIZED** - Authentication has failed or has not been provided. * Authorization field missing * Request signature verification failed

      402 - **PAYMENT** * The parameters were valid but the request failed.

      403 - **FORBIDDEN** - The credentials are correct and authorization was succesful, but access to this resource/operation is not allowed.

      406 - **NOT ACCEPTABLE** - The resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request.

      429 - **Rate limit exceeded** - The user has sent too many requests in a given amount of time.

      500 - **INTERNAL SERVER ERROR** - An unexpected condition was encountered. Possible causes *SYSTEM_ERROR* - These are internal server errors, please send us these errors together with the complete logs (JSON or XML requests and responses) at [apitude@hotelbeds.com]() so that our team can review them. *PRODUCT_ERROR* - This type of error is produced due to product restrictions or due to other account set-up limitations. In all cases, the end result is that the booking cannot be confirmed. Here is a list of common product errors: * *Insufficient allotment*: This means that the user is trying to book a room which is no longer available. This may happen if the room was still available in the Availability stage but someone else has made a reservation for this room or rooms. * *Price has increased*: The price increase between booking steps has exceeded the allowed tolerance that was set. This is a setting to protect clients from booking a room with a higher price than expected. * *Contract is closed/Office or branch not active/Cannot find channel quotation*: There are problems related to the contract. * *Stop sales*: This means that the hotel is forbidding sales on the requested dates. * *Booking confirmation error XXX-YYYYYY*: A confirmation error occurred. Please try again later. * *Release violated* * *There's a stop sales for the date/s* *CONFIGURATION_ERROR* - This type of error is produced by configuration restrictions set-up at account level. Usually this results in the inability to perform an specific operation. Here is a list of common configuration errors: * *This apikey is not associated with a valid client*: This means that the provided apiKey belongs to an inactive client/agency. If you need information regarding the cause for this please contact our support team at [apitude@hotelbeds.com]().

      503 - **SERVICE UNAVAILABLE** - The server is currently unable to handle the request due to a temporary condition which will be alleviated after some delay. You can choose to resend the request again. * *BOOKING CHANGE* - Error during cancellation, the booking XXX-YYYYY is locked. Please try again later. *SERVICE_OVERLOAD* - The server is currently unable to handle the request due to an overwhelming number of requests being processed. Condition which will be alleviated after some delay.

      Parameters:
      accept - Response format.
      acceptEncoding - Defines type of encoding used on the data.
      contentType - Defines request format.
      bookingId - Booking reference number taken from the confirmation response or from the booking list function. Format: XXX-YYYYYY
      body - Definition and examples of request body of BookingChange operation
      Returns:
      ResponseEntity<BookingChangeRS>
      Throws:
      org.springframework.web.reactive.function.client.WebClientResponseException - if an error occurs while attempting to invoke the API

    • bookingChangeWithResponseSpec

      public org.springframework.web.reactive.function.client.WebClient.ResponseSpec bookingChangeWithResponseSpec(String accept, String acceptEncoding, String contentType, String bookingId, BookingChangeRQ body) throws org.springframework.web.reactive.function.client.WebClientResponseException
      Booking change The BookingChange operation is used to change or update different values of a booking. The changes that can be performed are: * Change clientReference * Change remarks * Change holder name and surname * Change checkIn and checkOut date * Change board plans * Change passengers name and surname * Add rooms (only from the same type already in the booking) * Remove rooms from a booking (partial cancellation)

      200 - Sample

      401 - **UNAUTHORIZED** - Authentication has failed or has not been provided. * Authorization field missing * Request signature verification failed

      402 - **PAYMENT** * The parameters were valid but the request failed.

      403 - **FORBIDDEN** - The credentials are correct and authorization was succesful, but access to this resource/operation is not allowed.

      406 - **NOT ACCEPTABLE** - The resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request.

      429 - **Rate limit exceeded** - The user has sent too many requests in a given amount of time.

      500 - **INTERNAL SERVER ERROR** - An unexpected condition was encountered. Possible causes *SYSTEM_ERROR* - These are internal server errors, please send us these errors together with the complete logs (JSON or XML requests and responses) at [apitude@hotelbeds.com]() so that our team can review them. *PRODUCT_ERROR* - This type of error is produced due to product restrictions or due to other account set-up limitations. In all cases, the end result is that the booking cannot be confirmed. Here is a list of common product errors: * *Insufficient allotment*: This means that the user is trying to book a room which is no longer available. This may happen if the room was still available in the Availability stage but someone else has made a reservation for this room or rooms. * *Price has increased*: The price increase between booking steps has exceeded the allowed tolerance that was set. This is a setting to protect clients from booking a room with a higher price than expected. * *Contract is closed/Office or branch not active/Cannot find channel quotation*: There are problems related to the contract. * *Stop sales*: This means that the hotel is forbidding sales on the requested dates. * *Booking confirmation error XXX-YYYYYY*: A confirmation error occurred. Please try again later. * *Release violated* * *There's a stop sales for the date/s* *CONFIGURATION_ERROR* - This type of error is produced by configuration restrictions set-up at account level. Usually this results in the inability to perform an specific operation. Here is a list of common configuration errors: * *This apikey is not associated with a valid client*: This means that the provided apiKey belongs to an inactive client/agency. If you need information regarding the cause for this please contact our support team at [apitude@hotelbeds.com]().

      503 - **SERVICE UNAVAILABLE** - The server is currently unable to handle the request due to a temporary condition which will be alleviated after some delay. You can choose to resend the request again. * *BOOKING CHANGE* - Error during cancellation, the booking XXX-YYYYY is locked. Please try again later. *SERVICE_OVERLOAD* - The server is currently unable to handle the request due to an overwhelming number of requests being processed. Condition which will be alleviated after some delay.

      Parameters:
      accept - Response format.
      acceptEncoding - Defines type of encoding used on the data.
      contentType - Defines request format.
      bookingId - Booking reference number taken from the confirmation response or from the booking list function. Format: XXX-YYYYYY
      body - Definition and examples of request body of BookingChange operation
      Returns:
      ResponseSpec
      Throws:
      org.springframework.web.reactive.function.client.WebClientResponseException - if an error occurs while attempting to invoke the API

    • bookingDetail

      public reactor.core.publisher.Mono<BookingDetailRS> bookingDetail(String accept, String acceptEncoding, String bookingId, String language) throws org.springframework.web.reactive.function.client.WebClientResponseException
      Booking detail The BookingDetail operation allows to retrieve a booking with all its details from the booking reference locator.

      200 - Sample

      401 - **UNAUTHORIZED** - Authentication has failed or has not been provided. * Authorization field missing * Request signature verification failed

      403 - **FORBIDDEN** - The credentials are correct and authorization was succesful, but access to this resource/operation is not allowed.

      406 - **NOT ACCEPTABLE** - The resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request.

      429 - **Rate limit exceeded** - The user has sent too many requests in a given amount of time.

      500 - **INTERNAL SERVER ERROR** - An unexpected condition was encountered. Possible causes *SYSTEM_ERROR* - These are internal server errors, please send us these errors together with the complete logs (JSON or XML requests and responses) at [apitude@hotelbeds.com]() so that our team can review them. *PRODUCT_ERROR* - This type of error is produced due to product restrictions or due to other account set-up limitations. In all cases, the end result is that the booking cannot be confirmed. Here is a list of common product errors: * *Insufficient allotment*: This means that the user is trying to book a room which is no longer available. This may happen if the room was still available in the Availability stage but someone else has made a reservation for this room or rooms. * *Price has increased*: The price increase between booking steps has exceeded the allowed tolerance that was set. This is a setting to protect clients from booking a room with a higher price than expected. * *Contract is closed/Office or branch not active/Cannot find channel quotation*: There are problems related to the contract. * *Stop sales*: This means that the hotel is forbidding sales on the requested dates. * *Booking confirmation error XXX-YYYYYY*: A confirmation error occurred. Please try again later. * *Release violated* * *There's a stop sales for the date/s* *CONFIGURATION_ERROR* - This type of error is produced by configuration restrictions set-up at account level. Usually this results in the inability to perform an specific operation. Here is a list of common configuration errors: * *This apikey is not associated with a valid client*: This means that the provided apiKey belongs to an inactive client/agency. If you need information regarding the cause for this please contact our support team at [apitude@hotelbeds.com]().

      Parameters:
      accept - Response format.
      acceptEncoding - Defines type of encoding used on the data.
      bookingId - Booking reference number taken from the confirmation response or from the booking list function. Format: XXX-YYYYYY
      language - Language code that defines the language of the response. English will be used by default if this parameter is not informed.
      Returns:
      BookingDetailRS
      Throws:
      org.springframework.web.reactive.function.client.WebClientResponseException - if an error occurs while attempting to invoke the API

    • bookingDetailWithHttpInfo

      public reactor.core.publisher.Mono<org.springframework.http.ResponseEntity<BookingDetailRS>> bookingDetailWithHttpInfo(String accept, String acceptEncoding, String bookingId, String language) throws org.springframework.web.reactive.function.client.WebClientResponseException
      Booking detail The BookingDetail operation allows to retrieve a booking with all its details from the booking reference locator.

      200 - Sample

      401 - **UNAUTHORIZED** - Authentication has failed or has not been provided. * Authorization field missing * Request signature verification failed

      403 - **FORBIDDEN** - The credentials are correct and authorization was succesful, but access to this resource/operation is not allowed.

      406 - **NOT ACCEPTABLE** - The resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request.

      429 - **Rate limit exceeded** - The user has sent too many requests in a given amount of time.

      500 - **INTERNAL SERVER ERROR** - An unexpected condition was encountered. Possible causes *SYSTEM_ERROR* - These are internal server errors, please send us these errors together with the complete logs (JSON or XML requests and responses) at [apitude@hotelbeds.com]() so that our team can review them. *PRODUCT_ERROR* - This type of error is produced due to product restrictions or due to other account set-up limitations. In all cases, the end result is that the booking cannot be confirmed. Here is a list of common product errors: * *Insufficient allotment*: This means that the user is trying to book a room which is no longer available. This may happen if the room was still available in the Availability stage but someone else has made a reservation for this room or rooms. * *Price has increased*: The price increase between booking steps has exceeded the allowed tolerance that was set. This is a setting to protect clients from booking a room with a higher price than expected. * *Contract is closed/Office or branch not active/Cannot find channel quotation*: There are problems related to the contract. * *Stop sales*: This means that the hotel is forbidding sales on the requested dates. * *Booking confirmation error XXX-YYYYYY*: A confirmation error occurred. Please try again later. * *Release violated* * *There's a stop sales for the date/s* *CONFIGURATION_ERROR* - This type of error is produced by configuration restrictions set-up at account level. Usually this results in the inability to perform an specific operation. Here is a list of common configuration errors: * *This apikey is not associated with a valid client*: This means that the provided apiKey belongs to an inactive client/agency. If you need information regarding the cause for this please contact our support team at [apitude@hotelbeds.com]().

      Parameters:
      accept - Response format.
      acceptEncoding - Defines type of encoding used on the data.
      bookingId - Booking reference number taken from the confirmation response or from the booking list function. Format: XXX-YYYYYY
      language - Language code that defines the language of the response. English will be used by default if this parameter is not informed.
      Returns:
      ResponseEntity<BookingDetailRS>
      Throws:
      org.springframework.web.reactive.function.client.WebClientResponseException - if an error occurs while attempting to invoke the API

    • bookingDetailWithResponseSpec

      public org.springframework.web.reactive.function.client.WebClient.ResponseSpec bookingDetailWithResponseSpec(String accept, String acceptEncoding, String bookingId, String language) throws org.springframework.web.reactive.function.client.WebClientResponseException
      Booking detail The BookingDetail operation allows to retrieve a booking with all its details from the booking reference locator.

      200 - Sample

      401 - **UNAUTHORIZED** - Authentication has failed or has not been provided. * Authorization field missing * Request signature verification failed

      403 - **FORBIDDEN** - The credentials are correct and authorization was succesful, but access to this resource/operation is not allowed.

      406 - **NOT ACCEPTABLE** - The resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request.

      429 - **Rate limit exceeded** - The user has sent too many requests in a given amount of time.

      500 - **INTERNAL SERVER ERROR** - An unexpected condition was encountered. Possible causes *SYSTEM_ERROR* - These are internal server errors, please send us these errors together with the complete logs (JSON or XML requests and responses) at [apitude@hotelbeds.com]() so that our team can review them. *PRODUCT_ERROR* - This type of error is produced due to product restrictions or due to other account set-up limitations. In all cases, the end result is that the booking cannot be confirmed. Here is a list of common product errors: * *Insufficient allotment*: This means that the user is trying to book a room which is no longer available. This may happen if the room was still available in the Availability stage but someone else has made a reservation for this room or rooms. * *Price has increased*: The price increase between booking steps has exceeded the allowed tolerance that was set. This is a setting to protect clients from booking a room with a higher price than expected. * *Contract is closed/Office or branch not active/Cannot find channel quotation*: There are problems related to the contract. * *Stop sales*: This means that the hotel is forbidding sales on the requested dates. * *Booking confirmation error XXX-YYYYYY*: A confirmation error occurred. Please try again later. * *Release violated* * *There's a stop sales for the date/s* *CONFIGURATION_ERROR* - This type of error is produced by configuration restrictions set-up at account level. Usually this results in the inability to perform an specific operation. Here is a list of common configuration errors: * *This apikey is not associated with a valid client*: This means that the provided apiKey belongs to an inactive client/agency. If you need information regarding the cause for this please contact our support team at [apitude@hotelbeds.com]().

      Parameters:
      accept - Response format.
      acceptEncoding - Defines type of encoding used on the data.
      bookingId - Booking reference number taken from the confirmation response or from the booking list function. Format: XXX-YYYYYY
      language - Language code that defines the language of the response. English will be used by default if this parameter is not informed.
      Returns:
      ResponseSpec
      Throws:
      org.springframework.web.reactive.function.client.WebClientResponseException - if an error occurs while attempting to invoke the API

    • bookingList

      public reactor.core.publisher.Mono<BookingListRS> bookingList(String accept, String acceptEncoding, String contentType, Integer from, Integer to, LocalDate start, LocalDate end, String filterType, String status, String clientReference, String creationUser, List<String> country, List<String> destination, List<Integer> hotel) throws org.springframework.web.reactive.function.client.WebClientResponseException
      Booking list The booking list operation returns a list of bookings based on the search criteria. The most important information returned for each booking in the list is: * Booking reference * Booking holder * Booking paxes * Hotel, rooms and boards confirmed * Booking rates The results are returned in a paginated response that can be filtered with the use of parameters in the request. Timeout for this operation is 60 seconds.

      200 - Sucessful response

      401 - **UNAUTHORIZED** - Authentication has failed or has not been provided. * Authorization field missing * Request signature verification failed

      403 - **FORBIDDEN** - The credentials are correct and authorization was succesful, but access to this resource/operation is not allowed.

      406 - **NOT ACCEPTABLE** - The resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request.

      429 - **Rate limit exceeded** - The user has sent too many requests in a given amount of time.

      500 - **INTERNAL SERVER ERROR** - An unexpected condition was encountered. Possible causes *SYSTEM_ERROR* - These are internal server errors, please send us these errors together with the complete logs (JSON or XML requests and responses) at [apitude@hotelbeds.com]() so that our team can review them. *PRODUCT_ERROR* - This type of error is produced due to product restrictions or due to other account set-up limitations. In all cases, the end result is that the booking cannot be confirmed. Here is a list of common product errors: * *Insufficient allotment*: This means that the user is trying to book a room which is no longer available. This may happen if the room was still available in the Availability stage but someone else has made a reservation for this room or rooms. * *Price has increased*: The price increase between booking steps has exceeded the allowed tolerance that was set. This is a setting to protect clients from booking a room with a higher price than expected. * *Contract is closed/Office or branch not active/Cannot find channel quotation*: There are problems related to the contract. * *Stop sales*: This means that the hotel is forbidding sales on the requested dates. * *Booking confirmation error XXX-YYYYYY*: A confirmation error occurred. Please try again later. * *Release violated* * *There's a stop sales for the date/s* *CONFIGURATION_ERROR* - This type of error is produced by configuration restrictions set-up at account level. Usually this results in the inability to perform an specific operation. Here is a list of common configuration errors: * *This apikey is not associated with a valid client*: This means that the provided apiKey belongs to an inactive client/agency. If you need information regarding the cause for this please contact our support team at [apitude@hotelbeds.com]().

      Parameters:
      accept - Response format.
      acceptEncoding - Defines type of encoding used on the data.
      contentType - Defines request format.
      from - Defines the lowest value of the range of bookings to be returned.
      to - Defines the highest value of the range of bookings to be returned.
      start - Defines the starting date of the range of bookings to be returned.
      end - Defines the ending date of the range of bookings to be returned. value.
      filterType - Parameter used to define wether **start** and **end** fields are filtering by check-in date or by booking creation date.
      status - Parameter used to filter results by status. Can be used to include or exclude cancelled bookings.
      clientReference - Parameter to filter the result by the __clientReference__ field of the booking.
      creationUser - Parameter to filter the result by the creationUser field of the booking.
      country - Parameter to filter the results by the country code of the hotel. Can include multiple values separated by commas.
      destination - Parameter to filter the results by the destination code of the hotel. Can include multiple values separated by commas.
      hotel - Parameter to filter the results by the hotel codes. Can include multiple values separated by commas.
      Returns:
      BookingListRS
      Throws:
      org.springframework.web.reactive.function.client.WebClientResponseException - if an error occurs while attempting to invoke the API

    • bookingListWithHttpInfo

      public reactor.core.publisher.Mono<org.springframework.http.ResponseEntity<BookingListRS>> bookingListWithHttpInfo(String accept, String acceptEncoding, String contentType, Integer from, Integer to, LocalDate start, LocalDate end, String filterType, String status, String clientReference, String creationUser, List<String> country, List<String> destination, List<Integer> hotel) throws org.springframework.web.reactive.function.client.WebClientResponseException
      Booking list The booking list operation returns a list of bookings based on the search criteria. The most important information returned for each booking in the list is: * Booking reference * Booking holder * Booking paxes * Hotel, rooms and boards confirmed * Booking rates The results are returned in a paginated response that can be filtered with the use of parameters in the request. Timeout for this operation is 60 seconds.

      200 - Sucessful response

      401 - **UNAUTHORIZED** - Authentication has failed or has not been provided. * Authorization field missing * Request signature verification failed

      403 - **FORBIDDEN** - The credentials are correct and authorization was succesful, but access to this resource/operation is not allowed.

      406 - **NOT ACCEPTABLE** - The resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request.

      429 - **Rate limit exceeded** - The user has sent too many requests in a given amount of time.

      500 - **INTERNAL SERVER ERROR** - An unexpected condition was encountered. Possible causes *SYSTEM_ERROR* - These are internal server errors, please send us these errors together with the complete logs (JSON or XML requests and responses) at [apitude@hotelbeds.com]() so that our team can review them. *PRODUCT_ERROR* - This type of error is produced due to product restrictions or due to other account set-up limitations. In all cases, the end result is that the booking cannot be confirmed. Here is a list of common product errors: * *Insufficient allotment*: This means that the user is trying to book a room which is no longer available. This may happen if the room was still available in the Availability stage but someone else has made a reservation for this room or rooms. * *Price has increased*: The price increase between booking steps has exceeded the allowed tolerance that was set. This is a setting to protect clients from booking a room with a higher price than expected. * *Contract is closed/Office or branch not active/Cannot find channel quotation*: There are problems related to the contract. * *Stop sales*: This means that the hotel is forbidding sales on the requested dates. * *Booking confirmation error XXX-YYYYYY*: A confirmation error occurred. Please try again later. * *Release violated* * *There's a stop sales for the date/s* *CONFIGURATION_ERROR* - This type of error is produced by configuration restrictions set-up at account level. Usually this results in the inability to perform an specific operation. Here is a list of common configuration errors: * *This apikey is not associated with a valid client*: This means that the provided apiKey belongs to an inactive client/agency. If you need information regarding the cause for this please contact our support team at [apitude@hotelbeds.com]().

      Parameters:
      accept - Response format.
      acceptEncoding - Defines type of encoding used on the data.
      contentType - Defines request format.
      from - Defines the lowest value of the range of bookings to be returned.
      to - Defines the highest value of the range of bookings to be returned.
      start - Defines the starting date of the range of bookings to be returned.
      end - Defines the ending date of the range of bookings to be returned. value.
      filterType - Parameter used to define wether **start** and **end** fields are filtering by check-in date or by booking creation date.
      status - Parameter used to filter results by status. Can be used to include or exclude cancelled bookings.
      clientReference - Parameter to filter the result by the __clientReference__ field of the booking.
      creationUser - Parameter to filter the result by the creationUser field of the booking.
      country - Parameter to filter the results by the country code of the hotel. Can include multiple values separated by commas.
      destination - Parameter to filter the results by the destination code of the hotel. Can include multiple values separated by commas.
      hotel - Parameter to filter the results by the hotel codes. Can include multiple values separated by commas.
      Returns:
      ResponseEntity<BookingListRS>
      Throws:
      org.springframework.web.reactive.function.client.WebClientResponseException - if an error occurs while attempting to invoke the API

    • bookingListWithResponseSpec

      public org.springframework.web.reactive.function.client.WebClient.ResponseSpec bookingListWithResponseSpec(String accept, String acceptEncoding, String contentType, Integer from, Integer to, LocalDate start, LocalDate end, String filterType, String status, String clientReference, String creationUser, List<String> country, List<String> destination, List<Integer> hotel) throws org.springframework.web.reactive.function.client.WebClientResponseException
      Booking list The booking list operation returns a list of bookings based on the search criteria. The most important information returned for each booking in the list is: * Booking reference * Booking holder * Booking paxes * Hotel, rooms and boards confirmed * Booking rates The results are returned in a paginated response that can be filtered with the use of parameters in the request. Timeout for this operation is 60 seconds.

      200 - Sucessful response

      401 - **UNAUTHORIZED** - Authentication has failed or has not been provided. * Authorization field missing * Request signature verification failed

      403 - **FORBIDDEN** - The credentials are correct and authorization was succesful, but access to this resource/operation is not allowed.

      406 - **NOT ACCEPTABLE** - The resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request.

      429 - **Rate limit exceeded** - The user has sent too many requests in a given amount of time.

      500 - **INTERNAL SERVER ERROR** - An unexpected condition was encountered. Possible causes *SYSTEM_ERROR* - These are internal server errors, please send us these errors together with the complete logs (JSON or XML requests and responses) at [apitude@hotelbeds.com]() so that our team can review them. *PRODUCT_ERROR* - This type of error is produced due to product restrictions or due to other account set-up limitations. In all cases, the end result is that the booking cannot be confirmed. Here is a list of common product errors: * *Insufficient allotment*: This means that the user is trying to book a room which is no longer available. This may happen if the room was still available in the Availability stage but someone else has made a reservation for this room or rooms. * *Price has increased*: The price increase between booking steps has exceeded the allowed tolerance that was set. This is a setting to protect clients from booking a room with a higher price than expected. * *Contract is closed/Office or branch not active/Cannot find channel quotation*: There are problems related to the contract. * *Stop sales*: This means that the hotel is forbidding sales on the requested dates. * *Booking confirmation error XXX-YYYYYY*: A confirmation error occurred. Please try again later. * *Release violated* * *There's a stop sales for the date/s* *CONFIGURATION_ERROR* - This type of error is produced by configuration restrictions set-up at account level. Usually this results in the inability to perform an specific operation. Here is a list of common configuration errors: * *This apikey is not associated with a valid client*: This means that the provided apiKey belongs to an inactive client/agency. If you need information regarding the cause for this please contact our support team at [apitude@hotelbeds.com]().

      Parameters:
      accept - Response format.
      acceptEncoding - Defines type of encoding used on the data.
      contentType - Defines request format.
      from - Defines the lowest value of the range of bookings to be returned.
      to - Defines the highest value of the range of bookings to be returned.
      start - Defines the starting date of the range of bookings to be returned.
      end - Defines the ending date of the range of bookings to be returned. value.
      filterType - Parameter used to define wether **start** and **end** fields are filtering by check-in date or by booking creation date.
      status - Parameter used to filter results by status. Can be used to include or exclude cancelled bookings.
      clientReference - Parameter to filter the result by the __clientReference__ field of the booking.
      creationUser - Parameter to filter the result by the creationUser field of the booking.
      country - Parameter to filter the results by the country code of the hotel. Can include multiple values separated by commas.
      destination - Parameter to filter the results by the destination code of the hotel. Can include multiple values separated by commas.
      hotel - Parameter to filter the results by the hotel codes. Can include multiple values separated by commas.
      Returns:
      ResponseSpec
      Throws:
      org.springframework.web.reactive.function.client.WebClientResponseException - if an error occurs while attempting to invoke the API

    • bookingreconfirmation

      public reactor.core.publisher.Mono<Void> bookingreconfirmation(String accept, String acceptEncoding, Integer from, Integer to, LocalDate start, LocalDate end, String filterType, List<String> clientReferences, List<String> references) throws org.springframework.web.reactive.function.client.WebClientResponseException
      Booking reconfirmation The Reconfirmation operation allows to retrieve the reconfirmation numbers (The confirmation number of the Hotel, both for the Hotelbeds product and for that of external suppliers product) of the bookings made by the client when requested in a GET call to our endpoint. Obtaining this reconfirmation numbers from hoteliers is an __asynchronous__ service: **reconfirmation numbers are not available at the time of the booking**, and as such they can't be informed at the time of the booking, hence the need for this operation. The Reconfirmation operation offers a wide variety of filters to help narrowing down reconfirmation number results. Only one filter can be used at the same time. Below the four possible filters you can use: * between two cheking dates * between two reconfirmation dates * list of clientReference ids * list of booking Ids ## Reconfirmation Service Additionally we offer you the capacity to receive the reconfirmation numbers automatically in our reconformation service, designed to automatically send you the reconfirmation information as soon as is available from the hoteliers in two different ways: * [Push Service](/documentation/hotels/booking-api/reconfirmation-service/push-service/) : The messages will be automatically sent in JSON format to an endpoint of your choice. * [Email Service](/documentation/hotels/booking-api/reconfirmation-service/email-service/): The messages will be automatically sent in an email to an address of your choice. Contact our support team at [apitude@hotelbeds.com]() to learn more about this features.

      200 - Sucessful response

      Parameters:
      accept - Response format.
      acceptEncoding - Defines type of encoding used on the data.
      from - Lowest value of the range of bookings with supplierConfirmationCodes to be returned (as in a paginated response).
      to - Highest value of the range of bookings with supplierConfirmationCodes to be returned (as in a paginated response).
      start - Date from when the method will start checking reconfirmation numbers. The format must be YYYY-MM-DD. In case of using __start__ and __end__ parameters, the use of __filterType__ parameter is mandatory.
      end - Date to when the method will finish checking reconfirmation numbers. The format must be YYYY-MM-DD. In case of using __start__ and __end__ parameters, the use of __filterType__ parameter is mandatory.
      filterType - The parameter is used to identify if the reconfirmation numbers is by check-in date or by reconfirmation date. Values: * CHECKIN: for the check-in date. * RECONFIRMATION: for the reconfirmation date the booking was included in Hotelbeds systems. In case of using __filterType__ parameters, the use of __start__ and __end__ parameters is mandatory.
      clientReferences - Parameter to filter the results by the booking reference in client API side.Can include multiple values separated by \",\". Max 80 values.
      references - Parameter to filter the results by the booking reference in Hotelbeds side.Can include multiple values separated by \",\". Max 80 values.
      Throws:
      org.springframework.web.reactive.function.client.WebClientResponseException - if an error occurs while attempting to invoke the API

    • bookingreconfirmationWithHttpInfo

      public reactor.core.publisher.Mono<org.springframework.http.ResponseEntity<Void>> bookingreconfirmationWithHttpInfo(String accept, String acceptEncoding, Integer from, Integer to, LocalDate start, LocalDate end, String filterType, List<String> clientReferences, List<String> references) throws org.springframework.web.reactive.function.client.WebClientResponseException
      Booking reconfirmation The Reconfirmation operation allows to retrieve the reconfirmation numbers (The confirmation number of the Hotel, both for the Hotelbeds product and for that of external suppliers product) of the bookings made by the client when requested in a GET call to our endpoint. Obtaining this reconfirmation numbers from hoteliers is an __asynchronous__ service: **reconfirmation numbers are not available at the time of the booking**, and as such they can't be informed at the time of the booking, hence the need for this operation. The Reconfirmation operation offers a wide variety of filters to help narrowing down reconfirmation number results. Only one filter can be used at the same time. Below the four possible filters you can use: * between two cheking dates * between two reconfirmation dates * list of clientReference ids * list of booking Ids ## Reconfirmation Service Additionally we offer you the capacity to receive the reconfirmation numbers automatically in our reconformation service, designed to automatically send you the reconfirmation information as soon as is available from the hoteliers in two different ways: * [Push Service](/documentation/hotels/booking-api/reconfirmation-service/push-service/) : The messages will be automatically sent in JSON format to an endpoint of your choice. * [Email Service](/documentation/hotels/booking-api/reconfirmation-service/email-service/): The messages will be automatically sent in an email to an address of your choice. Contact our support team at [apitude@hotelbeds.com]() to learn more about this features.

      200 - Sucessful response

      Parameters:
      accept - Response format.
      acceptEncoding - Defines type of encoding used on the data.
      from - Lowest value of the range of bookings with supplierConfirmationCodes to be returned (as in a paginated response).
      to - Highest value of the range of bookings with supplierConfirmationCodes to be returned (as in a paginated response).
      start - Date from when the method will start checking reconfirmation numbers. The format must be YYYY-MM-DD. In case of using __start__ and __end__ parameters, the use of __filterType__ parameter is mandatory.
      end - Date to when the method will finish checking reconfirmation numbers. The format must be YYYY-MM-DD. In case of using __start__ and __end__ parameters, the use of __filterType__ parameter is mandatory.
      filterType - The parameter is used to identify if the reconfirmation numbers is by check-in date or by reconfirmation date. Values: * CHECKIN: for the check-in date. * RECONFIRMATION: for the reconfirmation date the booking was included in Hotelbeds systems. In case of using __filterType__ parameters, the use of __start__ and __end__ parameters is mandatory.
      clientReferences - Parameter to filter the results by the booking reference in client API side.Can include multiple values separated by \",\". Max 80 values.
      references - Parameter to filter the results by the booking reference in Hotelbeds side.Can include multiple values separated by \",\". Max 80 values.
      Throws:
      org.springframework.web.reactive.function.client.WebClientResponseException - if an error occurs while attempting to invoke the API

    • bookingreconfirmationWithResponseSpec

      public org.springframework.web.reactive.function.client.WebClient.ResponseSpec bookingreconfirmationWithResponseSpec(String accept, String acceptEncoding, Integer from, Integer to, LocalDate start, LocalDate end, String filterType, List<String> clientReferences, List<String> references) throws org.springframework.web.reactive.function.client.WebClientResponseException
      Booking reconfirmation The Reconfirmation operation allows to retrieve the reconfirmation numbers (The confirmation number of the Hotel, both for the Hotelbeds product and for that of external suppliers product) of the bookings made by the client when requested in a GET call to our endpoint. Obtaining this reconfirmation numbers from hoteliers is an __asynchronous__ service: **reconfirmation numbers are not available at the time of the booking**, and as such they can't be informed at the time of the booking, hence the need for this operation. The Reconfirmation operation offers a wide variety of filters to help narrowing down reconfirmation number results. Only one filter can be used at the same time. Below the four possible filters you can use: * between two cheking dates * between two reconfirmation dates * list of clientReference ids * list of booking Ids ## Reconfirmation Service Additionally we offer you the capacity to receive the reconfirmation numbers automatically in our reconformation service, designed to automatically send you the reconfirmation information as soon as is available from the hoteliers in two different ways: * [Push Service](/documentation/hotels/booking-api/reconfirmation-service/push-service/) : The messages will be automatically sent in JSON format to an endpoint of your choice. * [Email Service](/documentation/hotels/booking-api/reconfirmation-service/email-service/): The messages will be automatically sent in an email to an address of your choice. Contact our support team at [apitude@hotelbeds.com]() to learn more about this features.

      200 - Sucessful response

      Parameters:
      accept - Response format.
      acceptEncoding - Defines type of encoding used on the data.
      from - Lowest value of the range of bookings with supplierConfirmationCodes to be returned (as in a paginated response).
      to - Highest value of the range of bookings with supplierConfirmationCodes to be returned (as in a paginated response).
      start - Date from when the method will start checking reconfirmation numbers. The format must be YYYY-MM-DD. In case of using __start__ and __end__ parameters, the use of __filterType__ parameter is mandatory.
      end - Date to when the method will finish checking reconfirmation numbers. The format must be YYYY-MM-DD. In case of using __start__ and __end__ parameters, the use of __filterType__ parameter is mandatory.
      filterType - The parameter is used to identify if the reconfirmation numbers is by check-in date or by reconfirmation date. Values: * CHECKIN: for the check-in date. * RECONFIRMATION: for the reconfirmation date the booking was included in Hotelbeds systems. In case of using __filterType__ parameters, the use of __start__ and __end__ parameters is mandatory.
      clientReferences - Parameter to filter the results by the booking reference in client API side.Can include multiple values separated by \",\". Max 80 values.
      references - Parameter to filter the results by the booking reference in Hotelbeds side.Can include multiple values separated by \",\". Max 80 values.
      Returns:
      ResponseSpec
      Throws:
      org.springframework.web.reactive.function.client.WebClientResponseException - if an error occurs while attempting to invoke the API