Things to note:

• Instant/Non-Instant Confirmation:

• Booking should be instant/non-instant confirmation based on the value of “isInstantConfirm”.
  For non-instant confirmation, please return “BOOKING_PENDING” as the response status.

• Booking Deduplication:

• Supplier API should accept Agoda booking id as the unique identifier of a booking.
  Supplier should implement booking deduplication on their side by accepting Agoda booking Id as one of the request parameter. When duplicate request was sent, supplier should return a SUCCESS response status indicating the booking already exists.

• Booking Retry

• Booking failure will not trigger a booking retry by default because in the case of no allotment or price mismatch, there is no point in retrying.
  If a retry is desired, supplier can choose to return BOOKING_TIMEOUT as the responseStatus and 408 as the http code before Agoda times out the booking request. This will trigger the retry on Agoda side. (Note: booking deduplication needs to be implemented correctly to ensure retry does not cause duplicated bookings.)