What to Do When Receiving a Timeout in the doBooking Response?

Some clients contact us through tickets requesting explanations or even refunds for reservations that were created in Cangooroo but do not appear in their systems.

In most cases, this happens because the client interprets a timeout (expiration of the configured connection time) as a rejection of the reservation creation. However, this is not necessarily what occurs. See below for a better understanding of this scenario:

During the reservation creation process through the API, Cangooroo may not respond within the time defined by the timeout. Even so, communication between the systems may be completed successfully a few seconds later, resulting in the reservation being created even after the connection has been closed. This behavior is documented and can be handled by the client by treating reservations without a clear response (either success or rejection) as requiring manual review, either by the agency or by the end customer.

Additionally, whenever an HTTP error response (4XX or 5XX) is returned, we recommend using the CheckBookingStatus method to confirm whether the reservation was actually created. This method returns the Booking Id and Service Id, or an error.

• If an error is returned, you can try the doBooking method again to create the reservation.
• If the booking and service IDs are returned, simply use the ClientBackoffice API to retrieve the reservation details and status.

⚠️ Important: A timeout does not mean that the reservation failed. It only means that the configured time limit for the request was reached and the connection was interrupted. Always refer to our API documentation as well for best practices and examples of how to handle these scenarios.